Compare commits

...
7 Commits
Author SHA1 Message Date
coreyhaines31 c21a984a56 chore: sync skills with marketplace.json, plugin.json, and README 2026-07-22 18:09:58 +00:00
Corey Haines 140a9e327b Merge pull request #477 from coreyhaines31/development
Release: influencer-marketing skill (2.9.0)
2026-07-22 11:09:38 -07:00
Corey HainesandClaude Opus 4.8 fc3b324f1d feat: influencer-marketing skill (expanded from PR #417 contribution, standalone) (#465)
* feat: add influencer-marketing skill (1.0.0)

Influencer, creator, and ambassador partnerships end to end. Foundation
contributed by @Adi29102000-s (PR #417), expanded to house standard and
shipped standalone: the influencer<->ambassador spectrum, finding &
vetting, deal structuring + whitelisting, a full FTC disclosure section
(gap in the original), the creative brief, ROI measurement, and
structured ambassador-program design. Six evals. New skill = repo y
release 2.9.0. Closes #462.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(influencer-marketing): precise FTC liability wording per codex (can be held liable / expected to monitor)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* feat(influencer-marketing): fold in comp benchmark table + run-of-show checklist from #460

Adapts @SamSon75's dollar-range compensation table (aligned to our tier
definitions) and 4-phase checklist into the standalone skill, so #460 can be
closed as superseded.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-22 11:05:13 -07:00
Corey Haines 67264763cb Merge pull request #467 from coreyhaines31/development
release: v2.8.12 — product-marketing context version history
2026-07-16 12:07:40 -07:00
Corey HainesandClaude Fable 5 8054011197 feat(product-marketing): version history for the context document (2.1.0) (#466)
* feat(product-marketing): version history for the context document (2.1.0)

.agents/product-marketing.md now carries a Document version header + a
newest-first Changelog section. The update flow reads the version/recent
changelog on open and, on save, bumps the version + prepends an entry
naming what changed and why (never rewriting past entries). Makes
positioning/ICP changes traceable across a project since every skill
reads this doc. New eval. Repo release 2.8.12. Closes #462... (pmm issue).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(product-marketing): clarify typo-fix exception (no version bump or changelog) + ISO dates, per codex

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 12:07:28 -07:00
Corey Haines 286d3718d9 Merge pull request #458 from coreyhaines31/development
release: v2.8.11 — video edit reverse-engineering (beat sheet)
2026-07-15 09:56:22 -07:00
Corey HainesandClaude Fable 5 fdff3dec99 feat(video): reverse-engineer a viral edit into a reusable edit spec (2.1.0) (#457)
* feat(video): reverse-engineer a viral edit into a reusable edit spec (2.1.0)

New references/edit-anatomy.md: decompose a reference edit into a beat
sheet (per-beat table + 3-5 signature moves) across nine edit-anatomy
dimensions, pulled via watch-video/social-fetch, reviewed once, then
executed in Remotion/CapCut/an AI editor. The tool-agnostic decomposition
half of 'copy any viral edit' (Arcads' Omni generation is proprietary).
Originality guardrail: copy editing grammar, never the reference's
footage/script/music. SKILL.md workflow + triggers + eval. Repo release
2.8.11. Closes #456.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(video): soften edit-style IP claim per codex — techniques usually reusable, finished-work reproduction still risky (§102(b)); add SFX/samples

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-15 09:56:13 -07:00
11 changed files with 428 additions and 12 deletions
+2 -2
View File
@@ -6,13 +6,13 @@
},
"metadata": {
"description": "Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, and growth",
"version": "2.8.10",
"version": "2.9.0",
"repository": "https://github.com/coreyhaines31/marketingskills"
},
"plugins": [
{
"name": "marketing-skills",
"description": "47 marketing skills for technical marketers and founders: CRO, copywriting, cold email, prospecting, SEO, AI SEO, paid ads, SMS, ad creative, video production, image generation, co-marketing, churn prevention, pricing, referrals, revenue operations, sales enablement, customer research, site architecture, comprehensive AARRR-structured marketing plans, public relations and earned media, offer design, and more",
"description": "48 marketing skills for technical marketers and founders: CRO, copywriting, cold email, prospecting, SEO, AI SEO, paid ads, SMS, ad creative, video production, image generation, co-marketing, churn prevention, pricing, referrals, revenue operations, sales enablement, customer research, site architecture, comprehensive AARRR-structured marketing plans, public relations and earned media, offer design, and more",
"source": "./"
}
]
+1 -1
View File
@@ -1,7 +1,7 @@
{
"name": "marketing-skills",
"description": "Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, ad creative, and growth",
"version": "2.8.10",
"version": "2.9.0",
"author": {
"name": "Corey Haines"
},
+1
View File
@@ -77,6 +77,7 @@ See each skill's **Related Skills** section for the full dependency map.
| [emails](skills/emails/) | When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email... |
| [free-tools](skills/free-tools/) | When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or... |
| [image](skills/image/) | When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product... |
| [influencer-marketing](skills/influencer-marketing/) | When the user wants to run influencer, creator, or ambassador partnerships to promote their product — finding and... |
| [launch](skills/launch/) | When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user... |
| [lead-magnets](skills/lead-magnets/) | When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the... |
| [marketing-council](skills/marketing-council/) | When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by... |
+14 -2
View File
@@ -24,6 +24,7 @@ Current versions of all skills. Agents can compare against local versions to che
| emails | 2.0.0 | 2026-05-05 |
| free-tools | 2.0.0 | 2026-05-05 |
| image | 2.0.1 | 2026-05-18 |
| influencer-marketing | 1.0.0 | 2026-07-15 |
| launch | 2.0.1 | 2026-06-16 |
| lead-magnets | 2.0.0 | 2026-05-05 |
| marketing-council | 1.0.0 | 2026-07-06 |
@@ -37,7 +38,7 @@ Current versions of all skills. Agents can compare against local versions to che
| paywalls | 2.0.0 | 2026-05-05 |
| popups | 2.0.0 | 2026-05-05 |
| pricing | 2.0.1 | 2026-06-16 |
| product-marketing | 2.0.0 | 2026-05-05 |
| product-marketing | 2.1.0 | 2026-07-16 |
| programmatic-seo | 2.0.0 | 2026-05-05 |
| prospecting | 1.1.0 | 2026-07-13 |
| public-relations | 1.0.0 | 2026-06-10 |
@@ -50,10 +51,21 @@ Current versions of all skills. Agents can compare against local versions to che
| site-architecture | 2.0.0 | 2026-05-05 |
| sms | 1.0.0 | 2026-05-21 |
| social | 2.2.0 | 2026-07-09 |
| video | 2.0.1 | 2026-05-18 |
| video | 2.1.0 | 2026-07-14 |
## Recent Changes
### 2.9.0 (2026-07-15)
- Added **`influencer-marketing`** skill — influencer, creator, and ambassador partnerships end to end. Foundation contributed by @Adi29102000-s (PR #417), expanded to the repo's standard and shipped standalone (the PR's other proposed skills were not included). Covers the **influencer ↔ ambassador spectrum** (paid influencer → affiliate creator → gifting → long-term ambassador program → organic advocate, each with when-to-use and skill handoffs), finding & vetting (audience-alignment test, creator tiers incl. B2B thought leaders, engagement/fake-follower/brand-safety checks), 1:1 outreach (→ cold-email), deal structuring (flat / CPA / hybrid / gifting compensation, rate-as-a-range reality, and the high-ROI content-usage-rights/whitelisting clause → ad-creative), a full **FTC disclosure & compliance section** (material-connection disclosure, clear-and-conspicuous placement, gifting-still-needs-disclosure, platform labels, brand liability, no fabricated claims — a gap in the original contribution), the creative brief (don't script; grounded talking points), measurement & ROI (unique promo codes, UTMs, vanity URLs, post-purchase survey for the branded-search/direct attribution blind spot, whitelisting performance, cost-per-qualified-outcome over EMV/reach), and a structured **ambassador program design** (ask → benefits ladder → recruit-from-evidence → equip → activate → track, cross-referencing community-marketing for community-led advocacy and referrals for payout rails). Six-eval suite covering compensation/whitelisting, podcast attribution, the gifting-disclosure misconception, ambassador-program design, creator vetting, and the no-word-for-word-scripting brief. New skill = repo y release. Total skills: 48.
### 2.8.12 (2026-07-16)
- **product-marketing** (2.0.0 → 2.1.0): the context document now carries its own **version history**. `.agents/product-marketing.md` gets a `Document version:` header (v1, v2 …) and a `## Changelog` section at the bottom — a newest-first, dated, one-line-per-revision paper trail of *what changed and why*. The update flow now reads the current version and recent changelog on open, and on save bumps the version, updates `Last updated`, and prepends a new changelog entry naming the sections touched and the reason (never rewriting past entries; skipped only for pure typo fixes). Since this doc is the shared context every other marketing skill reads, the changelog makes positioning/ICP changes traceable across a project — you can see how the positioning evolved and what a downstream skill was generating against. New eval (id 7) covers the version-bump + prepend-changelog behavior on a repositioning update.
### 2.8.11 (2026-07-14)
- **video** (2.0.1 → 2.1.0): added **reverse-engineering a viral edit into a reusable edit spec** (the tool-agnostic decomposition behind "copy any viral edit" — pattern from Arcads' skill, whose Omni generation model is proprietary/MCP-gated; we build only the decomposition, credited). New `references/edit-anatomy.md`: pull the reference with watch-video (visual/multimodal to read frames + caption style + cut timing) or social-fetch, extract the edit anatomy beat by beat across nine dimensions (shot/framing, cut rhythm/cuts-per-second, on-screen text, caption style, motion/punch-ins, b-roll/overlays, sound design, the first-2s hook, pacing curve), and output a per-beat **beat sheet** table plus a **style summary** of the 3–5 signature moves that make the edit recognizable (patterns over instance-logging). Includes the review-once gate (approve the beat sheet — on-screen text + scene-change placement — before executing in Remotion/Hyperframes, CapCut, or an AI restyle tool) and a hard originality guardrail (copy the editing grammar applied to your own footage/message, never the reference's footage, script, voiceover, or music). SKILL.md adds a Reverse-Engineer a Viral Edit workflow and 'copy this edit,' 'match this video style,' 'reverse-engineer this video,' 'edit like this reference' triggers. New eval (id 7). Closes #456.
### 2.8.10 (2026-07-14)
- **ad-creative** (2.7.0 → 2.8.0): added **AirDrop** as a fourth surface in the iOS-native reveal video ad family (`references/imessage-video-ads.md`, alongside iMessage / ChatGPT / Apple Notes; format popularized by Shiv Sakhuja / Gooseworks' goose-video Airdrop Ads, re-expressed originally — their runtime is MIT but the recipe is private, so this is original craft). The one interaction-native format in the family: the hook is an **incoming AirDrop request** and the **Accept tap is the reveal** — a translucent AirDrop card (sender device name, preview thumbnail, red Decline / blue Accept) from the receiver's POV, where iOS's own accept/decline choice is a built-in micro-conversion beat. New `### AirDrop Reveal` subsection: the preview thumbnail as the hook that must earn the tap, sender-name casting (relatable human name reads native; brand-as-sender reads like an ad), the transfer progress-ring as the signature motion, the AirDrop swoosh sound (not iMessage tritones) with the same CC0-Apple + trade-dress caveat, receiver-POV-default vs sender-POV-flex, and the family grounding/disclosure rules (a dramatization of a share, never a real endorsement). Updates the H1, intro, surface-selection table, and choosing-signal line to four surfaces. SKILL.md pointer names AirDrop and adds the 'AirDrop ad' trigger. New eval (id 11).
+197
View File
@@ -0,0 +1,197 @@
---
name: influencer-marketing
description: "When the user wants to run influencer, creator, or ambassador partnerships to promote their product — finding and vetting partners, structuring deals, briefing creators, disclosure compliance, and measuring ROI. Also use when the user mentions 'influencer marketing,' 'creator partnerships,' 'sponsorships,' 'YouTube sponsorships,' 'podcast sponsorships,' 'brand ambassador,' 'ambassador program,' 'creator program,' 'UGC creators,' 'B2B influencers,' 'thought leader ads,' 'gifting,' 'product seeding,' 'whitelisting creator content,' 'how much to pay an influencer,' or 'FTC disclosure.' For affiliate/referral payout mechanics, see referrals. For community-led advocacy, see community-marketing. For turning creator content into paid ads, see ad-creative."
metadata:
version: 1.0.0
---
# Influencer & Creator Marketing
You are an expert in influencer, creator, and ambassador marketing across B2C (Instagram, TikTok, YouTube) and B2B (LinkedIn, X, newsletters, niche podcasts). Your goal is to help the user pick the right partners, structure fair deals, keep the program compliant, and measure real ROI — not vanity reach.
> Foundation contributed by @Adi29102000-s; compensation benchmarks and run-of-show checklist adapted from @SamSon75's PR; expanded to the repo's standard.
## Before Starting
**Check for product marketing context first.** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or legacy `product-marketing-context.md`), read it before asking questions — the ICP, positioning, and offer anchor every partner-fit decision. Then gather what's missing: goal (awareness / conversions / content / trust), budget and whether it's cash or product, target platform(s), and any brand-safety redlines.
## The Influencer ↔ Ambassador Spectrum
"Influencer marketing" and "ambassador programs" are points on one spectrum — from a one-off paid post to an unpaid long-term advocate. Pick the model that fits the goal and stage, not the buzzword:
| Model | What it is | Pay | Best for | Home |
|---|---|---|---|---|
| **Paid influencer** | A creator posts sponsored content for a fee | Cash (flat / hybrid) | Reach + a credibility borrow, fast | This skill |
| **Affiliate creator** | A creator promotes for commission on sales | Performance (CPA/rev-share) | Conversion at scale, low upfront risk | This skill + **referrals** (payout mechanics) |
| **Gifted / seeding** | Free product, no obligation to post | Product only | Physical DTC, nano/micro, volume | This skill |
| **Brand ambassador program** | A cohort of ongoing advocates (paid, gifted, or perks) posting over months | Mixed / perks | Sustained presence, community depth | This skill (design below) + **community-marketing** |
| **Organic advocate** | A customer who already recommends you unprompted | None | Authenticity, cheapest trust | **community-marketing** |
The further right you go, the more it's about *relationship* than *transaction* — and the cheaper and more durable the trust, but the slower to scale. Most programs blend several (a few paid macro placements for reach + a gifted micro cohort + an affiliate tier for conversion).
## 1. Finding & Vetting Partners
Influence is trust and relevance, not follower count.
**The audience-alignment test.** Don't ask "Are they famous?" Ask "Does their *audience* match our ICP?" A 12k-follower creator whose audience is exactly your buyer beats a 500k generalist. Where you can, look at *their* audience (comments, who engages, any media-kit demographics), not just the creator.
**Creator tiers** (reach vs. trust trade-off):
| Tier | Followers | Character |
|---|---|---|
| **Nano** | 1k–10k | Highest engagement, hyper-niche, often works for gifting. High ROI, low reach. |
| **Micro** | 10k–50k | Best balance of reach and trust; usually paid; strong conversion. |
| **Mid** | 50k–500k | Broader reach, more awareness than conversion, pricier. |
| **Macro / celebrity** | 500k+ | Top-of-funnel awareness; lowest conversion rate per follower; expensive. |
| **B2B thought leader** | Any size | LinkedIn creators, newsletter writers, niche podcasters — small audiences, extreme purchasing power. Judge by *who* follows, not how many. |
For most brands, a portfolio of **micro + nano** partners out-converts one macro placement at the same total spend — and produces more content to repurpose.
**Vetting checklist:**
- **Engagement rate**, not follower count (a rough floor: ~1–3% is healthy on IG/TikTok at scale; higher for nano). Suspiciously round numbers, comment pods, or comments that don't match the audience are red flags.
- **Fake-follower / bot check** — a sudden follower spike, generic comments, or engagement wildly out of line with reach. Tools like SparkToro (audience intelligence) help; media kits overstate.
- **Sponsored-content track record** — do their *ads* still get engagement, or does their audience tune out promos? Ask for past campaign results.
- **Brand safety** — scroll their last ~3 months. Controversy, competitor conflicts, or off-brand content that would attach to you.
- **Authenticity of fit** — have they mentioned your category unprompted? A genuine user is worth several cold partners.
## 2. Outreach
Reach out **1:1 and personally** — reference specific content, why *them*, and what's in it for their audience. A generic form blast to 200 creators converts worse than 20 tailored notes. For writing the outreach itself, use **cold-email** (personalization, deliverability, follow-up cadence). Lead with the offer and the fit; don't bury the ask.
## 3. Structuring the Deal
Move beyond "pay for a post."
**Compensation models:**
- **Flat fee** — standard for awareness; you pay for the placement regardless of result.
- **Performance / CPA** — pay per click or conversion. Hard to get larger creators to accept without a baseline; best with affiliate-minded creators (see **referrals** for tracking + payout).
- **Hybrid (flat + CPA)** — usually the best deal: a lower baseline to cover their production time, plus commission for upside. Aligns incentives.
- **Gifting / seeding** — free product, no obligation. Works for physical DTC with nano/micro at volume; expect a low but authentic post rate.
**Rate reality:** published "rates" are wildly variable by niche, geography, and platform, and creators quote high. Treat any benchmark as a *range to negotiate from*, not a price — and anchor on **cost per qualified outcome** (CPA, cost per qualified follower/lead), not cost per post. A cheap post to the wrong audience is the expensive one.
**Starting ranges for a single post** (negotiation anchors, *not* fixed prices — aligned to the tiers above):
| Tier | Single post (rough range) | Notes |
|---|---|---|
| **Nano** (1k–10k) | Free product – $100 | Often product-only |
| **Micro** (10k–50k) | $100 – $1,500 | Widest range; negotiate on engagement, not follower count |
| **Mid** (50k–500k) | $1,500 – $10,000 | Rate cards common at this tier |
| **Macro / celebrity** (500k+) | $10,000 – $30,000+ | Usually has an agent/manager |
| **Video / long-form** (YouTube) | Higher than short-form at the same follower count | More production effort |
| **B2B thought leader** | Priced on audience quality, not size | A 5k-follower niche voice can command more than a 200k generalist |
Ask for their **rate card first** — it sets an anchor you respond to rather than naming a number blind.
**Deliverables to negotiate:**
- **Content usage rights (crucial)** — the right to repurpose their content as **paid ads** (whitelisting / dark posting / "creator ads") for a defined window (commonly 3–6 months). This is often the highest-ROI clause: their content becomes your best-performing ad. Then run it through **ad-creative** (and present variations for sign-off with the creative review page).
- **Exclusivity** — competitor lockout for a set period; costs more, worth it in tight categories.
- **Format & specifics** — dedicated video vs. a 60-second integration; number of posts; stories vs. feed; posting window; approval rights; how long it stays up.
- **Approvals & revisions** — one review round is normal; scripting word-for-word is not (below).
Put it in a simple written agreement: deliverables, timing, usage rights, exclusivity, disclosure obligation (below), payment terms, and a kill/rework clause.
## 4. Disclosure & Compliance (non-negotiable)
Influencer marketing has hard legal requirements — this is the part most brands under-do, and the brand — not just the creator — can be held liable.
- **Any material connection must be disclosed** — payment, free product, commission, a family/employee relationship, even a free trial. Gifting is *not* a loophole; a gifted post still needs disclosure.
- **The disclosure must be clear and hard to miss** — "#ad" or "#sponsored" placed where viewers actually see it (not buried in a wall of hashtags, not below the "more" fold, and spoken aloud in video/audio, not just in the description). "#sp," "#collab," "#ambassador," and "thanks to [brand]" are considered insufficient on their own by the FTC.
- **Use the platform's own tool** — Instagram/TikTok/YouTube "paid partnership" labels *in addition to* the written disclosure, not instead of it.
- **You're responsible for your creators.** Build the disclosure requirement into the brief and the agreement, and check that they actually did it. Non-disclosure exposes the brand to liability, not just the creator — the FTC expects advertisers to have a program to guide, monitor, and remediate disclosure (FTC actions target advertisers).
- **No fabricated claims.** Creators can't say things about the product that aren't true, can't fake results, and can't imply they're a customer if they aren't. Give them what's true and let them speak it in their voice.
- **International + platform rules vary** (e.g., stricter regimes in the UK/EU, category rules for health/finance/alcohol). When the campaign is regulated or cross-border, route to legal.
Disclosure done well doesn't hurt performance — audiences expect it, and the FTC has never found "#ad" to tank a genuinely good integration.
## 5. The Creative Brief
Do **not** script the creator word-for-word — they know their audience better than you, and scripted reads convert worst. Provide:
- **The "why"** — the core problem your product solves (the one sentence).
- **Key talking points (2–3 max)** — the most important benefits; more than three and none land.
- **The CTA** — exactly what to tell the audience to do (a specific vanity link, a unique promo code).
- **Guardrails** — what *not* to say (don't promise features that don't exist), the disclosure requirement, and any brand redlines.
- **Creative freedom** — explicitly grant it. The integration should live inside their normal content style.
Ground the talking points in real proof (reviews, results) — same grounding discipline as **ad-creative**'s inputs. Never hand a creator a claim you can't back.
## 6. Measurement & ROI
Influencer marketing suffers from attribution gaps — fix them upfront, before the campaign runs:
- **Unique promo codes** (e.g., `CREATOR20`) — the easiest direct-conversion tracker, and essential for podcasts/video where links aren't clickable.
- **UTM tracking links** — mandatory on every digital placement; one per creator per placement.
- **Vanity / dedicated landing pages** — `yourdomain.com/creatorname` with a personalized welcome; lifts conversion *and* attributes cleanly.
- **Post-purchase survey** — "How did you hear about us?" catches the halo/branded-search effect that promo codes and last-click miss (much of influencer impact shows up later as branded search and direct — see the attribution blind spot in **ai-seo**'s citations-vs-recommendations).
- **Whitelisting performance** — when you repurpose creator content as ads, that ad's own metrics are a clean read on the creative's real pull.
Judge the program on **cost per qualified outcome and repeat/retained value**, not reach, likes, or "EMV" (earned media value is a vanity number). One nano creator driving 40 real buyers beats a macro placement with a million muted views.
## Ambassador Program Design
When you want *sustained* presence rather than one-off posts, design a program (this is the structured, paid/perks version of community-marketing's advocate program):
1. **Define the tier(s) and the ask** — e.g., 2 posts/month + 1 event; keep it light enough to sustain.
2. **Build the benefits ladder** — perks that scale with contribution: early access, free/ongoing product, commission (via **referrals**), exclusive swag, revenue share, public recognition, a private channel. Meaningful beats "early access to features."
3. **Recruit from evidence** — start with people already advocating unprompted (reviews, mentions, community — mine via **customer-research**); a personal 1:1 ask, never a form.
4. **Equip them** — referral/affiliate links, shareable assets, 2–3 talking points, the disclosure requirement, a private Slack/Discord.
5. **Activate on a cadence** — give them something to post about monthly (launches, milestones, challenges); a program with nothing to do dies.
6. **Track and iterate** — attributed traffic/signups per ambassador (codes + links), and double down on the top decile; graduate strong ambassadors to paid partnerships.
For the community-led, unpaid advocate end of this (badges, recognition, community support), hand off to **community-marketing**; for the affiliate payout rails, **referrals**.
## Common Mistakes
- **Chasing follower count over audience fit** — reach to the wrong people is the most expensive spend there is.
- **Skipping disclosure** — a brand-liability risk, and audiences trust disclosed content more than they distrust it.
- **Scripting the creator** — kills the authenticity you're paying for; brief, don't dictate.
- **Not securing usage rights** — you lose the biggest ROI lever (whitelisting their content into paid ads).
- **No attribution plan** — codes, UTMs, vanity URLs, and the post-purchase survey must exist *before* launch, not after.
- **One-and-done** — the second post from the same creator usually outperforms the first (their audience has seen you before); build relationships, not transactions.
- **Judging on EMV / reach** — measure cost per qualified outcome.
- **Ignoring nano/micro** — a portfolio of small, aligned creators usually beats one big name at the same budget.
## Run-of-Show Checklist
### Sourcing
- [ ] Define the ICP overlap you're looking for, not just follower count
- [ ] Shortlist 10–20 creators across at least two tiers (weight toward micro + nano)
- [ ] Check engagement rate and comment quality for each; run the fake-follower check
### Outreach & Deal
- [ ] Personalize outreach with a specific reference to their content
- [ ] Agree deliverables, timeline, and compensation type in writing
- [ ] Lock **usage rights** (paid-ad whitelisting window) and exclusivity terms
- [ ] Put the disclosure requirement in the agreement
### Execution
- [ ] Send a brief with the "why," 2–3 talking points, the CTA, and what to avoid
- [ ] Set up tracking (unique code, UTM, or vanity URL) *before* content goes live
- [ ] Review the draft if you have approval rights — without over-scripting
- [ ] Confirm the disclosure actually shipped where viewers can see it
### Post-Campaign
- [ ] Pull performance against the goal set upfront (cost per qualified outcome)
- [ ] Share results with the creator — it builds the relationship
- [ ] Decide: one-off, repeat, or move to a retainer / ambassador program
## Tool Integrations
For implementation, see the [tools registry](../../tools/REGISTRY.md).
| Tool | Best for | Guide |
|------|----------|-------|
| **SparkToro** | Audience intelligence — where your ICP actually pays attention, and vetting a creator's real audience | [sparktoro.md](../../tools/integrations/sparktoro.md) |
Dedicated creator-discovery/CRM platforms (e.g., Modash, GRIN, Aspire, Upfluence) and creator-sponsorship marketplaces (e.g., Passionfroot) are the category to reach for at scale; add the specific one to the registry when the user adopts it. For pulling a specific creator's recent posts to vet them, use `social-fetch`; for analyzing their content style, `watch-video`.
## Related Skills
- **referrals** — affiliate/commission tracking and payout rails (the performance side of creator deals)
- **community-marketing** — community-led advocacy and the unpaid advocate program
- **ad-creative** — repurpose creator content into paid ads (whitelisting); creative review page for sign-off
- **cold-email** — the creator outreach itself (personalization, deliverability, follow-up)
- **customer-research** — find existing advocates and ground the talking points
- **ai-seo** — the branded-search/direct attribution blind spot that hides influencer impact
- **social** — organic content strategy the partnerships plug into
@@ -0,0 +1,76 @@
{
"skill_name": "influencer-marketing",
"evals": [
{
"id": 1,
"prompt": "We want to sponsor a big YouTuber with 1M subs. Should we just pay their flat rate?",
"expected_output": "Should advise against just paying a flat rate without negotiation. Should recommend the hybrid compensation model (lower flat fee + performance upside). Should explicitly recommend negotiating content usage rights (whitelisting/dark posting) so the video can be repurposed as a paid ad. Should warn that macro-influencers have lower conversion rates per follower and suggest that a portfolio of micro/nano creators may out-convert one macro placement at the same budget. Should require FTC disclosure in the deal.",
"assertions": [
"Recommends hybrid compensation model over a bare flat fee",
"Highlights securing content usage rights / whitelisting",
"Warns about macro-influencer conversion rates and suggests micro/nano portfolio",
"Requires clear FTC disclosure"
],
"files": []
},
{
"id": 2,
"prompt": "How do we make sure we can track ROI from podcast sponsorships?",
"expected_output": "Should recommend multiple attribution methods set up before launch. Must mention unique promo codes (critical for audio where links aren't clickable). Should suggest dedicated vanity URLs / landing pages and UTM links. Should recommend a post-purchase 'how did you hear about us?' survey to catch the halo/branded-search effect that direct attribution misses. Should steer judging on cost per qualified outcome rather than reach or EMV.",
"assertions": [
"Recommends unique promo codes",
"Recommends vanity URLs / dedicated landing pages and UTMs",
"Recommends a post-purchase survey for the attribution blind spot",
"Judges ROI on cost per qualified outcome, not reach/EMV"
],
"files": []
},
{
"id": 3,
"prompt": "We're just gifting free product to creators — no payment — so we don't need them to say #ad, right?",
"expected_output": "Should correct the misconception firmly: gifting is a material connection and a gifted post STILL requires clear disclosure. Should explain the disclosure must be clear and conspicuous (visible placement, spoken in video/audio, not buried in hashtags), that platform 'paid partnership' labels are in addition to not instead of it, and that the brand — not just the creator — is liable for non-disclosure. Should recommend building the disclosure requirement into the brief and agreement and verifying it happened.",
"assertions": [
"States gifting still requires disclosure (not a loophole)",
"Describes clear-and-conspicuous placement (not buried in hashtags; spoken in video)",
"Notes brand liability for creator non-disclosure",
"Recommends putting disclosure in the brief/agreement and verifying it"
],
"files": []
},
{
"id": 4,
"prompt": "I want to build a long-term brand ambassador program for our DTC skincare brand, not just one-off posts.",
"expected_output": "Should apply the ambassador-program design (the sustained end of the spectrum): define a light, sustainable ask; build a benefits ladder that scales with contribution (early access, product, commission, recognition); recruit from evidence (existing unprompted advocates found via reviews/community) with a personal 1:1 ask rather than a form; equip ambassadors with links, assets, talking points, disclosure requirement, and a private channel; activate on a monthly cadence; and track attributed results per ambassador (codes + links), doubling down on top performers. Should cross-reference referrals for affiliate payout rails and community-marketing for the community-led/unpaid end, and require disclosure.",
"assertions": [
"Applies structured ambassador-program design (ask, benefits ladder, recruit, equip, activate, track)",
"Recruits from existing advocates with a personal ask, not a mass form",
"Sets up per-ambassador attribution and iterates on top performers",
"Cross-references referrals (payout) and/or community-marketing (community advocacy)"
],
"files": []
},
{
"id": 5,
"prompt": "This creator has 500k followers but I'm worried some are fake. How do I vet them before we pay?",
"expected_output": "Should focus vetting on audience quality and fit over follower count: check engagement rate relative to followers (flagging suspiciously low or padded engagement, comment pods, generic comments, sudden follower spikes), assess whether their audience matches the ICP (not just size), review sponsored-content track record (do their ads still get engagement), and scroll recent content for brand safety. Should note media kits overstate and suggest audience-intelligence tooling (e.g., SparkToro) and pulling their recent posts (social-fetch) to inspect real engagement. Should frame audience alignment as more important than reach.",
"assertions": [
"Prioritizes engagement quality + audience fit over follower count",
"Flags fake-follower / engagement-pod signals to check",
"Checks sponsored-content track record and brand safety",
"Suggests audience-intelligence tooling / inspecting real recent posts"
],
"files": []
},
{
"id": 6,
"prompt": "Write me a word-for-word script for the influencer to read.",
"expected_output": "Should push back on word-for-word scripting (it kills the authenticity being paid for and converts worst) and instead provide a creative brief: the one-sentence 'why,' 2-3 key talking points max, the exact CTA (vanity link / promo code), guardrails (what not to say, disclosure requirement, brand redlines), and explicit creative freedom to integrate it in their own style. Talking points must be grounded in real proof, not invented claims.",
"assertions": [
"Declines to script word-for-word and explains why",
"Provides a brief structure (why, 2-3 talking points, CTA, guardrails, creative freedom)",
"Includes the disclosure requirement and grounded (non-fabricated) talking points"
],
"files": []
}
]
}
+19 -5
View File
@@ -2,7 +2,7 @@
name: product-marketing
description: "When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context."
metadata:
version: 2.0.0
version: 2.1.0
---
# Product Marketing Context
@@ -18,9 +18,10 @@ The document is stored at `.agents/product-marketing.md`.
First, check if `.agents/product-marketing.md` already exists. Also check `.claude/product-marketing.md` and the legacy filename `product-marketing-context.md` (in either `.agents/` or `.claude/`) for older setups — if found anywhere other than `.agents/product-marketing.md`, offer to move it to the canonical location.
**If it exists:**
- Read it and summarize what's captured
- Read it and summarize what's captured — note its current **Document version** and the last few **Changelog** entries so the user sees where the doc stands and what's changed recently
- Ask which sections they want to update
- Only gather info for those sections
- On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of *what changed and why* is worth keeping.
**If it doesn't exist, offer two options:**
@@ -133,7 +134,8 @@ After gathering information, create `.agents/product-marketing.md` with this str
```markdown
# Product Marketing Context
*Last updated: [date]*
**Document version:** v1
**Last updated:** [date]
## Product Overview
**One-liner:**
@@ -219,16 +221,28 @@ After gathering information, create `.agents/product-marketing.md` with this str
**Business goal:**
**Conversion action:**
**Current metrics:**
## Changelog
*Newest first. One line per revision: what changed and why.*
- v1 ([date]) — Initial context.
```
---
## Step 4: Confirm and Save
## Step 4: Confirm, Version, and Save
- Show the completed document
- Ask if anything needs adjustment
- **Set the version and changelog** — this is the paper trail for a doc every other skill reads:
- **New document:** set `Document version: v1` and a single Changelog entry — `- v1 ([today]) — Initial context.`
- **Updating an existing document:** increment the version (v2 → v3 …), update `Last updated` to today, and **prepend a new Changelog entry** at the top of the list (newest first) summarizing *what changed and why* in one line. Never rewrite or reorder past entries.
- A good entry names the sections touched and the reason, not "updated the doc." Examples:
- `- v3 (2026-07-16) — Repositioned from "email tool" to "deliverability platform"; added RevOps to the ICP.`
- `- v2 (2026-06-02) — Rewrote value prop and objections after 5 customer interviews; added competitor Acme.`
- Use today's date in ISO form (YYYY-MM-DD) for the entry and `Last updated`.
- **Pure typo-only fix:** don't bump the version or add a changelog entry — just save the correction. Every other change bumps the version and gets an entry. When the change is a real repositioning, say so plainly — downstream skills will now generate against the new context.
- Save to `.agents/product-marketing.md`
- Tell them: "Other marketing skills will now use this context automatically. Run `/product-marketing` anytime to update it."
- Tell them: "Other marketing skills will now use this context automatically. The Changelog at the bottom tracks every revision — check it to see how your positioning has evolved. Run `/product-marketing` anytime to update it."
---
+13
View File
@@ -80,6 +80,19 @@
"Does not attempt to write homepage copy using context creation patterns"
],
"files": []
},
{
"id": 7,
"prompt": "We just repositioned — we're no longer an 'email tool,' we're a 'deliverability platform,' and our ICP now includes RevOps teams. Update our product marketing context.",
"expected_output": "Should recognize an existing .agents/product-marketing.md, read it, note its current Document version and recent Changelog entries, and update only the affected sections (product overview/positioning, target audience/ICP). On save, should bump the Document version (e.g. v2 → v3), update the Last updated date, and PREPEND a new newest-first Changelog entry summarizing what changed and why in one line — e.g. 'Repositioned from email tool to deliverability platform; added RevOps to the ICP' — naming the sections touched and the reason, not just 'updated the doc.' Should not rewrite or reorder past changelog entries. Should tell the user the changelog tracks revisions and that downstream skills will now use the new context.",
"assertions": [
"Reads the existing doc and surfaces its current version + recent changelog",
"Updates only the affected sections (positioning + ICP)",
"Bumps the Document version and updates Last updated",
"Prepends a newest-first changelog entry naming what changed and why",
"Preserves prior changelog entries unchanged"
],
"files": []
}
]
}
+6 -2
View File
@@ -1,8 +1,8 @@
---
name: video
description: "When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative."
description: "When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' 'copy this edit,' 'match this video style,' 'reverse-engineer this video,' 'edit like this reference,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative."
metadata:
version: 2.0.1
version: 2.1.0
---
# Video
@@ -244,6 +244,10 @@ CapCut: Add captions, effects, platform styling
Distribute: TikTok, Reels, Shorts, LinkedIn
```
### Reverse-Engineer a Viral Edit
To replicate the *style* of a video edit you admire — the cut rhythm, caption treatment, punch-ins, on-screen text, sound design — decompose it into a reusable **edit spec** (a beat sheet) and apply it to your own footage. Pull the reference with **watch-video** (visual/multimodal mode extracts frames at the cut points) or **social-fetch**, extract the edit anatomy beat by beat, and output a per-beat table plus the 3–5 signature moves that make the edit recognizable. Review the beat sheet once before executing it (in Remotion/Hyperframes, CapCut, or an AI restyle tool). Copies the editing grammar, never the reference's footage/script/music. Full method: [references/edit-anatomy.md](references/edit-anatomy.md).
---
## Video Production Workflows
+15
View File
@@ -83,6 +83,21 @@
"Asks about stack or animation needs"
],
"files": []
},
{
"id": 7,
"prompt": "There's a TikTok edit style I love — fast cuts, one-word captions that pop, a whoosh on every scene change. I have my own talking-head clip. Break down how that edit works so I can replicate the style. Here's the reference: [link]",
"expected_output": "Should apply references/edit-anatomy.md (reverse-engineer the edit into a reusable spec), not just describe it. Should pull the reference with watch-video (visual/multimodal to read frames + caption style + cut timing) or social-fetch — not qualify from the transcript alone. Should extract the edit anatomy beat by beat across the dimensions (shot/framing, cut rhythm/cuts-per-second, on-screen text content+placement+timing, caption style, motion/punch-ins, b-roll/overlays, sound design, the first-2s hook, pacing curve) and output BOTH a per-beat beat-sheet table AND a short style summary of the 3-5 signature moves. Should emphasize patterns over instance-logging. Should present the beat sheet for a review-once approval (does the on-screen text say what you want; do scene changes land where you want) before executing, and note the spec can be executed in Remotion/Hyperframes, CapCut, or an AI restyle tool. Should apply the originality guardrail: copy the editing grammar applied to the user's own footage/message, never the reference's footage, script, voiceover, or music.",
"assertions": [
"Applies the edit-anatomy reverse-engineering method, not a plain description",
"Pulls the reference with watch-video/social-fetch to read the actual frames, not just the transcript",
"Extracts the edit anatomy across the dimensions and expresses patterns (not a raw list of cut timestamps)",
"Outputs a per-beat beat sheet AND a style summary of the signature moves",
"Presents the beat sheet for a review-once approval before executing",
"Notes execution paths (Remotion/Hyperframes, CapCut, or AI restyle tool)",
"Applies the originality guardrail — copies editing grammar applied to the user's own footage, never the reference's footage/script/music"
],
"files": []
}
]
}
+84
View File
@@ -0,0 +1,84 @@
# Reverse-Engineering an Edit (The Beat Sheet)
A viral short-form video usually isn't winning on the footage — it's winning on the *edit*: the cut rhythm, the caption style, the punch-ins, the on-screen text landing on the exact word, the b-roll cutaways, the sound design. This reference turns a reference edit you admire into a **reusable edit spec** — a beat sheet you (or an editing tool) can execute against your own footage — without copying a single frame of theirs.
This is the tool-agnostic half of "copy any viral edit": the *decomposition*. The generation is whatever you edit with afterward — CapCut, Premiere, Remotion/Hyperframes, or an AI restyle tool. The spec is the deliverable.
## When to use it
- A competitor's or creator's edit keeps stopping your scroll and you want to understand *why* and replicate the technique
- You have raw footage (a talking-head clip, a demo) and a reference edit whose style you want to match
- You're briefing an editor or a template and need the edit decisions written down, not vibes
Don't use it to copy someone's actual creative — this extracts the *editing grammar* (structure, rhythm, caption treatment), not the script, footage, or brand. Same rule as mining organic content for vocabulary in the hook system: take the technique, never the creative.
## Step 1 — Pull the reference so you can actually read the edit
You cannot decompose an edit from a description of it. Get the frames and the timing:
- **watch-video** (visual or multimodal mode) — extracts the transcript *and* samples frames at the cut points, so you can read on-screen text, caption style, and shot changes. This is the primary tool.
- **social-fetch** — pull the post for the caption, engagement, and the media URL when the reference is a specific tweet/Reel/TikTok.
- Screenshots of key frames also work if the user supplies them — you need the visual, not just the words.
Note the total duration and roughly how many cuts there are before you start — cuts-per-second is the single most telling number about an edit's energy.
## Step 2 — Extract the anatomy, beat by beat
Walk the reference from 0:00 and log every editing decision. The dimensions that define a short-form edit:
| Dimension | What to read off the reference |
|---|---|
| **Shot & framing** | Talking head / screen recording / b-roll / text card; close-up vs. wide; headroom, rule-of-thirds, or dead-center |
| **Cut rhythm** | Where each cut lands and how fast (cuts-per-second); is it on the beat, on the word, or on the breath? |
| **On-screen text** | The words, when each appears/disappears, and *where* on the frame (top-third caption vs. big centered statement) |
| **Caption style** | Font, weight, color, outline/box, and animation (word-by-word pop, karaoke highlight, whole-line) |
| **Motion** | Punch-ins / zoom pushes, shakes, whip-transitions, speed ramps — where and how aggressive |
| **B-roll & overlays** | Cutaways, stickers, arrows, emoji, screenshots, meme inserts — what's laid over the base footage and when |
| **Sound design** | Music choice and where it hits, SFX (whooshes, dings, risers), and deliberate silence before a beat |
| **Hook (first 2s)** | The single most-copied element — what's on screen and said in the opening two seconds, before anyone's committed |
| **Pacing curve** | Does it stay frantic, or fast-hook → slower-body → fast-CTA? Map the energy over the runtime |
Read the *pattern*, not just the instances: "a hard cut + punch-in on every new sentence," "caption is one word at a time, yellow, karaoke-highlighted, bottom third," "a whoosh SFX on every scene change." Patterns are what make an edit replicable; a list of 40 individual cuts is not.
## Step 3 — Write the beat sheet
Two artifacts: a per-beat table and a short style summary.
**The beat sheet** — one row per beat (a beat = a cut or a distinct edit event):
```
| Beat | Time | Shot | On-screen text | Caption style | Transition / motion | Audio |
|------|-----------|-----------------|-----------------------|----------------------|-----------------------|------------------|
| 1 | 0:00–0:02 | CU talking head | "STOP doing this" | word-pop, yellow, ctr| hard in, slow push | music in + riser |
| 2 | 0:02–0:04 | screen record | (caption only) | karaoke, white, btm | hard cut + whoosh | click SFX |
| … | | | | | | |
```
**The style summary** — the 3–5 *signature moves* that make this edit recognizable, stated so they're reusable:
- e.g. "Every sentence gets a hard cut + a 5% punch-in." / "Captions are one word at a time, bottom-third, karaoke-highlighted." / "A whoosh SFX on every cut; music drops out for 0.5s before the CTA." / "The hook is a bold centered statement on frame 1, no logo."
The signature moves are the real deliverable — someone can apply those five rules to any footage and get the style. The table is the detailed backup.
## Step 4 — Review once, then execute
Show the beat sheet before anyone edits anything — the same review-once gate as the ad-creative creative review page. The reviewer checks two things:
- **The on-screen text says what you want** (mapped to your message, not the reference's)
- **The scene changes land where you want them** (your footage's beats, not a blind copy of the reference's timing)
Approve, then execute the spec with your footage:
- **Remotion / Hyperframes** — when you want the edit templated and data-driven (see the programmatic-video section in SKILL.md); the beat sheet *is* the composition spec.
- **CapCut / Premiere / an editor** — hand off the beat sheet + style summary as the brief.
- **An AI restyle tool** — feed the style summary as the target style.
## Originality guardrail
You are copying the *edit*, not the content. The beat sheet describes technique (cut rhythm, caption treatment, motion, sound design) applied to **your** footage and **your** message. General editing techniques and style cues are usually reusable — U.S. copyright protects expression, not procedures or methods (17 U.S.C. §102(b)) — but the reference's specific creative expression is not, and closely reproducing a finished video's exact selection and arrangement of choices can still create risk. So copy the grammar, not the finished work: use your own footage, message, script, voiceover, licensed music/SFX/samples, and brand elements. If the reference's "style" is really a specific bit or sketch, that's their creative — draw inspiration, don't reproduce it.
## Common mistakes
- **Describing instead of reading** — you can't extract caption style or cut timing from the transcript alone; pull the frames (watch-video).
- **Logging instances, not patterns** — 40 cut timestamps isn't a spec; "hard cut + punch-in per sentence" is.
- **Copying the reference's timing onto different footage** — beats land on *your* words and *your* cuts; the reference gives you the grammar, not the calendar.
- **Skipping the hook** — the first 2 seconds carry most of the retention; decode them in the most detail.
- **Reproducing the creative** — matching the edit is fine; re-shooting their exact bit, script, or using their footage/music/SFX is not.