This runs a two-phase brand research workflow: first it interviews you with seven grouped questions about the brand, product focus, audience, and constraints, then it goes off and does structured web research to fill in the gaps. It pulls brand story, full product catalog, competitor positioning, audience signals, voice patterns, and inferred creative constraints, then outputs everything as a structured markdown file. It's designed to run before any creative strategy or hook writing work, basically the context layer that keeps you from writing blind. The interview format is smart because it doesn't waste time researching things you already know. If you're doing client work or building briefs for paid social, this gives you a repeatable intake process instead of ad-hoc Googling.
npx -y skills add motion-team/creative-strategy-skills --skill brand-intake --agent claude-codeInstalls into .claude/skills of the current project.
This does two things in sequence:
The output is a structured markdown file (brand-context.md) that all downstream modules — Creative Strategy Engine, Hook Writing, Creative Mechanics — can reference as the foundational context layer.
Before researching anything, ask the user the following questions. Ask them all at once in a single message — do not drip them one by one. Group them clearly so the user can answer quickly.
Brand basics:
What you already know: 4. What do you know about this brand and its audience that is important to use in your workflow? (e.g. Age, gender, lifestyle, pain points, values.) 5. Do you know who their main competitors are? 6. Are there any brand constraints you're already aware of? (e.g., can't make health claims, family-friendly tone, sensitive topic, regulated category)
Creative context: 7. Do you have any existing creative or messaging you've already seen from this brand that you want to keep in mind?
Once you have their answers, confirm before proceeding:
"Got it — I'll use this as my starting point and go research the rest. I'll come back with a full brand context doc. Give me a moment."
Then proceed to Phase 2.
Using the brand name and URL provided, conduct web research to fill out the full brand context document. Use the web_search and web_fetch tools.
Work through each of these areas. For each one, gather what you can from the brand's website, ad library, reviews, press, and competitor sites.
Research approach: Fetch the About page. Search "[brand name] founder story" and "[brand name] how it started."
Research approach: Fetch the product/shop pages. Look at site navigation.
Research approach: Fetch product detail pages and any "How it works" or FAQ pages. Look for any clinical claims, certifications, or patent language.
Research approach: Search "[brand name] vs [competitor]", "[product category] alternatives", and "[brand name] competitors." Also check if the brand calls out competitors directly in their messaging.
Research approach: Look at reviews, the brand's own problem-framing language, and any "vs. traditional methods" content.
Research approach: Analyze homepage copy, ad creative (Meta Ad Library if accessible), product page language, and review language.
Research approach: Read website copy closely. Look for patterns in headlines, CTAs, email popups, FAQ answers.
Based on everything you've found, identify likely constraints that would affect ad creative. Think about:
Label each constraint as confirmed (explicitly stated somewhere) or inferred (reasonable assumption based on category/signals).
Anything else that a creative strategist needs to know before writing a single hook. This might include:
Once research is complete, compile everything into a structured markdown document.
# Brand Context: [Brand Name]
*Generated: [Date] | Focus: [Product/Product Line or "Full Brand"]*
---
## Brand Overview
[2–3 sentence summary of who this brand is, what they sell, and where they sit in the market.]
---
## Brand Story & Origin
[Founder story, mission, origin. Keep it factual and concise.]
---
## Product Catalog
[List of products with brief descriptions. Flag the hero product if identifiable.]
| Product | Key Differentiator | Audience |
|---|---|---|
| ... | ... | ... |
---
## What Makes Them Different
[Unique mechanism, proprietary ingredient, format advantage, or positioning edge. Quote their own language where possible.]
---
## Competitor Landscape
[3–5 competitors, how each positions, and how this brand contrasts.]
| Competitor | Their Positioning | How This Brand Differs |
|---|---|---|
| ... | ... | ... |
---
## The Alternative Solution
[What the customer was doing before this product. The "old way."]
---
## Core Audience(s)
**Primary:** [Description]
**Secondary (if applicable):** [Description]
Key signals: [Pain points, lifestyle, language patterns, what they care about]
---
## Brand Voice & Tone
[Adjectives. Patterns. Examples of actual copy that demonstrate the voice. What they avoid.]
---
## Creative Constraints
| Constraint | Type | Notes |
|---|---|---|
| ... | Confirmed / Inferred | ... |
---
## Must-Know Strategic Context
[Anything else a creative strategist must know before writing creative. Bullets OK here.]
---
## Research Notes
*Sources consulted: [list URLs fetched]*
*Gaps / low-confidence areas: [anything you couldn't verify — flag it clearly so the user can fill in or correct]*
After building the document:
brand-context-[brandname].mdpresent_files"Does anything here look off, or is there anything important I'm missing? Once you confirm, this becomes the working context for all creative strategy on this brand."
After confirmation, this document should be referenced by all downstream modules (Creative Strategy Engine, Hook Writing, Creative Mechanics) for this brand.
When handing off to the Creative Strategy Engine or Hook Writing, reference the brand context doc explicitly:
"Using
brand-context-[brandname].mdas the foundation — the audience, differentiation, constraints, and voice are all defined there."
This prevents downstream modules from making assumptions that conflict with the established brand context.