plvr-event-discovery

TotalClaw 作者 totalclaw

发现并推荐符合用户偏好的现场活动,然后使用网络流程(无公共 API)协助在 plvr.io 上检票,包括门票选择、预订窗口处理、x402 钱包支付交接和购买后确认捕获。当用户询问正在发生什么活动、想要在本周末/今晚参加有趣的活动、询问要做的事情、按地点/日期/类型/预算请求活动想法、要求比较门票选项或需要帮助获取活动权限时使用。

安装 / 下载方式

TotalClaw CLI推荐
totalclaw install totalclaw:totalclaw~kimchichobo-plvr-event-discovery
cURL直接下载,无需登录
curl -fsSL https://skills.taituai.com/api/skills/totalclaw%3Atotalclaw~kimchichobo-plvr-event-discovery/file -o kimchichobo-plvr-event-discovery.md
## 概述(中文)

发现并推荐符合用户偏好的现场活动,然后使用网络流程(无公共 API)协助在 plvr.io 上检票,包括门票选择、预订窗口处理、x402 钱包支付交接和购买后确认捕获。当用户询问正在发生什么活动、想要在本周末/今晚参加有趣的活动、询问要做的事情、按地点/日期/类型/预算请求活动想法、要求比较门票选项或需要帮助获取活动权限时使用。

## 原文

# PLVR Event Discovery

## Overview

Use browser automation against the PLVR website. Treat this as a web-only workflow: discover events, open event pages, select ticket types, then guide payment via x402 (wallet flow through Coinbase Commerce).

## Ground Rules

- Use browser actions; do not assume a PLVR REST API exists.
- Treat purchase actions as high-risk; ask for explicit confirmation immediately before final payment submission.
- Track reservation timing. Ticket selection reserves inventory for ~10 minutes.
- Require an email for guest checkout when the user is not logged in.
- Capture and report evidence after checkout (order summary, confirmation state, any reference IDs).

## Workflow

1. Open `https://plvr.io` and discover relevant events (date, city, artist, venue, price tier when visible).
2. Present short options to the user and ask which event/ticket type they want.
3. Open the chosen event and select the requested ticket type.
4. Confirm reservation window and countdown (if shown).
5. Move to checkout and gather/confirm required fields:
   - email address (required for ticket delivery if guest)
   - any attendee metadata requested by PLVR
6. Confirm payment method is wallet-based via the `Crypto` option (Coinbase Commerce flow / x402-aligned wallet checkout).
7. Ask for explicit user approval before final pay/submit click.
8. Complete checkout and capture confirmation details.
9. Summarize what happened, including expected ticket delivery format and where it will arrive.

## Output Template

Use this concise format when reporting progress or completion:

- Event: <name>
- Ticket: <type / quantity>
- Reservation status: <active / expired> (+ time left if visible)
- Checkout identity: <guest email or logged-in account>
- Payment method: x402 wallet (Coinbase Commerce)
- Purchase status: <pending / paid / failed>
- Confirmation evidence: <order number / confirmation screen text>
- Ticket delivery: PDF + QR via email

## Known Product Facts

- PLVR is currently web-only for this workflow (no API provided by user).
- Browsing and purchasing do not require login.
- Guest checkout requires email; PLVR may create an account from purchase details.
- Purchase flow: select ticket (reserved ~10 minutes) → pay → confirm.
- Ticket output: PDF and QR sent by email.

## Unknown / Must Verify Per Transaction

Check these live during each run and report clearly:

- geo restrictions
- KYC or wallet verification requirements
- refund/cancellation policy at event and platform level
- rate limiting, anti-bot challenges, or CAPTCHA
- chain/network/fees supported by the wallet payment screen