Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

brand-intake品牌摄入量

Agent Skill

brand-intake 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

3,434

周安装

146

GitHub Stars

88

下载量

1,203
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:brand-intake(品牌摄入量)
来源仓库:https://github.com/motion-team/creative-strategy-skills
仓库路径:skills/brand-intake
安装命令:
npx skills add https://github.com/motion-team/creative-strategy-skills --skill brand-intake
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/motion-team/creative-strategy-skills --skill brand-intake

简介

brand-intake 先访谈再调研,构建品牌背景文档作为下游创意模块的统一上下文基础。

  • 它收集品牌种子信息后主动检索公开资料,形成包含竞品与市场定位的综合报告。
  • 输出 brand-context.md 可被 Hook Writing、Creative Mechanics 等技能复用,避免重复提问。
  • 注意网络搜索结果时效性,过时的市场数据可能影响策略建议可靠性。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Brand Intake

This does two things in sequence:

  1. Interviews the user to collect essential seed information about the brand
  2. Researches the brand using that information to build a comprehensive brand context document

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.


PHASE 1: INTAKE INTERVIEW

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.

Questions to Ask

Brand basics:

  1. What's the brand name?
  2. What's the brand website URL?
  3. What product(s) are you running paid ads for? If multiple, list them. If all, say "all".
  4. Is there a specific product or product line you want this context document to focus on, or should it cover the full brand?

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?


After the User Answers

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.


PHASE 2: RESEARCH

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.

Research Checklist

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.

1. Brand Story & Origin

  • How did the brand start? What problem did the founder set out to solve?
  • Is there a founder story or mission that drives the brand's identity?
  • How long have they been around? Are they a startup, scaling, or established?

Research approach: Fetch the About page. Search "[brand name] founder story" and "[brand name] how it started."

2. Full Product Catalog

  • What products do they sell?
  • What are the key SKUs or product lines?
  • How are products differentiated from each other (size, use case, formulation, audience)?
  • What is the hero product or primary revenue driver (if identifiable)?
  • Does the brand offer any bundles?

Research approach: Fetch the product/shop pages. Look at site navigation.

3. Product Differentiation & Unique Mechanism

  • What makes their product(s) different from alternatives?
  • Is there a proprietary ingredient, format, technology, or method?
  • How do they explain their point of difference on their website?
  • What claims do they make and how do they support them?

Research approach: Fetch product detail pages and any "How it works" or FAQ pages. Look for any clinical claims, certifications, or patent language.

4. Competitors

  • Who are the 3–5 closest competitors?
  • How do competitors position themselves vs. this brand?
  • What does this brand do that competitors don't (or vice versa)?

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.

5. The Alternative Solution

  • What was the customer doing BEFORE this product existed?
  • What is the "old way" this product replaces or improves upon?
  • This is not always a direct competitor — sometimes it's a behavior, DIY approach, or doing nothing.

Research approach: Look at reviews, the brand's own problem-framing language, and any "vs. traditional methods" content.

6. Core Audience(s)

  • Who is the primary audience this brand speaks to on their website and in ads?
  • Are there distinct secondary audiences?
  • What signals point to who they're targeting? (Imagery, language, pain points surfaced, price point, lifestyle cues)
  • Combine what the user told you in Phase 1 with what you find in research.

Research approach: Analyze homepage copy, ad creative (Meta Ad Library if accessible), product page language, and review language.

7. Brand Voice & Tone

  • How does this brand communicate? (Clinical? Warm? Witty? Direct? Community-driven?)
  • What adjectives describe their copy style?
  • Are there notable patterns — vocabulary they use, things they avoid, emotional register?
  • Does voice shift between product types or audiences?

Research approach: Read website copy closely. Look for patterns in headlines, CTAs, email popups, FAQ answers.

8. Inferred Creative Constraints

Based on everything you've found, identify likely constraints that would affect ad creative. Think about:

  • Category sensitivities (health claims, before/after restrictions, regulated ingredients)
  • Audience constraints (if audience includes older demographics, religious communities, parents, etc.)
  • Platform norms (if brand is in a category with known Meta/TikTok ad restrictions)
  • Tone constraints (brands that are buttoned-up, family-safe, or community-led often have limits on edginess or provocation)
  • Price point constraints (high-AOV brands often can't do price-shock tactics; budget brands can't lean on premium positioning)

Label each constraint as confirmed (explicitly stated somewhere) or inferred (reasonable assumption based on category/signals).

9. Must-Know Strategic Context

Anything else that a creative strategist needs to know before writing a single hook. This might include:

  • Unusual purchase behavior (subscription vs. one-time, bundle-heavy, etc.)
  • Seasonal relevance
  • Strong community or UGC presence
  • Noteworthy press or cultural moments
  • Anything the user flagged in Phase 1 that needs to be incorporated

PHASE 3: BUILD THE CONTEXT DOCUMENT

Once research is complete, compile everything into a structured markdown document.

Output Format

# 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]*

PHASE 4: DELIVER & CONFIRM

After building the document:

  1. Save it as brand-context-[brandname].md
  2. Present it to the user using present_files
  3. Flag gaps — call out anything you couldn't verify or are inferring vs. confirming
  4. Ask one closing question:
"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.


Notes for Downstream Handoff

When handing off to the Creative Strategy Engine or Hook Writing, reference the brand context doc explicitly:

"Using brand-context-[brandname].md as 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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.56%
按下载量换算464

Claude

29.11%
按下载量换算350

Cursor

20.66%
按下载量换算249

Gemini CLI

8.8%
按下载量换算106

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills