/reelclaw

name: reelclaw
description: Make short-form UGC video ads (TikTok, Reels, Shorts) for the product in the current repo with DansUGC ReelClaw and real human creator reactions from the DansUGC library, or with the user's own footage. You edit and render every reel locally on this machine with the reelclaw template engine (7 templates, TikTok Sans, safe-zone captions) and its reelclaw-playbook skill, and check each render frame by frame before delivering. The dansugc MCP server supplies the reaction clips, viral-format suggestions, trending music, research and posting; it does not render. Use when the user asks for UGC ads, reaction ads, TikTok/Reels ads, "make N ads for this app", ReelClaw, DansUGC videos, HyperFrames reels, "make viral reels" when the user is unsure which formats to use, hook variations of an ad, or editing or re-cutting an ad (caption style, position, timing, trims).
license: MIT
metadata:
  author: DansUGC
  version: "3.0.0"

DansUGC ReelClaw: UGC ads from your repo, edited locally

You are the producer and the editor. The open-source **reelclaw** engine ([danielhangan/reelclaw-templates](https://github.com/danielhangan/reelclaw-templates)) turns inputs into a 1080×1920 MP4 and ships the craft (brief, hooks, footage, music, QA, variants) as the `reelclaw-playbook` skill. This skill is the DansUGC layer on top: connecting, credits, accounts, real-creator clips, viral formats, trending music, research and posting. DansUGC reactions are always real human creators, never AI; never claim or imply otherwise. Always write the brand as **DansUGC** (lowercase s, capital UGC). DansUGC is optional footage: the user's own clips work too.

0. Connect and costs

• Tools live on the `dansugc` MCP server. Clients may prefix them

(`mcp__plugin_reelclaw_dansugc__…` in Claude Code, `mcp__dansugc__…` when added by hand). This skill uses bare names: `search_videos`, `purchase_videos`, `reelclaw_suggest_formats`, `reelclaw_trending_music`, `tiktok_search_videos`, `get_media_upload_url`, … Map: [references/tools.md](references/tools.md).

• The MCP server does **not** render or edit videos. There are no batch or render tools: all editing

and rendering happens on this machine (section 1). If a tool you expected is missing, see [references/errors.md](references/errors.md#removed-tools).

• No `dansugc` tools? Tell the user how to connect, then stop (or continue with their own footage if

they prefer):

• Claude Code: `/plugin marketplace add dansugc/reelclaw` + `/plugin install reelclaw@dansugc`

(or `claude mcp add --transport http dansugc https://dansugc.com/mcp`), then `/mcp` → the server (`plugin:reelclaw:dansugc`, or `dansugc` if added by hand) → Authenticate.

• Codex: `codex plugin marketplace add dansugc/reelclaw` + `codex plugin add reelclaw@dansugc`

(or `codex mcp add dansugc --url https://dansugc.com/mcp`), then `codex mcp login dansugc`.

• Any other agent: add the remote MCP server `https://dansugc.com/mcp` (no headers) and log in

when the client prompts.

• Auth is OAuth only (browser login with the DansUGC account). Never ask for or suggest an API

key. If a tool says it "no longer accepts API keys — reconnect with OAuth", see [references/errors.md](references/errors.md).

• Cost (say it when asked, and before anything is spent): the MCP works on any DansUGC account, no

plan needed (a plan only adds bonus credits and clip discounts). **Editing and rendering are local and free.** Users pay only for (a) reaction clips they don't already own (library clips are 11 credits each, images 8, less the plan's discount; owned clips are never charged again) and (b) research queries through the MCP (TikTok/Instagram search, `reelclaw_trending_music`: 0.02 credits per query, only on success). `reelclaw_suggest_formats` and `search_videos` are free. Top up at https://dansugc.com/dashboard/credits.

• **Talk in credits.** Every price, quote, and balance is in DansUGC credits ("11 credits per

clip", "Total: 104.50 credits", "Balance: 245.50 credits"). Never write "$" amounts; only convert to dollars if the user explicitly asks, and then say the credit amount first. Totals come from the tools (the `purchase_videos` quote step), never from multiplying per-clip prices yourself (owned clips are free and the plan discount is applied for you).

• **Accounts.** A user has a Personal Account and may belong to teams (each with its own credits

and plan discounts). When the user mentions a team, company, or teammate, or a spend fails for low personal balance, call `list_accounts` and pass that team's `project_id` to every account tool (`search_videos`, `get_video`, `purchase_videos`, `list_purchases`, `get_balance`, the research tools, `reelclaw_suggest_formats`, `reelclaw_trending_music`). Omit `project_id` for the Personal Account. Never switch accounts on your own; before the first spend on a team in a conversation, name the team and the amount and get an explicit yes.

• Tool results are JSON or Markdown; follow any `next_action`. Summarize; don't dump raw output.

1. Set up the studio (once per repo)

Work from the root of the user's product repo. All reels live in **one** reel project, `reelclaw-studio/`; finals go to `./reelclaw-output/`.

1. **Installer** (`<installer>` below). Until the `reelclaw` npm package is published it is `npx --yes github:danielhangan/reelclaw-templates`; this prints the right one:

   npm view reelclaw repository.url 2>/dev/null | grep -q danielhangan/reelclaw-templates \
     && echo "npx --yes reelclaw@latest" || echo "npx --yes github:danielhangan/reelclaw-templates"

Where the playbook or a template skill says `npx reelclaw@latest add`, use `<installer> add`. 2. **Create or reuse the project.** `reelclaw-studio/templates/` exists → reuse it (`ls` it to see the installed templates). Otherwise, or to add templates (safe to re-run; edited templates are kept): `<install