Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
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 and recommends the best path forward with a specific next-skill handoff. Even vague frustration like 'nobody knows about my product' or 'how do I get users' should trigger this when no specific channel or tactic is mentioned.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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 guessingまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
Add a new sound effect to @remotion/sfx
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up a secure email inbox for any AI agent — configuring inbound email via Resend, webhooks, tunneling for local development, and implementing security measures to prevent prompt injection attacks. Also use when someone mentions 'agent email', 'bot inbox', 'receive emails for agent', 'agent webhook', 'email security for AI', 'prompt injection via email', 'inbound email for bot', or wants their AI agent to receive and respond to emails securely.
日本語の概要は準備中です。原文の説明を表示しています。
Builds, measures, and improves an Answer Engine Optimization program across ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, and Copilot. Use for AEO, GEO, LLMO, AI search visibility, AI citations, brand mentions, answer-engine monitoring, llms.txt, AI crawler audits, or questions like 'what does AI say about us?' and 'why are competitors cited instead of us?'. Produces a durable evidence report and prioritized gameplan, not a one-shot content checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Apple App Store screenshot pages as a Next.js app with html-to-image export at required resolutions. Screenshots are advertisements, not documentation — every screenshot sells one idea. Use when building App Store screenshots, generating exportable marketing screenshots for iOS apps, or creating programmatic screenshot generators. Triggers on 'app store screenshots', 'App Store', 'screenshot generator', 'iOS screenshots', 'marketing screenshots', 'phone mockup', 'ASO screenshots', 'app store assets', 'app listing', 'app store page', or 'app preview images'. Also use when someone is about to submit an app and needs store assets, or when they say 'make my app store page look good'. Includes iPhone and iPad mockup components with pre-measured dimensions.
日本語の概要は準備中です。原文の説明を表示しています。
Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.
日本語の概要は準備中です。原文の説明を表示しています。