Best for
- Use when the agent doesn't know which skill to run, the user is vague about what they need, there are multiple valid marketing paths, or someone says 'I don't know where to start', 'what should we market', 'explore appr…
MoizIbnYousaf/marketing-cli/skills/brainstorm/SKILL.md
Structured marketing brainstorming when direction is unclear. Use when the agent doesn't know which skill to run, the user is vague about what they need, there are multiple valid marketing paths, or someone says 'I don't know where to start', 'what should we market', 'explore approaches', 'help me think through this', 'marketing ideas', 'what campaign should I run', 'where do I start with marketing', 'what's our marketing plan', or 'I have no idea how to promote this'. Explores 2-3 approaches an
Decision brief
Structured exploration when marketing direction is unclear. You produce a brief that tells /cmo where to route next.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill "skills/brainstorm"Inspect the Agent Skill "brainstorm" from https://github.com/MoizIbnYousaf/marketing-cli/blob/f12fbcbe4929584697b309b9096c9427b0cfce8e/skills/brainstorm/SKILL.md at commit f12fbcbe4929584697b309b9096c9427b0cfce8e. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Gate check. If the request is already specific, skip brainstorming:
Ask ONE question at a time. Prefer multiple choice when natural options exist. Skip questions already answered by brand/ context.
Present 2-3 concrete strategic directions. For each:
Write a structured brief to marketing/brainstorms/YYYY-MM-DD--brainstorm.md:
After writing the brief:
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 86/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 27 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Structured exploration when marketing direction is unclear. You produce a brief that tells /cmo where to route next.
For brand memory protocol, see /cmo rules/brand-memory.md.
brand/ files if they exist (voice-profile.md, audience.md, positioning.md, learnings.md). They enhance but never gate.Gate check. If the request is already specific, skip brainstorming:
| Signal | Action |
|---|---|
| "Write a landing page for X" | Skip. Route to direct-response-copy. |
| "Do SEO for my blog" | Skip. Route to keyword-research. |
| "I want to market my app" | Proceed. Multiple valid paths. |
| "What should I do next?" | Proceed. No clear direction. |
| "Help me think through our launch" | Proceed. Needs exploration. |
If skipping: "Your request is specific enough to execute directly. Routing to /<skill> instead of brainstorming."
Ask ONE question at a time. Prefer multiple choice when natural options exist. Skip questions already answered by brand/ context.
Questions to cover (in order, stop when clear):
brand/audience.md exists and is current — confirm briefly instead: "Your audience profile says X. Still accurate?")brand/competitors.md exists — reference it instead)Stop as soon as you have enough to propose approaches. 3-4 questions is usually enough.
Present 2-3 concrete strategic directions. For each:
### Approach [N]: [Name]
**Core angle:** [One sentence positioning]
**Channels:** [Primary → Secondary]
**Audience fit:** [Why this resonates with the target]
**Timeline:** [Quick win vs. long play]
**Pros:** [2-3 bullet points]
**Cons:** [1-2 bullet points]
**Best when:** [Conditions that make this the right choice]
Ask the user to pick one, combine elements, or explore further.
Handling responses:
| User says | Action |
|---|---|
| Picks an approach | Move to Phase 3 with that approach |
| Wants to combine | Merge the relevant elements into a hybrid approach, confirm the blend, then move to Phase 3 |
| Rejects all approaches | Ask what felt wrong. Probe for the constraint or preference you missed. Generate 1-2 new approaches informed by their feedback |
| "I want to do all of them" | Recommend a sequence: "Start with [approach] because [reason]. If that works, layer in [approach 2] in week 3." Prioritize, don't parallelize |
| Wants to explore further | Ask one targeted follow-up question, then generate 1-2 additional approaches |
Write a structured brief to marketing/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md:
---
type: marketing-brainstorm
date: YYYY-MM-DD
topic: [kebab-case topic]
goal: [awareness|leads|revenue|retention|launch]
chosen-approach: [N]
---
# Marketing Brief: [Topic]
## Context
[What we're marketing and why now]
## Chosen Approach
[Selected direction with rationale]
## Target Audience
[Who we're reaching]
## Channels
[Primary and secondary channels]
## Key Messages
[3-5 core messages]
## Constraints
[Budget, timeline, tools]
## Success Metrics
[How we'll measure impact]
## Structured Handoff
next-skill: [skill-name]
confidence: [high|medium|low]
context-summary: "[One line summary for /cmo routing]"
The next-skill field is critical — it tells /cmo where to route after brainstorming.
After writing the brief:
"The brainstorm is complete. Brief saved to marketing/brainstorms/[filename]. Run /cmo to execute the next step (/[next-skill]), or invoke /<next-skill> directly."
Do not list all 50 skills. Recommend the ONE next skill based on the brief.
User request: 'I just built a verified meal delivery app, what should I do for marketing?'
Approach 1: Community-Led Growth Build presence in health-focused community spaces (neighborhood Slack groups, campus food subreddits, verified-source food Instagram). Create shareable content that spreads through existing trust networks. → next-skill: audience-research
Approach 2: SEO + Content Capture 'verified meal delivery' search traffic with city-specific landing pages. Write comparison content ('Is DoorDash organic?') to redirect competitor traffic. → next-skill: keyword-research
Recommended: Approach 1 — community trust is the moat for verification-driven products. SEO is Phase 2 after you have testimonials to feature.
Follow the output formatting rules from /cmo rules/output-format.md. Key requirements:
| Anti-pattern | Instead | Why |
|---|---|---|
| Asking 5+ questions at once | One question at a time, multiple choice | Builders get overwhelmed by question walls. Each answer should shape the next question. |
| Jumping straight to tactics | Explore the strategic direction first | Tactics without strategy leads to scattered effort. "Post on TikTok" isn't a plan. |
| Proposing 5+ approaches | 2-3 focused options, not a menu | More options = more decision paralysis. The builder came here because they were stuck — don't make it worse. |
| Generic advice ("build an audience") | Specific to their product and context | Anyone can say "build an audience." The value is knowing WHICH audience, WHERE, with WHAT message. |
| Brainstorming when direction is clear | Skip to the execution skill | Brainstorming is exploration, not procrastination. If they know what they want, execute. |
| Leaving the user without a next step | Always include next-skill in the brief | A brainstorm that doesn't lead to action is just a meeting. The handoff is the whole point. |
audience-research, not guessingAlternatives
event4u-app/agent-config
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
MoizIbnYousaf/marketing-cli
Use when the user wants to generate an image or video via Higgsfield AI. Covers 30+ models: Soul V2, Seedance 2.0, Kling 3.0, Veo 3.1, GPT Image 2, Nano Banana 2. Also covers Marketing Studio — branded ad video/image with avatars and products. Use whenever: "generate an image", "make a video", "animate this photo", "image-to-video", "img2vid", "edit this image with AI", "produce a clip", "create an ad", "make a UGC video", "marketing video", "brand video", "TV spot", "import product from URL", "
MoizIbnYousaf/marketing-cli
Create new marketing skills for the mktg playbook. Use when the agent needs to add a new capability, someone says 'create a skill', 'new skill', 'add a marketing skill', 'extend the playbook', 'I need a skill for X', 'build a skill', 'make a skill for Y', or 'add capability for Z'. Also use when someone wants to capture a marketing workflow they just did into a reusable skill, or when they say 'turn this into a skill'. Reads the skill contract, generates SKILL.md with correct frontmatter and str
MoizIbnYousaf/marketing-cli
Generate visual asset briefs, ad copy variants, AI image prompts, video scripts, and storyboards. Full creative production system with 5 specialized modes: product photos, product video, social graphics, talking heads, and ad creative. Make sure to use this skill whenever the user mentions any visual or creative marketing need — ad creative, image prompts, video scripts, thumbnails, banners, social graphics, product photography, storyboards, or marketing visuals of any kind. Even if they just sa