Loading
Use when the user asks to "create an influencer brief" or "write a campaign brief"; produces a structured creator brief with deliverables, key messages, creative direction, timeline, disclosure rules,
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add aaron-he-zhu/aaron-marketing-skills --skill brief-generator -a cursor -y
Use when the user asks to "create an influencer brief" or "write a campaign brief"; produces a structured creator brief with deliverables, key messages, creative direction, timeline, disclosure rules, and compensation terms. Not for choosing how to split spend across creators — use budget-optimizer. 达人合作简报/创作者BF
Use when the user asks to "create an influencer brief" or "write a campaign brief"; produces a structured creator brief with deliverables, key messages, creative direction, timeline, disclosure rules, and compensation terms. Not for choosing how to split spend across creators — use budget-optimizer. 达人合作简报/创作者BF
This skill helps you create clear, comprehensive influencer briefs that set creators up for success. Good briefs lead to better content, fewer revisions, and stronger partnerships.
Shortest invocation:
Create an influencer brief for [campaign]
Common scenario:
Generate a TikTok brief for micro-influencers promoting [product], 1 review video, with disclosure and timeline
creator_ref, brand_ref, page_ref, shipping_ref, contact_ref, brand_asset_ref, hashtag_ref, promo_code_ref, and (when voice is used) voice_source_ref; plus memory/projections/narrative.json, memory/projections/claims.json, and relevant creator/channel projections. HOT is only an index to those sources. Raw creator/brand names and handles, page/asset-folder URLs, shipping addresses, contact names/emails/phones, hashtags, promo codes, and voice-source locators are transient rendering/dispatch inputs only.memory/influencer/brief-generator/YYYY-MM-DD-<topic>.md only with exact authorization. Saved artifacts and handoffs represent creator, brand, landing destination, shipping destination, contact path, assets, hashtags, promo terms, and voice provenance only with creator_ref, brand_ref, page_ref, shipping_ref, contact_ref, brand_asset_ref, hashtag_ref, promo_code_ref, and voice_source_ref; never persist their raw identity/address/URL/contact/content values or a hidden mapping. Each unresolved-claim proposal is a separate exact operation: propose authorization; a brief-save approval does not cover it.Emit the standard shape from skill-contract.md §Handoff Summary Format, including the Narrative/claims dependency tuple.
Required fields: narrative_canon_id, narrative_canon_version, claims_projection_offset, and dependency_status: verified | approved-fallback | blocked, plus the applicable opaque creator_ref, brand_ref, page_ref, shipping_ref, contact_ref, brand_asset_ref, hashtag_ref, promo_code_ref, and voice_source_ref values. Do not include their raw resolved values.
This family has no live integrations required (Tier 1). The skill works end to end by asking the user for inputs: campaign details, deliverables, key messages, timeline, and compensation. Provide those in the prompt and you get a complete brief with zero setup.
Optional connectors that can enrich a brief when available:
~~influencer database — resolve creator details transiently for personalization while retaining only creator_ref and opaque evidence refs in the saved brief/handoff.~~social platform analytics — confirm current format specs and best-performing post lengths per platform.~~CRM — fetch the assigned contact_ref and prior brief versions; resolve raw contact details only during an authorized dispatch.Read accepted Narrative and claims projections before drafting. Claim approval is contextual: audience, market, media, offer window, and required disclaimer must match. No usable canon permits only an explicitly approved exploratory brief, never a creator-ready/on-canon label.
See CONNECTORS.md for the verified free/keyless recipe per category. None are required.
When a user requests a brief:
creator_ref, brand_ref, page_ref, shipping_ref, contact_ref, and voice_source_ref; resolve HOT pointers to their actual source records. Read Narrative/claims projections at named offsets. Keep raw identity, page, address, contact, and voice-source locators transient. If creator voice is required, capture the reference-safe intake via creator-voice-intake.md.[needs source], offer an exact registry-events.py operation: propose request for separate authorization, and prevent creator-ready status until resolved.Send, “deliver,” or “share with creators” request/label creates only a pending outreach handoff; it does not authorize delivery. Hand the brief to outreach-manager, resolve raw recipient/brand/page/contact values only transiently inside the delivery job, and pass its exact single-touch gate: independently approve the exact recipient_ref, channel, final rendered message/brief payload, and one concrete ISO-8601 dispatch_at plus timezone when scheduled, then run fresh eligibility and live-suppression checks immediately before the provider call. Any changed recipient, channel, payload, or schedule requires new approval.Disclosure and usage rights must be stated explicitly — never leave them as placeholders once the user has given input. Briefs are guidelines, not scripts: respect the creator's voice while pinning the key messages and compliance terms.
User: "Create a brief for our organic protein powder: 1 IG Reel + 1 TikTok, morning-routine/workout-fuel angles, approved clean-label claims, draft due 15 Sep, go-live 22 Sep, $1,200 fee, and 12-month repost/paid rights in the US."
Output: Complete reference-safe inline brief using the supplied claims, deliverables, dates, fee, territory, and rights scope, with dated official platform specs or TBD/NEEDS_INPUT. Offer the exact memory/influencer/brief-generator/YYYY-MM-DD-<topic>.md path; do not claim it was saved without exact authorization. Saving or a Send label never authorizes delivery; outreach resolves the raw render only after its separate exact send gate.
Termination note: Maintain a visited-set. If a recommended skill was already invoked this session, stop and report chain-complete instead of re-running it. Cap any handoff chain at max-depth 3.