aaron-he-zhu/brief-generator
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
npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill brief-generator
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
memory/projections/narrative.json, memory/projections/claims.json, and relevant creator/channel projections; HOT is only an index to those sources.memory/influencer/brief-generator/YYYY-MM-DD-<topic>.md; unresolved claims become authorized claims proposals.> 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.
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 — pull creator handles, audience size, and past collaboration notes to personalize the "Why You" section.~~social platform analytics — confirm current format specs and best-performing post lengths per platform.~~CRM — fetch the assigned point of contact and prior brief versions for an ambassador.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:
[needs source], submit it through registry-events.py as an authorized operation: propose event, and prevent creator-ready status until resolved.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 micro-influencers to promote our new organic protein powder on Instagram and TikTok"
Output: Complete brief — messaging around organic ingredients and clean label, deliverables of 1 IG Reel + 1 TikTok video with platform specs, creative direction for "morning routine" / "workout fuel" angles, timeline with draft + go-live dates, #ad disclosure at caption start, and 12-month repost/paid usage rights. Saved to memory/influencer/brief-generator/.
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.
Take aaron-he-zhu/brief-generator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.