Recharm

View saved version →

---
name: "aspire-tone-brief"
description: >
  Build a Recharm footage brief for an ad anchored in an optimistic purchasing emotion — show the prospect already thriving, not suffering from a problem. Use whenever a user provides a creative brief, concept, or ad idea and wants to frame it around a positive mindstate such as achievement, belonging, empowerment, autonomy, competence, engagement, esteem, nurturance, or security. Searches the Recharm clip library and produces a shareable shot-by-shot brief with clip picks. Trigger this skill whenever the user mentions "optimistic", "positive emotion", "aspirational", "feel-good ad", "celebrate the win", "prospect mindstate", or provides a brief with an uplifting, forward-looking angle — even if they don't name the mindstate explicitly. Also use this when the user asks for an ad that leads with the prospect's joy, confidence, freedom, connection, or sense of accomplishment rather than pain or fear.
---

# Aspire Tone Brief

You orchestrate a multi-step search loop against the user's Recharm clip library to turn a creative brief into a shot-by-shot brief anchored in a specific **optimistic purchasing emotion** (mindstate). The ad speaks _to_ the prospect while they are in that positive mindstate — it mirrors their aspiration, not their problem.

The Recharm MCP server (`recharm`) is available in this plugin. Key behavioral notes:

- Call `list_labels` once at the start — keep the result for the entire workflow; do not call it again per scene.
- You do NOT build HTML. You pick clips and hand `save_brief` a slim structured package; the server derives every clip's URLs, name, duration, and aspect ratio from its `clipSymbol` and renders the HTML.
- Call `save_brief` exactly once, after clip picks are final. Each call mints a new URL.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — do not invent or guess label strings.

**Always refer to a clip in user-facing output as its `clipName` — `<clipSymbol> - <sceneType>`** (e.g. "AB - Product Reveal"). If `sceneType` is null, fall back to just the `clipSymbol`.

This skill processes one video at a time. If the brief calls for multiple videos, ask the user to pick one or confirm sequential processing.

Follow the steps below in order.

---

## The Nine Optimistic Mindstates

Each mindstate represents the positive emotional lens through which the prospect is viewing their world when they encounter the ad. The ad should _confirm and celebrate_ that feeling — not introduce doubt or fear.

| Mindstate                  | Core desire                                  | What the ad celebrates                            |
| -------------------------- | -------------------------------------------- | ------------------------------------------------- |
| **Optimistic Achievement** | Success, accomplishing goals                 | The win, the milestone, the earned result         |
| **Optimistic Autonomy**    | Freedom, self-expression, personal choice    | Being the author of one's own story               |
| **Optimistic Belonging**   | Connection, shared experiences, community    | Togetherness, tribe, being part of something      |
| **Optimistic Competence**  | Improvement, growth, doing one's best        | Getting better, leveling up, mastering something  |
| **Optimistic Engagement**  | Pleasure, excitement, full immersion in life | Joy, vitality, savoring the moment                |
| **Optimistic Empowerment** | Handling challenges, feeling capable         | Strength, readiness, rising to occasions          |
| **Optimistic Esteem**      | Recognition, appreciation, self-confidence   | Being seen, valued, proud of who you are          |
| **Optimistic Nurturance**  | Compassion, feeling loved, caring for others | Warmth, being cherished, giving or receiving care |
| **Optimistic Security**    | Safety, protection, peace of mind            | Confidence in the future, freedom from

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: "authority-ad-brief"
description: >
  Build a Recharm footage brief for an AUTHORITY ad — borrow the credibility of experts, credentials, science, or institutions so the viewer defers to trusted judgment instead of evaluating from scratch. Use whenever a user provides a brief, concept, or ad idea framed around expert endorsement, 'doctor recommended', 'formulated by', scientific backing, certifications, pro-grade positioning, or credential-led trust. Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. Trigger on "authority", "expert ad", "doctor recommended", "dermatologist", "nutritionist", "scientifically proven", "lab tested", "what the pros use", or any creative fronted by one qualified voice rather than a crowd. Distinct from social proof (many ordinary voices) — authority is one credible expert voice.
---

# Authority Ad Brief

You build a Recharm footage brief for a **authority** ad — one that borrows the credibility of experts, credentials, science, or institutions so the viewer defers to trusted judgment instead of evaluating from scratch.

The psychological engine: people defer to legitimate expertise. When a credible authority — a doctor, coach, scientist, certification body — vouches for the product, evaluation shortcuts to trust. This is distinct from social proof (many ordinary voices — this is *one qualified voice*), from liking (warmth), and from herd psychology (crowd feeling). The ad must establish the credential before spending it.

The Recharm MCP server (`recharm`) is available in this plugin. Key behavioral notes:

- Call `list_labels` once at the start — keep the result for the entire workflow; do not call it again per scene.
- Search hits from `search_clips_visually` already include `posterUrl` and `previewUrl` — use them directly. Only call `get_clip_poster_image` as a fallback if a hit is missing `posterUrl`.
- The template builds "View clip" and "Find similar" links itself from `clipSymbol`, `brand`, and `searchString` — you don't construct any Recharm app URLs.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — do not invent or guess label strings.
- Do **NOT** call `save_brief`. Instead, render the brief using `templates/brief.html` and upload via `save_html_file`.

**Always refer to a clip in user-facing output as its `clipName` — `<clipSymbol> - <sceneType>`** (e.g. "AB - Product Reveal"). If `sceneType` is null, fall back to just the `clipSymbol`.

Follow the steps below in order.

---

## Step 1 — Confirm the brand, hook, and content constraints

**Brand:** If the user already named a brand slug (e.g. `magic_spoon`, `hike_footwear`), use it. Otherwise call `list_brands` and ask the user to pick. If a user-named brand doesn't appear in `list_brands`, don't give up — call `list_labels` with that slug directly.

**Hook selection:** Choose the best-fitting authority hook pattern for the brief. If the user provided a specific hook line, use it and map it to the closest pattern. Make your pick, write a one-sentence rationale, and note why you're rejecting the others — you'll need all of this for the final brief output.

**Authority hook patterns:**
- *Expert Confession* — "A [dermatologist] told me to stop doing this immediately."
- *Credential Open* — "I've spent 15 years as a [profession]. This is what I actually use."
- *Science Lead* — "The study that changed how I think about [category]."
- *Formulated-By* — "Designed by [experts] who got tired of what's on shelves."
- *Insider Warning* — "As a [profession], here's what I'd never buy."
- *Award Stack* — "Backed by [certification], tested by [lab], used by [pros]."
- *Myth Bust* — "A [expert] debunks the biggest [category] myth."
- *Pro Standard* — "What [pros/athletes] use when nobody is sponsoring them."
- *Checklist Authority* — "The three things a [expert] checks before buying any [category]."
- *White Coat Reveal*

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: "brief-creator"
description: Turn an end-to-end video creative brief into a sectioned shot list, search the user's Recharm clip library for footage that fits each section using label-based filters, and produce a final creative brief with picks. Use whenever a user provides a brief/script/storyboard and asks for matching footage from Recharm.
---

# Find Video Footage for a Brief

You orchestrate a multi-step search loop against the user's Recharm clip library to turn a creative brief into a shot-by-shot brief with concrete clip picks. You use label-based filters to constrain searches — no visual review of clips is performed.

The Recharm MCP server (`recharm`) is available in this plugin. Key behavioral notes:

- Call `list_labels` once at the start — keep the result for the entire workflow; do not call it again per scene.
- You do NOT build HTML. You pick clips and hand `save_brief` a slim structured package; the server derives every clip's URLs, name, duration, and aspect ratio from its `clipSymbol` and renders the HTML.
- Call `save_brief` exactly once, after the clip picks are final. Each call mints a new URL.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — do not invent or guess label strings.

Please check the actual MCP server data for up-to-date API info.

**Always refer to a clip in user-facing output as its `clipName` — `<clipSymbol> - <sceneType>`** (e.g. "AB - Product Reveal"). If `sceneType` is null, fall back to just the `clipSymbol`.

This skill processes one video at a time. If you detect that the provided brief calls for creating multiple videos, prompt the user up front whether to run the skill once per video (sequentially) or pick a single video to process — then follow the steps below for each chosen video.

Follow the steps below in order.

## Before you begin — capture the prompt

Note the user's verbatim opening message now — before any processing. By Step 7, `prompt` will include this plus any further input they gave during the workflow (see below).

**File attachments (PDF, Word doc, etc.):** if the user attached a file, read its full content and treat it as the brief. For `prompt`, start with the filename, then a newline, then the full extracted text of the file — not a summary. If the user also typed an accompanying message (e.g. "make this into a brief"), prepend that message followed by a newline before the filename and content.

**Subsequent user input:** as the workflow progresses, append any further instructions, corrections, clarifications, or interruptions the user provides — verbatim. This includes answers to questions you asked, changes of direction, feedback on scene breakdowns, or anything else they typed. The goal is that a viewer of the brief can reconstruct the full intent from `prompt` alone.

## Step 1 — Confirm the brand

- If the user already named a brand slug (e.g. `lululemon`, `hike_footwear`), use it.
- Otherwise call `list_brands` and ask the user to pick.
- Do not guess the brand if there is any ambiguity.

## Step 2 — Fetch available labels

Call `list_labels(brandName)` and keep the result for the rest of the workflow. You will use these categories and labels to build search filters. Do not invent or use label values that were not returned by this call.

Note the following special-case categories if present:

- **SceneType**: each clip belongs to exactly one SceneType. Useful values include `Hook`, `CTA`, `Product Benefit`, `Demo`, and `Product Shot`.
- **ActorType**: indicates whether a person appears and whether they are speaking.

## Step 3 — Section the brief

Read the brief and break it into ordered scenes. Each scene should be approximately 2–5 seconds and correspond to a single Recharm clip. Cap the total at **18 scenes**.

For each scene capture:

- A short heading (e.g. "Hook — runner laces up at dawn")
- 1–2 sentences describing what should appear on screen
- The narrative role (hook

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: "commitment-consistency-ad-brief"
description: >
  Build a Recharm footage brief for a COMMITMENT & CONSISTENCY ad — open by surfacing an identity or goal the viewer has already claimed ('you said this was your year'), stack small yeses, then position the product as the consistent next step. Use whenever a user provides a brief, concept, or ad idea framed around keeping promises, staying on-streak, identity-based selling, micro-commitments, or New Year's-resolution energy. Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. Trigger on "commitment", "consistency", "identity ad", "keep your promise", "you said you would", "stay on track", "micro-yes", "if you're the kind of person who", or any creative where the lever is the viewer's own prior commitment. Also use for goal-callback or streak-keeper style ads.
---

# Commitment & Consistency Ad Brief

You build a Recharm footage brief for a **commitment & consistency** ad — one that opens by surfacing a commitment or identity the viewer already holds, stacks small agreements, then positions the product as the way to stay consistent with who they've said they are.

The psychological engine: people strive to act consistently with what they've already said and done. When an ad earns a small "yes" — an identity claim, a goal already declared, a value the viewer holds — the product becomes the way to honor that self-image. This is distinct from a problem-aware ad (pain-led) or a herd ad (crowd-led): the driver is *the viewer's own prior commitment*, and the tone is "stay true to yourself," never shame.

The Recharm MCP server (`recharm`) is available in this plugin. Key behavioral notes:

- Call `list_labels` once at the start — keep the result for the entire workflow; do not call it again per scene.
- Search hits from `search_clips_visually` already include `posterUrl` and `previewUrl` — use them directly. Only call `get_clip_poster_image` as a fallback if a hit is missing `posterUrl`.
- The template builds "View clip" and "Find similar" links itself from `clipSymbol`, `brand`, and `searchString` — you don't construct any Recharm app URLs.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — do not invent or guess label strings.
- Do **NOT** call `save_brief`. Instead, render the brief using `templates/brief.html` and upload via `save_html_file`.

**Always refer to a clip in user-facing output as its `clipName` — `<clipSymbol> - <sceneType>`** (e.g. "AB - Product Reveal"). If `sceneType` is null, fall back to just the `clipSymbol`.

Follow the steps below in order.

---

## Step 1 — Confirm the brand, hook, and content constraints

**Brand:** If the user already named a brand slug (e.g. `magic_spoon`, `hike_footwear`), use it. Otherwise call `list_brands` and ask the user to pick. If a user-named brand doesn't appear in `list_brands`, don't give up — call `list_labels` with that slug directly.

**Hook selection:** Choose the best-fitting commitment & consistency hook pattern for the brief. If the user provided a specific hook line, use it and map it to the closest pattern. Make your pick, write a one-sentence rationale, and note why you're rejecting the others — you'll need all of this for the final brief output.

**Commitment & Consistency hook patterns:**
- *Identity Check* — "If you're the kind of person who [X], keep watching."
- *Goal Callback* — "Remember when you said this was the year you'd [X]?"
- *Micro-Yes* — "Agree that [obvious truth]? Then you already agree with what's next."
- *Streak Keeper* — "You didn't come this far to only come this far."
- *Values Mirror* — "You care about [value] — so why is your [category] working against it?"
- *Resolution Rescue* — "Your January goal called. It's not dead yet."
- *Public Promise* — "You told everyone you'd [X]. Here's the easy way to actually keep it."
- *Small-Step Ladder* — "Start with ten seconds 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: creator-finder
description: Identify which creator (on-camera talent) in a Recharm clip library is the best fit to front a given ad creative concept. Use whenever the user asks who should star in, front, or be cast for an ad concept, asks to "find a creator", "pick talent", "which creator should I use", or wants a creator recommendation backed by evidence from their Recharm library. Searches the library visually, inspects poster images of real clips to judge each creator's on-camera fit, and delivers an HTML report with the recommended creator, supporting clips, and the reasons other creators were rejected.
---

# Creator Finder

You are acting as a casting director, but instead of audition tapes you have a Recharm clip library. Videos and clips are labeled with a `Creator` category. Your job: given an ad creative concept, work out what kind of person should front it, surface candidate creators through visual searches, **actually look at their faces** in poster images, and recommend one creator — with explicit reasoning for the pick and for every rejection. The deliverable is an HTML findings report, not a brief.

The Recharm MCP server provides: `list_brands`, `list_labels`, `search_clips_visually`, `get_clip_poster_image`, `get_clip_sprite_image`, `save_html_file`. Check the live tool schemas for current parameters.

Two principles drive everything below:

1. **Decide what you're looking for before you look.** If you start browsing faces first, you'll anchor on whoever you saw first. Define the target persona from the concept, then evaluate candidates against it.
2. **Labels get you candidates; only your eyes can cast them.** Search metadata tells you a creator exists and what scene types they have. Whether they have the right age, energy, polish, and camera presence for _this_ concept — you must judge from the actual images.

## Step 1 — Brand

Use the brand slug if the user named one. Otherwise call `list_brands` and ask the user to pick. Don't guess.

## Step 2 — Define the target creator persona and scene needs

Think through how this ad concept would actually be executed:

- **Scene needs**: what 3–6 types of scenes would the finished ad require? (e.g. hook, problem moment, product demo, testimonial to camera, lifestyle b-roll, CTA). The chosen creator should ideally cover most of them.
- **Target persona**: who should be on camera? Capture apparent age range, gender (if the concept implies one), energy (deadpan, high-energy, warm), polish (relatable UGC vs. pro spokesperson), and setting/lifestyle cues (office worker, golfer, gym, home).

State the persona and scene needs explicitly before searching — this is the rubric every candidate gets scored against.

## Step 3 — Fetch labels

Call `list_labels(brandName)` once and keep the result. Note:

- **Creator** — the candidate universe. Every recommendation must be a name from this list.
- **Gender / Age / Asset Type / Scene Type / Actor Type** — useful filter categories when present.

Only ever filter with label values returned by this call.

## Step 4 — Discovery searches: build the candidate pool

Run **one or two visual searches per scene need** (roughly 5–10 searches total), with short literal visual phrases (under ~8 words, describe what's on screen, not concepts). Vary subjects, framings, and settings across queries. Add a `Gender` or `Age` filter when the persona clearly implies one — but don't over-filter; discovery should cast a wide net.

Important quirk: only the **top few hits** of each search come back with `categoriesAndLabels` populated — that's where creator names come from. This is another reason to run many varied searches rather than one big one.

Each hit also returns a **`posterUrl`** (a hosted still thumbnail of the clip) and a `recharmUrl`. **Record the `posterUrl` alongside the `clipSymbol`** for every candidate's best clip — you will reuse it in Step 7 so the report shows the creator's actual face, not just initials. (`posterUrl` is wha

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: footage-gap-finder
description: Analyze a creative input — an ad concept, creative brief, ad transcript, script, or even a rough idea — and find which shot types are MISSING from the user's Recharm clip library. Use whenever the user asks "what footage are we missing", "find gaps in our library", "what do we need to shoot", "can our library support this idea", wants a shoot list of footage to capture before production, or wants to stress-test a creative concept against their existing clips. Brainstorms many shot types the concept calls for, searches the library visually for each, verifies hits by inspecting poster images, and delivers an HTML gap report (saved locally AND uploaded to a shareable Recharm URL) explaining each missing shot and why it would be useful. Produces a findings report, NOT a brief — never use this when the user wants a brief or clip picks for an edit.
---

# Footage Gap Finder

You are acting as a pre-production footage auditor. The user gives you a creative input — a polished brief, an ad transcript, a concept, or a one-line idea — and your job is to figure out what shots that idea _would need_, check whether the Recharm library actually has them, and report the ones it doesn't. The deliverable is an HTML gap report that a team can take straight into a shoot-planning meeting: each gap names the missing shot, why the creative needs it, and what to capture. The report is saved locally **and** uploaded to Recharm's public-share storage so the user gets a shareable link.

The Recharm MCP server provides: `list_brands`, `list_labels`, `search_clips_visually`, `get_clip_poster_image`, `get_clip_sprite_image`, `save_html_file`. Check the live tool schemas for current parameters.

**Two kinds of "poster image" — don't confuse them:**

- Every `search_clips_visually` hit already includes a `posterUrl` (a public HTTPS still-frame URL) plus `previewUrl` and `recharmUrl`. These URLs are what you embed in the HTML report — record the `posterUrl` for every clip you cite. No extra tool call is needed to get an image URL.
- `get_clip_poster_image` / `get_clip_sprite_image` return raw JPEG bytes **for you to look at** when judging whether a clip really depicts a shot. They are your verification eyes, not a source of embeddable URLs.

Three principles drive everything below:

1. **Generate generously, verify ruthlessly.** Brainstorm far more shot ideas than you expect to be missing. The value of this skill is breadth — a gap you never thought to search for is a gap you'll never report.
2. **Visual search always returns _something_.** `search_clips_visually` ranks by similarity; it rarely returns empty. A low cosine distance is encouraging and a high one is suspicious, but neither decides anything. A shot is only "covered" or "missing" after you have **looked at poster images** of the top hits and judged whether they actually depict the shot. (An empty or near-empty result set, however, is a strong gap signal — note it.)
3. **A gap is only worth reporting if you can argue for it.** Every gap in the report must say why this specific creative needs that shot — not "more footage is always nice".

## Step 1 — Brand

Use the brand slug if the user named one. Otherwise call `list_brands` and ask the user to pick. Don't guess.

## Step 2 — Derive shot ideas from the creative input

Read the input and reconstruct how the finished ad would actually be cut together. Then brainstorm **12–20 candidate shot types** that would help fulfill it. Cover the full structure, not just the obvious centerpiece:

- **Hook** — the scroll-stopping first frame (often the least-stocked and most valuable category)
- **Problem / tension** — the frustration, symptom, or "before" moment
- **Product in action** — demo, application, unboxing, close-ups of texture/mechanism/UI
- **Proof** — results, before/after, testimonial-to-camera, reactions
- **Lifestyle / world** — the setting and people the ad lives in
- **CTA support** — packaging, offer-

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: "herd-psychology-brief"
description: >
  Build a Recharm footage brief for a HERD PSYCHOLOGY ad — open with a FOMO or social-proof hook ("Why is everyone switching to X?", "Am I the only one who hasn't tried this?"), then ride the bandwagon narrative to the product reveal and CTA. Use whenever a user provides a brief, concept, or ad idea and wants to frame it around social proof, FOMO, viral curiosity, or the feeling that "everyone is doing this." Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. Trigger this skill whenever the user mentions "herd psychology", "FOMO", "bandwagon", "everyone is using", "why is everyone", "social proof hooks", "viral curiosity", "am I the only one", or provides a brief with a trend-driven, crowd-following angle. Also use when the user asks for herd-style hooks, bandwagon ad openers, or any creative where the core tension is "everyone else is already doing this — why aren't you?"
---

# Herd Psychology Ad Brief

You build a Recharm footage brief for a **herd psychology** ad — one that opens with a hook rooted in social curiosity or FOMO, then rides the bandwagon narrative to a product reveal and CTA.

The psychological engine: the viewer feels slightly behind a crowd that's already discovered something great. The ad validates that feeling ("you're not alone in not knowing yet") and then resolves it ("here's what they found"). This is distinct from a problem-aware ad (which leads with pain) or a solution-aware ad (which leads with the product). The driver here is _social momentum_ — not suffering, not features.

The Recharm MCP server (`recharm`) is available in this plugin. Key behavioral notes:

- Call `list_labels` once at the start — keep the result for the entire workflow; do not call it again per scene.
- You do NOT build HTML. You pick clips and hand `save_brief` a slim structured package; the server derives every clip's URLs, name, duration, and aspect ratio from its `clipSymbol` and renders the HTML.
- Call `save_brief` exactly once, after the clip picks are final. Each call mints a new URL.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — do not invent or guess label strings.

**Always refer to a clip in user-facing output as its `clipName` — `<clipSymbol> - <sceneType>`** (e.g. "AB - Product Reveal"). If `sceneType` is null, fall back to just the `clipSymbol`.

Follow the steps below in order.

---

## Step 1 — Confirm the brand, hook, and content constraints

**Brand:** If the user already named a brand slug (e.g. `magic_spoon`, `hike_footwear`), use it. Otherwise call `list_brands` and ask the user to pick. If a user-named brand doesn't appear in `list_brands`, don't give up — call `list_labels` with that slug directly.

**Hook selection:** Choose one herd psychology hook pattern from the list below that best fits the brief. If the user already provided a specific hook line, use it and map it to the closest pattern. If the brief is general, suggest a hook and confirm with the user before proceeding.

**Herd psychology hook patterns:**

- _Laggard FOMO_ — "Am I the only one who hasn't tried [X] yet?"
- _Trend curiosity_ — "Why is everyone suddenly obsessed with [X]?"
- _Switcher wave_ — "Why is everyone ditching [old thing] for [X]?"
- _Feed takeover_ — "Why is [X] all over my feed?"
- _Last to know_ — "Am I the last person to know about [X]?"
- _Shared discovery_ — "Have you seen why everyone is talking about [X]?"
- _Mass benefit_ — "Is everyone else seeing the benefits of [X]?"
- _Bandwagon check_ — "Is it just me, or is everyone switching to [X]?"
- _Hype investigation_ — "Why is everyone so excited about [X]?"
- _Ubiquity question_ — "Why is [X] suddenly everywhere?"

**ActorType preference:** Herd psychology ads benefit from social proof footage — people using the product, reacting positively, or going about active lives. Scan the brief and apply j

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: "hook-explorer"
description: >
  Build a 10-hook creative brief for a brand by selecting diverse hook archetypes from a curated template bank, filling them in specifically for the brand, pairing each hook with matching Recharm b-roll clip picks (no talking heads — Actor B-Roll and No Actor only), and saving a shareable brief designed for voiceover-led ads. Use this skill whenever a user wants to generate hook ideas, explore ad angles, or build a hook-focused brief for a brand — even if they say "give me hooks", "what hooks should we test", "generate 10 ad openers", or "I need hook options for [brand]". Always use this when the goal is finding hooks + b-roll footage for a VO-driven ad.
---

# Hook Explorer

You generate 10 diverse, brand-specific hooks for a given brand, match each hook with b-roll clips from the brand's Recharm library, and save a shareable brief where each section is one hook with its opening visuals and voiceover line. All clip picks are b-roll only — no talking heads or speaking actors. This brief is designed for voiceover-led ads where the hook line is spoken over footage, not delivered on camera.

The Recharm MCP server (`recharm`) is available in this plugin.

**Key rules (same as brief-creator):**

- Call `list_labels` once at the start — reuse for the whole workflow.
- Do NOT build HTML. Hand `save_brief` a structured v2 package; the server renders everything.
- Call `save_brief` exactly once after all clip picks are final.
- Only use label values returned by `list_labels` — never invent them.
- Do not paginate `search_clips_visually` — use first page only.
- Refer to clips in user-facing output as `clipName` = `<clipSymbol> - <sceneType>`.

---

## Step 1 — Gather brand context

Ask the user for (or infer from what they've already provided):

1. **Brand slug** — e.g. `magic_spoon`, `hike_footwear`. If unknown, call `list_brands` and have them pick.
2. **Product / SKU** (optional) — a specific product or flavor to feature, if any.
3. **Target audience** — who the hooks are for (e.g. "women 25–45 interested in fitness", "busy parents").
4. **Tone** — one or two words: funny, sincere, bold, educational, aspirational, etc.
5. **Any hook styles to include or avoid** — e.g. "no skeptic hooks", "definitely include a listicle hook".

If the user's message already contains enough context, proceed without asking — state your assumptions at the top of your output.

---

## Step 2 — Fetch available labels

Call `list_labels(brandName)`. Keep the full result for the rest of the workflow.

Note these categories for use in search filters later:

- **Scene Type** — e.g. `Hook`, `Visual Hook`, `Product Shot`, `Bowl Shot`, `CTA`.
- **Actor Type** — whether a person appears and whether they're speaking. Identify the exact label values for `No Actor` and `Actor B-Roll` from the returned labels — these are the only two Actor Type values used in this skill.
- **Product** — specific SKUs or flavors. Use these when the user named a specific product.

---

## Step 3 — Select and write 10 hooks

Read `references/hook-templates.md`. It contains 20 hook categories with 400+ templates across a wide range of psychological angles.

Select **10 hooks** spanning at least **7 different categories** — variety is the whole point. Fill each template in concretely for the brand: replace every placeholder (`[pain point]`, `[outcome]`, `[product]`, etc.) with specific language that fits this brand and audience. Don't leave generic placeholders — a hook like "Stop scrolling if you suffer from energy crashes" beats "Stop scrolling if you suffer from [problem]".

For each hook, produce:

- **Hook name** — a short label, e.g. "Skeptic Test", "Bold Claim", "FOMO Scroll-Stop"
- **Hook line** — the filled-in, verbatim hook text the creator or VO would say or show on screen
- **Visual opening** — 1 sentence describing what should be on screen during this hook (this drives the Recharm search)
- **Voiceover / on-screen text** — the hook lin

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: "liking-ad-brief"
description: >
  Build a Recharm footage brief for a LIKING ad — fronted by warmth, relatability, candor, and similarity, so the viewer buys because the ad feels like a recommendation from someone they'd be friends with. Use whenever a user provides a brief, concept, or ad idea framed around relatable confessions, best-friend recommendations, self-deprecating humor, 'real talk' energy, shared struggles, or unpolished authenticity. Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. Trigger on "liking", "relatable ad", "real talk", "bestie recommendation", "girl talk", "unpolished", "authentic UGC vibe", "friend telling a friend", or any creative where the persuasion engine is warmth and similarity rather than evidence, experts, or urgency.
---

# Liking Ad Brief

You build a Recharm footage brief for a **liking** ad — one fronted by warmth, relatability, and similarity — the viewer buys because the ad feels like a tip from someone they'd actually be friends with.

The psychological engine: people say yes to people they like — and we like people who are similar to us, who are candid, who feel familiar. The ad wins by being disarming and relatable before it sells anything: shared struggles, self-deprecating humor, best-friend energy. Distinct from authority (credentials) and social proof (evidence): the driver is *affection and similarity*, so imperfection is an asset, not a flaw.

The Recharm MCP server (`recharm`) is available in this plugin. Key behavioral notes:

- Call `list_labels` once at the start — keep the result for the entire workflow; do not call it again per scene.
- Search hits from `search_clips_visually` already include `posterUrl` and `previewUrl` — use them directly. Only call `get_clip_poster_image` as a fallback if a hit is missing `posterUrl`.
- The template builds "View clip" and "Find similar" links itself from `clipSymbol`, `brand`, and `searchString` — you don't construct any Recharm app URLs.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — do not invent or guess label strings.
- Do **NOT** call `save_brief`. Instead, render the brief using `templates/brief.html` and upload via `save_html_file`.

**Always refer to a clip in user-facing output as its `clipName` — `<clipSymbol> - <sceneType>`** (e.g. "AB - Product Reveal"). If `sceneType` is null, fall back to just the `clipSymbol`.

Follow the steps below in order.

---

## Step 1 — Confirm the brand, hook, and content constraints

**Brand:** If the user already named a brand slug (e.g. `magic_spoon`, `hike_footwear`), use it. Otherwise call `list_brands` and ask the user to pick. If a user-named brand doesn't appear in `list_brands`, don't give up — call `list_labels` with that slug directly.

**Hook selection:** Choose the best-fitting liking hook pattern for the brief. If the user provided a specific hook line, use it and map it to the closest pattern. Make your pick, write a one-sentence rationale, and note why you're rejecting the others — you'll need all of this for the final brief output.

**Liking hook patterns:**
- *Real Talk* — "Okay, real talk — I almost didn't post this."
- *Same-Boat* — "If your mornings look like this, we're already friends."
- *Candid Confession* — "I'm the laziest person I know. This is the only thing that stuck."
- *Best-Friend Rec* — "My best friend wouldn't shut up about this. She was right."
- *Self-Roast* — "I ignored this for a year because I'm stubborn. Don't be me."
- *Compliment Open* — "You clearly have good taste — that's exactly why this will annoy you."
- *Inside Joke* — "POV: you swear you'll meal prep this week."
- *Unpolished Review* — "No script, no ring light — here's what I actually think."
- *Shared Enemy* — "We both hate [annoying thing]. So does this brand."
- *Kitchen-Table Chat* — "Come here, sit down — we need to talk about breakfast."

**ActorType 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: problem-aware-ad-brief
description: Build a Recharm footage brief for a PROBLEM-AWARE ad — call out the problem, then sell the fix. Use whenever a brief, script, or storyboard targets people who already know they have a problem but not the solution, or the user mentions "problem aware", mid-funnel, pain-point-led ads, or wants an ad that opens by naming the viewer's frustration directly. Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. If the user asks for ad footage but the audience awareness level is unclear, ask whether the audience is unaware, problem-aware, or solution-aware before picking a skill.
---

# Problem-Aware Ad Brief

Turn a creative brief aimed at a **problem-aware market** — people who know they have a problem but don't know your solution — into a shot-by-shot footage brief with concrete clip picks from the user's Recharm library, via the `recharm` MCP server.

A problem-aware ad doesn't need to educate; the viewer already feels the pain. The hook's job is to **name that pain so precisely the viewer thinks "that's me"**, then move fast to the solution. Lingering on diagnosis bores this audience; skipping the problem call-out loses the "that's me" moment. That is why the stage order below is enforced, not suggested.

## The four stages — enforce strictly

Every scene belongs to exactly one stage, and stages appear in this order:

1. **Call out the problem** — open by naming the viewer's known frustration, vividly and specifically (e.g. "khakis that bunch and sag by lunch", "another clump of hair in the brush"). The viewer should feel recognized within 2 seconds.
2. **Introduce solution** — reveal the product as the fix.
3. **Answer objections / questions / increase trust** — proof: testimonials, demos, before/after, credentials, ingredients, durability tests, comparisons.
4. **Where to buy** — CTA: website, store, offer.

Scene budget: 8–14 scenes total (each scene ≈ 2–5 s, one Recharm clip). The problem call-out should be punchy (2–4 scenes); weight the middle toward solution + trust. If the user's brief skips a stage or reorders stages, point out the conflict with the problem-aware framework and ask before proceeding.

## Recharm mechanics (read once, applies throughout)

- Call `list_labels(brandName)` once at the start and keep the result; never invent label values or category names — use the exact strings returned (category names vary by brand: `Scene Type` vs `SceneType`, etc.).
- `search_clips_visually` returns slim hits: `clipSymbol`, `clipName`, `rawVideoPublicId`, `sceneType`, `cosineDistance` (lower = closer), `durationMs`, `categoriesAndLabels` (populated only for top hits). Never fetch poster or sprite images; pick on metadata only. Use only the first page — don't paginate.
- Refer to clips in all user-facing output by `clipName` (`<clipSymbol> - <sceneType>`), never bare `clipSymbol`.
- Call `save_brief` exactly once, after picks are final. The server renders the HTML — never build HTML or clip URLs yourself.
- One video per run. If the brief calls for multiple videos, ask the user whether to run per-video sequentially or pick one.

## Workflow

### Step 0 — Create a granular task list

Before any searching, create a visible task list with one task per stage — "Search Problem call-out scenes", "Search Solution-intro scenes", "Search Trust scenes", "Search Where-to-buy scenes" — plus "Confirm scene breakdown", "Establish primary creator", "Assemble & save brief", and "Explain picks & gaps". Mark each in progress and complete as you go. The searches take a while; granular tasks let the user watch the work happen stage by stage and catch a wrong turn early instead of at the end.

### Step 1 — Confirm the brand

Use the brand slug if the user named one; otherwise call `list_brands` and ask. Never guess between candidates.

### Step 2 — Fetch labels

Call `list_labels(brandName)`. Note which categories exist for: scene type, creator, actor

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: "reciprocity-ad-brief"
description: >
  Build a Recharm footage brief for a RECIPROCITY ad — give the viewer real value up front (a tip, a hack, a demo, an act of generosity), then let the product pitch land as a fair return of the favor. Use whenever a user provides a brief, concept, or ad idea framed around giving first: free value, 'steal my routine', money-saving tricks, samples, gifts, or generous no-strings openers. Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. Trigger on "reciprocity", "give first", "free value", "value-first ad", "steal my routine", "here's a free tip", "give before the ask", or any creative where the ad delivers something useful before selling. Also use when the user wants a soft-sell ad that earns the CTA through generosity rather than pressure.
---

# Reciprocity Ad Brief

You build a Recharm footage brief for a **reciprocity** ad — one that gives the viewer real value up front — a tip, a hack, a demo, an unexpected act of generosity — so the ask at the end feels like a natural return of the favor.

The psychological engine: people feel a deep pull to return favors. When an ad genuinely gives first — useful advice, a working demo, a gift — the viewer incurs a small, pleasant debt, and the product pitch lands as fair exchange rather than interruption. This is distinct from a herd-psychology ad (crowd-driven) or a scarcity ad (urgency-driven): the driver here is *indebtedness born of generosity* — the ad must actually deliver value before it asks.

The Recharm MCP server (`recharm`) is available in this plugin. Key behavioral notes:

- Call `list_labels` once at the start — keep the result for the entire workflow; do not call it again per scene.
- Search hits from `search_clips_visually` already include `posterUrl` and `previewUrl` — use them directly. Only call `get_clip_poster_image` as a fallback if a hit is missing `posterUrl`.
- The template builds "View clip" and "Find similar" links itself from `clipSymbol`, `brand`, and `searchString` — you don't construct any Recharm app URLs.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — do not invent or guess label strings.
- Do **NOT** call `save_brief`. Instead, render the brief using `templates/brief.html` and upload via `save_html_file`.

**Always refer to a clip in user-facing output as its `clipName` — `<clipSymbol> - <sceneType>`** (e.g. "AB - Product Reveal"). If `sceneType` is null, fall back to just the `clipSymbol`.

Follow the steps below in order.

---

## Step 1 — Confirm the brand, hook, and content constraints

**Brand:** If the user already named a brand slug (e.g. `magic_spoon`, `hike_footwear`), use it. Otherwise call `list_brands` and ask the user to pick. If a user-named brand doesn't appear in `list_brands`, don't give up — call `list_labels` with that slug directly.

**Hook selection:** Choose the best-fitting reciprocity hook pattern for the brief. If the user provided a specific hook line, use it and map it to the closest pattern. Make your pick, write a one-sentence rationale, and note why you're rejecting the others — you'll need all of this for the final brief output.

**Reciprocity hook patterns:**
- *Free Blueprint* — "Steal my exact [routine/recipe/system] — no purchase required."
- *Money Saver* — "I'm about to save you $[X] in 30 seconds."
- *No-Strings Tip* — "You don't have to buy anything — just try this one thing."
- *Insider Giveaway* — "The [industry] trick brands don't give away for free."
- *Over-Deliver Promise* — "Screenshot this — it's the only [guide] you'll ever need."
- *Gift Frame* — "Consider this my gift to your [morning routine]."
- *Try-Before-Anything* — "Test this at home before you spend a dime."
- *Reverse Pitch* — "I'm not here to sell you — I'm here to fix your [problem]."
- *Sample Drop* — "We're basically giving this away — here's why."
- *Value Stack* — "Thre

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: "scarcity-ad-brief"
description: >
  Build a Recharm footage brief for a SCARCITY ad — built on limited supply, limited time, or exclusivity: what's rare is wanted, and what's about to run out gets bought now. Use whenever a user provides a brief, concept, or ad idea framed around sell-outs, low stock, countdowns, limited drops, waitlists, seasonal windows, or last-chance urgency. Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. Trigger on "scarcity", "limited edition", "selling out", "almost gone", "last chance", "48 hours", "restock", "limited drop", "waitlist", "while supplies last", or any creative where the tension is dwindling availability. Distinct from herd psychology: herd sells 'everyone has it'; scarcity sells 'soon nobody can get it.'
---

# Scarcity Ad Brief

You build a Recharm footage brief for a **scarcity** ad — one built on limited supply, limited time, or exclusivity — what's rare is wanted, and what's about to run out gets bought now instead of later.

The psychological engine: people want more of what they can have less of, and potential loss looms roughly twice as large as equivalent gain. Limited drops, low stock, and closing windows convert "maybe later" into "now." Distinct from herd psychology: herd sells "everyone has it"; scarcity sells "soon nobody can get it." Critical constraint: only use scarcity claims the brand can substantiate — fake urgency destroys trust.

The Recharm MCP server (`recharm`) is available in this plugin. Key behavioral notes:

- Call `list_labels` once at the start — keep the result for the entire workflow; do not call it again per scene.
- Search hits from `search_clips_visually` already include `posterUrl` and `previewUrl` — use them directly. Only call `get_clip_poster_image` as a fallback if a hit is missing `posterUrl`.
- The template builds "View clip" and "Find similar" links itself from `clipSymbol`, `brand`, and `searchString` — you don't construct any Recharm app URLs.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — do not invent or guess label strings.
- Do **NOT** call `save_brief`. Instead, render the brief using `templates/brief.html` and upload via `save_html_file`.

**Always refer to a clip in user-facing output as its `clipName` — `<clipSymbol> - <sceneType>`** (e.g. "AB - Product Reveal"). If `sceneType` is null, fall back to just the `clipSymbol`.

Follow the steps below in order.

---

## Step 1 — Confirm the brand, hook, and content constraints

**Brand:** If the user already named a brand slug (e.g. `magic_spoon`, `hike_footwear`), use it. Otherwise call `list_brands` and ask the user to pick. If a user-named brand doesn't appear in `list_brands`, don't give up — call `list_labels` with that slug directly.

**Hook selection:** Choose the best-fitting scarcity hook pattern for the brief. If the user provided a specific hook line, use it and map it to the closest pattern. Make your pick, write a one-sentence rationale, and note why you're rejecting the others — you'll need all of this for the final brief output.

**Scarcity hook patterns:**
- *Sell-Out Streak* — "This has sold out four times. It's back — for now."
- *Countdown Open* — "You have 48 hours. Then it's gone."
- *Low-Stock Alert* — "There are fewer than [500] of these left."
- *Limited Drop* — "They only make this once a year."
- *Waitlist Flex* — "[30,000] people were on the waitlist. Doors just opened."
- *Last-Chance Frame* — "If you've been waiting for a sign, this is the last one."
- *Exclusive Access* — "Not on shelves. Not on Amazon. Only here."
- *Season Closer* — "When the [seasonal flavor] is gone, it's gone until next year."
- *Price-Window* — "The price goes up Friday. That's not a tactic — that's the calendar."
- *Almost-Missed-It* — "I nearly missed the restock. Don't make my mistake."

**ActorType preference:** Scarcity ads need kinetic, urgent fo

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: "social-proof-ad-brief"
description: >
  Build a Recharm footage brief for a SOCIAL PROOF ad — lead with hard evidence of other people's approval: review counts, star ratings, testimonials, UGC, sold-out stats, third-party awards. Use whenever a user provides a brief, concept, or ad idea framed around reviews, ratings, testimonials, 'thousands of customers', before/after results from real users, or evidence-led persuasion. Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. Trigger on "social proof", "reviews ad", "testimonial ad", "five-star", "rated #1", "customers say", "as seen in", or any creative where the sell is verifiable evidence that many others approve. NOTE: if the angle is FOMO/bandwagon feeling ("why is everyone switching?"), use herd-psychology-brief instead — this skill is for evidence-led proof, not crowd momentum.
---

# Social Proof Ad Brief

You build a Recharm footage brief for a **social proof** ad — one that leads with hard evidence of other people's approval — review counts, star ratings, testimonials, UGC, sold-out stats — until the viewer concludes "this many people can't be wrong."

The psychological engine: when people are uncertain, they look at what others have decided. This skill is evidence-led: ratings, review excerpts, user counts, real-customer results, stacked until skepticism collapses. It is deliberately distinct from the herd-psychology brief, which sells the *feeling* of a bandwagon and FOMO — here the sell is *verifiable proof*. Herd says "everyone's doing it"; social proof says "here's the evidence."

The Recharm MCP server (`recharm`) is available in this plugin. Key behavioral notes:

- Call `list_labels` once at the start — keep the result for the entire workflow; do not call it again per scene.
- Search hits from `search_clips_visually` already include `posterUrl` and `previewUrl` — use them directly. Only call `get_clip_poster_image` as a fallback if a hit is missing `posterUrl`.
- The template builds "View clip" and "Find similar" links itself from `clipSymbol`, `brand`, and `searchString` — you don't construct any Recharm app URLs.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — do not invent or guess label strings.
- Do **NOT** call `save_brief`. Instead, render the brief using `templates/brief.html` and upload via `save_html_file`.

**Always refer to a clip in user-facing output as its `clipName` — `<clipSymbol> - <sceneType>`** (e.g. "AB - Product Reveal"). If `sceneType` is null, fall back to just the `clipSymbol`.

Follow the steps below in order.

---

## Step 1 — Confirm the brand, hook, and content constraints

**Brand:** If the user already named a brand slug (e.g. `magic_spoon`, `hike_footwear`), use it. Otherwise call `list_brands` and ask the user to pick. If a user-named brand doesn't appear in `list_brands`, don't give up — call `list_labels` with that slug directly.

**Hook selection:** Choose the best-fitting social proof hook pattern for the brief. If the user provided a specific hook line, use it and map it to the closest pattern. Make your pick, write a one-sentence rationale, and note why you're rejecting the others — you'll need all of this for the final brief output.

**Social Proof hook patterns:**
- *Review Mountain* — "12,000 five-star reviews later, I finally tried it."
- *Skeptic Convert* — "I read the reviews to prove it was a scam. I ordered two."
- *Stat Lead* — "9 out of 10 people who try [X] reorder it."
- *Review Digest* — "I read 500 reviews of [X] so you don't have to."
- *Rated #1* — "The internet's highest-rated [category], actually tested."
- *Testimonial Splice* — "Real customers, unscripted, on why they switched."
- *Sold-Out Proof* — "It sold out four times last year. Here's why."
- *Before/After Wall* — "These results came from customers, not the brand."
- *Comment Section* — "The comment section made me b

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: solution-aware-ad-brief
description: Build a Recharm footage brief for a SOLUTION-AWARE ad — lead with the product, win on proof and differentiation. Use whenever a brief, script, or storyboard targets people who already know solutions like this exist (bottom-of-funnel, retargeting, comparison shoppers), or the user mentions "solution aware", "warm audience", "why us", competitor comparisons, or wants an ad that opens on the product itself. Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. If the user asks for ad footage but the audience awareness level is unclear, ask whether the audience is unaware, problem-aware, or solution-aware before picking a skill.
---

# Solution-Aware Ad Brief

Turn a creative brief aimed at a **solution-aware market** — people who already know products like this exist and are weighing options — into a shot-by-shot footage brief with concrete clip picks from the user's Recharm library, via the `recharm` MCP server.

A solution-aware ad has nothing to teach and no pain to dramatize: the viewer is comparing. Lead with the product immediately, then win the comparison with **proof and differentiation** — that middle stage is where this ad lives or dies. Re-explaining the problem wastes the viewer's patience. That is why the stage order below is enforced, not suggested.

## The three stages — enforce strictly

Every scene belongs to exactly one stage, and stages appear in this order:

1. **Call out the solution** — open on the product, named and shown, with its sharpest differentiating claim (e.g. "the only khakis with 4-way stretch", "the dermatologist-built hair serum"). No problem setup.
2. **Answer objections / questions / increase trust** — the heart of the ad: testimonials, demos, before/after, credentials, ingredients, durability tests, competitor comparisons, social proof. Anticipate the specific doubts a comparison shopper has (does it work? why this one? is it worth more?) and give each its own scene.
3. **Where to buy** — CTA: website, store, offer, guarantee.

Scene budget: 6–12 scenes total (each scene ≈ 2–5 s, one Recharm clip). Stage 1 should be 1–3 scenes; weight heavily toward stage 2 — proof is the product here. If the user's brief skips a stage or reorders stages, point out the conflict with the solution-aware framework and ask before proceeding.

## Recharm mechanics (read once, applies throughout)

- Call `list_labels(brandName)` once at the start and keep the result; never invent label values or category names — use the exact strings returned (category names vary by brand: `Scene Type` vs `SceneType`, etc.).
- `search_clips_visually` returns slim hits: `clipSymbol`, `clipName`, `rawVideoPublicId`, `sceneType`, `cosineDistance` (lower = closer), `durationMs`, `categoriesAndLabels` (populated only for top hits). Never fetch poster or sprite images; pick on metadata only. Use only the first page — don't paginate.
- Refer to clips in all user-facing output by `clipName` (`<clipSymbol> - <sceneType>`), never bare `clipSymbol`.
- Call `save_brief` exactly once, after picks are final. The server renders the HTML — never build HTML or clip URLs yourself.
- One video per run. If the brief calls for multiple videos, ask the user whether to run per-video sequentially or pick one.

## Workflow

### Step 0 — Create a granular task list

Before any searching, create a visible task list with one task per stage — "Search Solution call-out scenes", "Search Trust & differentiation scenes", "Search Where-to-buy scenes" — plus "Confirm scene breakdown", "Establish primary creator", "Assemble & save brief", and "Explain picks & gaps". Because stage 2 carries most of the ad, split it into one task per objection/proof theme (e.g. "Search demo proof", "Search testimonial proof", "Search comparison proof"). Mark each in progress and complete as you go — granular tasks let the user watch the work happen and catch a wrong turn early instead of at t

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: "uber-ad-brief"
description: >
  Build a Recharm footage brief for an Uber-style ad — where the creative concept is set inside
  a rideshare and centers on the driver-passenger dynamic as the vehicle for storytelling about
  a product. Use this skill whenever a user provides an ad concept, brief, or product idea and
  wants to frame it around an Uber ride, rideshare setting, driver-passenger conversation, backseat
  discovery, or any in-car / commute scenario. Trigger on: "uber ad", "rideshare brief", "in-car ad
  concept", "driver-passenger", "backseat", "make an ad set in an Uber", or any brief that uses a
  car ride as the storytelling device. Always use this skill when the brief involves a prospect who
  is a passenger or driver in a rideshare — even if the user doesn't say "Recharm" or "brief"
  explicitly.
---

# Uber-Style Ad Brief Creator

You turn a product and an ad concept direction into a fully sectioned Uber-style creative brief,
then search the user's Recharm clip library for footage that fits, and produce a shareable brief.

The Recharm MCP server (`recharm`) is available. Key rules:

- Call `list_labels` **once** at the start — reuse it throughout, never call it again per scene.
- Do NOT build HTML. Hand `save_brief` a structured v2 package; the server renders everything.
- Call `save_brief` exactly **once**, after all clip picks are final.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — never invent or guess label strings.
- Always refer to a clip as its `clipName`: `<clipSymbol> - <sceneType>`. Fall back to `clipSymbol`
  if `sceneType` is null.

---

## Uber Ad Concept Archetypes

When the user's brief implies an approach, map it to one (or a blend) of these archetypes. If the
brief is open-ended, present 3–4 options and let the user pick.

### Original 10 Archetypes

1. **Expert Advice POV** — Driver stops mid-ride to offer niche, unsolicited life advice about the
   product. Feels like a genuine slightly-intrusive Uber conversation.
2. **Hidden Compartment Reveal** — Driver reveals the car is secretly stocked with the brand's
   products instead of the usual water/chargers. Acts like it's the most normal thing in the world.
3. **Music Taste Test** — Driver plays a track that perfectly matches the product's vibe, using the
   car's speakers to demonstrate the product's benefits (sound quality, mood-setting, etc.).
4. **"Wait, Look at This" Detour** — Driver pulls over at a scenic spot or store specifically to
   show the passenger a cool product feature or use case. Breaks the monotony of the car shot.
5. **Passenger Challenge** — Driver challenges the passenger to try the product for the duration of
   the ride and captures their raw, unfiltered first-impression reaction.
6. **Backseat Vlogger** — Dashcam-style angle catches the passenger "accidentally" discovering the
   product in the backseat and starting an organic conversation about it.
7. **Road Trip Prep** — Montage of the driver prepping the car — and prominently including the
   product as an essential part of the service they offer every passenger.
8. **Inside Joke Dynamic** — Driver and passenger are already laughing together, then effortlessly
   pivot to how the product solved a common problem they both share.
9. **Before/After Traffic Jam** — High-stress, gridlocked ride transforms into a relaxed experience
   once the driver introduces the product. Positions it as a mood-shifter or stress-reliever.
10. **The Rating Play** — Driver jokingly asks for a "5-star rating," but only if the passenger
    agrees that [Product] is the best thing they've tried all day. Familiar mechanic → CTA.

### 10 Additional Archetypes

11. **ETA Countdown** — Driver references the ride's remaining time ("6 minutes left") and shows
    how the product fits perfectly into any commute window — making every ride feel productive.
12. **Surge Pricing Confession** — Driver jokes about surg

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: unaware-ad-brief
description: Build a Recharm footage brief for an UNAWARE-market ad — symptom-led, educate-then-sell. Use whenever a brief, script, or storyboard targets cold or top-of-funnel audiences, or the user mentions "unaware", "cold traffic", "doesn't know they have a problem", or wants an ad that opens on a symptom or relatable moment rather than the product. Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. If the user asks for ad footage but the audience awareness level is unclear, ask whether the audience is unaware, problem-aware, or solution-aware before picking a skill.
---

# Unaware-Market Ad Brief

Turn a creative brief aimed at an **unaware market** — people who don't yet know they have a problem — into a shot-by-shot footage brief with concrete clip picks from the user's Recharm library, via the `recharm` MCP server.

An unaware-market ad must earn the right to sell. It opens on a **symptom** the viewer recognizes from their own life, **diagnoses** the underlying problem, and only then introduces the product. Selling too early loses this audience entirely — that is why the stage order below is enforced, not suggested.

## The five stages — enforce strictly

Every scene belongs to exactly one stage, and stages appear in this order:

1. **Symptom** — open on a relatable, *felt* experience. No product, no problem-naming yet. (e.g. "she keeps finding hair on her pillow", "he tugs at pants that don't fit right".)
2. **Diagnose with problem** — name and explain the underlying problem behind the symptom. Educational and authority footage belongs here (expert talking, animation, close-ups of the cause).
3. **Introduce solution** — reveal the product as the answer to the diagnosed problem.
4. **Answer objections / questions / increase trust** — proof: testimonials, demos, before/after, credentials, ingredients, durability tests.
5. **Where to buy** — CTA: website, store, offer.

Scene budget: 10–18 scenes total (each scene ≈ 2–5 s, one Recharm clip). Weight scenes toward stages 1–2 — the education work is what this ad type does that others skip. If the user's brief skips a stage or reorders stages, point out the conflict with the unaware framework and ask before proceeding.

## Recharm mechanics (read once, applies throughout)

- Call `list_labels(brandName)` once at the start and keep the result; never invent label values or category names — use the exact strings returned (category names vary by brand: `Scene Type` vs `SceneType`, etc.).
- `search_clips_visually` returns slim hits: `clipSymbol`, `clipName`, `rawVideoPublicId`, `sceneType`, `cosineDistance` (lower = closer), `durationMs`, `categoriesAndLabels` (populated only for top hits). Never fetch poster or sprite images; pick on metadata only. Use only the first page — don't paginate.
- Refer to clips in all user-facing output by `clipName` (`<clipSymbol> - <sceneType>`), never bare `clipSymbol`.
- Call `save_brief` exactly once, after picks are final. The server renders the HTML — never build HTML or clip URLs yourself.
- One video per run. If the brief calls for multiple videos, ask the user whether to run per-video sequentially or pick one.

## Workflow

### Step 0 — Create a granular task list

Before any searching, create a visible task list with one task per stage — "Search Symptom scenes", "Search Diagnose scenes", "Search Solution-intro scenes", "Search Trust scenes", "Search Where-to-buy scenes" — plus "Confirm scene breakdown", "Establish primary creator", "Assemble & save brief", and "Explain picks & gaps". Mark each in progress and complete as you go. The searches take a while; granular tasks let the user watch the work happen stage by stage and catch a wrong turn early instead of at the end.

### Step 1 — Confirm the brand

Use the brand slug if the user named one; otherwise call `list_brands` and ask. Never guess between candidates.

### Step 2 — Fetch labels

Call `list_labels(brandN

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: "unity-ad-brief"
description: >
  Build a Recharm footage brief for a UNITY ad — built on shared identity: not 'people like you use this' but 'this is ours; we made it for us.' Use whenever a user provides a brief, concept, or ad idea framed around tribe, family, community, subculture, co-creation, 'made by us for us', hometown pride, or in-group belonging. Searches the user's Recharm clip library and produces a shareable shot-by-shot brief with clip picks. Trigger on "unity", "tribe ad", "community ad", "our people", "if you know you know", "IYKYK", "made by runners for runners", "for my fellow", "join the family", or any creative where buying feels like belonging. Distinct from liking (affection between individuals) and social proof (evidence from strangers) — unity is shared membership.
---

# Unity Ad Brief

You build a Recharm footage brief for a **unity** ad — one built on shared identity — not "people like you use this" but "this is ours; we made it for us." Buying feels like belonging, not shopping.

The psychological engine: the deepest Cialdini lever: shared identity. People say yes to "one of us." Family, hometown, subculture, profession, co-creation — when the brand credibly sits inside the viewer's "we," the purchase becomes an act of membership. Distinct from liking (affection and similarity between individuals) and social proof (evidence from strangers): unity is *membership*, and the ad must speak insider fluently or it reads as pandering.

The Recharm MCP server (`recharm`) is available in this plugin. Key behavioral notes:

- Call `list_labels` once at the start — keep the result for the entire workflow; do not call it again per scene.
- Search hits from `search_clips_visually` already include `posterUrl` and `previewUrl` — use them directly. Only call `get_clip_poster_image` as a fallback if a hit is missing `posterUrl`.
- The template builds "View clip" and "Find similar" links itself from `clipSymbol`, `brand`, and `searchString` — you don't construct any Recharm app URLs.
- Do not paginate `search_clips_visually` — use the first page only.
- Only use label values returned by `list_labels` — do not invent or guess label strings.
- Do **NOT** call `save_brief`. Instead, render the brief using `templates/brief.html` and upload via `save_html_file`.

**Always refer to a clip in user-facing output as its `clipName` — `<clipSymbol> - <sceneType>`** (e.g. "AB - Product Reveal"). If `sceneType` is null, fall back to just the `clipSymbol`.

Follow the steps below in order.

---

## Step 1 — Confirm the brand, hook, and content constraints

**Brand:** If the user already named a brand slug (e.g. `magic_spoon`, `hike_footwear`), use it. Otherwise call `list_brands` and ask the user to pick. If a user-named brand doesn't appear in `list_brands`, don't give up — call `list_labels` with that slug directly.

**Hook selection:** Choose the best-fitting unity hook pattern for the brief. If the user provided a specific hook line, use it and map it to the closest pattern. Make your pick, write a one-sentence rationale, and note why you're rejecting the others — you'll need all of this for the final brief output.

**Unity hook patterns:**
- *In-Group Call* — "This is for my fellow [runners/nurses/new parents]."
- *IYKYK* — "If you know, you know."
- *Made-By-Us* — "Made by [runners], for [runners]. Nobody else would get it."
- *We Don't* — "Our people don't do [mainstream compromise]."
- *Family Table* — "In this house, breakfast is sacred."
- *Roots Nod* — "For everyone who grew up on [shared memory] — we fixed it."
- *Tribe Test* — "You can spot one of us from across the gym."
- *Co-Creation* — "You asked. We built it. It's yours too."
- *Insider Language* — "[Niche slang] — if that made sense, this is for you."
- *Belonging Promise* — "You've found your people. Here's the handshake."

**ActorType preference:** Unity ads need footage of people together — groups, families, teams sharing rituals; solo shots undercu

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.