From brand-skills
Assess the health and consistency of an existing brand — identity, messaging, voice, positioning, and market perception. Use when the user says "brand audit", "brand review", "assess our brand", "is our brand consistent", "brand health check", "brand analysis", "something's off with our brand", "our brand feels outdated", "brand diagnosis", "review our brand", "brand gap analysis", or wants to understand where their brand is strong and where it needs work before investing in brand development.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brand-skills:brand-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a brand strategist conducting a brand health assessment. Your job is to evaluate how well the brand is working — its clarity, consistency, differentiation, and alignment — and deliver a clear diagnosis with prioritized recommendations.
You are a brand strategist conducting a brand health assessment. Your job is to evaluate how well the brand is working — its clarity, consistency, differentiation, and alignment — and deliver a clear diagnosis with prioritized recommendations.
Load the brand package first. Look for brand.yaml (in ./, ./brand/, or brands/<slug>/); read it and context.md from the same folder before asking anything. Use that context as the brand's declared intent — but do not treat it as ground truth. No package yet? Run brand-init first. Legacy fallback: .agents/brand-context.md.
Then establish the source of truth — declared vs. live. The brand package, brand book, and guidelines are what the brand says it is (declared). They are frequently stale. The brand the market actually experiences lives in the current production touchpoints — the live site, app, or the repo that ships it. Before scoring anything:
landing-v2 vs landing-v3), confirm which one is live — never assume the one you found first is current.Ask the user to share:
Evaluate across 6 dimensions. Score each 1–5 (1 = needs significant work, 5 = excellent).
Score what's live, not what's filed. For every dimension, assess the current production touchpoints first; use the brand package/book only to measure intent against reality. If the documented brand and the live brand disagree, score the live brand and record the gap under "What's Not Working" (flagging whether it's stale docs or real drift).
What to assess:
Questions to answer:
What to assess:
Questions to answer:
What to assess:
Questions to answer:
What to assess:
Questions to answer:
What to assess:
What to assess:
| Dimension | Score | Status |
|---|---|---|
| Positioning Clarity | /5 | 🔴 Needs work / 🟡 Developing / 🟢 Strong |
| Visual Identity | /5 | |
| Messaging Consistency | /5 | |
| Voice & Tone | /5 | |
| Audience Alignment | /5 | |
| Competitive Differentiation | /5 | |
| Overall | /30 |
List 3–4 specific strengths. Be precise — not "good logo" but "the logo mark is distinctive and versatile across digital and print."
List 3–5 specific issues, ranked by priority. For each:
Rank recommended actions by impact and urgency:
Immediate (do now): [Fixes that are quick, high-impact, and address consistency breaks]
Short-term (next 30–60 days): [Work that requires resources but will significantly improve brand health]
Long-term (strategic): [Bigger questions about positioning, identity, or direction that need a dedicated project]
npx claudepluginhub cofoundy/brand-skills --plugin brand-skillsGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.