---
name: reel
description: |
  Use when the user wants to take part in REEL · 首映 on BNB Chain: RSVP for a free audience seat (gas only), commit BNB
  to the 24-hour box office (0.001–0.1 BNB per agent, one price for all backers, 10 BNB cap with pro-rata refunds,
  1 BNB greenlight or full refunds), launch the PancakeSwap pool, claim REEL (+ refunds), take a refund if the premiere
  was cancelled, or trade REEL. Only AI agents with a .ai Agent ID can take part.
  Triggers: reel, 首映, premiere, box office, RSVP REEL, commit BNB to REEL, claim reel.
metadata:
  version: '0.1.0'
  requires:
    bins: [baw, reel]
  install:
    - kind: node
      package: '@binance/agentic-wallet'
      bins: [baw]
      label: Binance Agentic Wallet CLI
    - kind: node
      package: 'reel-cli'
      bins: [reel]
      label: REEL CLI (the site's reel-cli.tgz, or this repo's cli/ folder)
---

# REEL · 首映 skill

REEL is a BEP-20 token on BNB Chain launched through a **24-hour box office for AI agents** (Binance Agentic Wallets
holding a **.ai Agent ID**). 1,000,000,000 REEL in three cuts:

| | |
|---|---|
| Backers (45%) | 450M REEL split **pro-rata to the BNB committed**: every backer pays **the same price** = BNB used ÷ 450M |
| Commit | **0.001–0.1 BNB per agent** in total (several commits allowed) |
| Hard cap | **10 BNB**. Above it, everyone's commitment is used pro-rata and **the excess comes back** at claim |
| Greenlight | at least **1 BNB** committed, otherwise the premiere is **cancelled** and everyone gets a **full refund** |
| Audience (20%, free) | 200M REEL split **equally** among every agent that **RSVPs** (gas only, once). Claimable **24 h after launch** |
| Pool (35%) | 80% of the BNB used + 350M REEL → PancakeSwap (opens ~2.9% above the backer price), **LP burned**; 20% → treasury |
| Tax | **none** — REEL is a plain token |

The `reel` CLI reads the chain and builds calldata; every transaction is previewed and signed by the user's Agentic
Wallet through `baw`. **It never holds keys. Never ask the user for a private key or seed phrase.**

Rules for you, the agent:
- Only act when the user asks. Never RSVP, commit, claim or sell on your own initiative; don't schedule recurring runs.
- **Every** `requestId` needs the user's explicit "yes" before `reel execute`. Show them the `askTheUser` text.
- REEL is a speculative token. Never promise profit, a price or a return. The estimate in a commit preview changes as
  others commit; the free audience share shrinks as more agents RSVP.
- Mention that the contracts are unaudited (see the site).

## 0. Preflight
```bash
reel preflight
```
Fix every `issues` item: `NO_BAW` / `NOT_SIGNED_IN` (install `@binance/agentic-wallet`, `baw auth signin`),
`NO_AGENT_ID` (claim a .ai in Binance Wallet), `LOW_BNB`, `NOT_CONFIGURED`.

## 1. The box office (phase "box office open", 24 hours)
```bash
reel status                  # BNB committed / cap / greenlight, backer price, audience size, time left
reel rsvp                    # free audience seat, gas only, once
reel commit --bnb 0.05       # back the premiere (0.001–0.1 BNB per agent in total)
reel me                      # your seat: estimated REEL + refund, audience share
```
RSVP and commit are independent: an agent can do either, both or neither.

## 2. After the 24 hours
- **greenlit, ready to launch**: anyone can run `reel launch` (≈ 2,800,000 gas).
- **launched**: `reel claim` → backer REEL + any refund at once. The audience share opens 24 h after launch; run
  `reel claim` again then (only when the user asks).
- **cancelled, refunds open**: `reel refund` → the full commitment back.

## 3. Trading (PancakeSwap, after launch, no tax)
```bash
reel trade buy --bnb 0.01 [--slippage 2]
reel trade sell --reel 100000 [--slippage 2]     # step 1: approve; then run it again
```

## 4. Sending a transaction
Every action prints `{ requestId, askTheUser, next }`. Ask the user in your own words; only after a clear yes:
`reel execute --request-id <id>`. It prints the decoded events (Rsvp, Committed, Launched, BackerClaimed, …).
If the Binance App needs a confirmation, follow the `next` line. Requests expire in about 5 minutes.
If an action returns `"action": "step 1 of 2: …"`, it's an approval: execute it (after a yes), then run the original
command again.