brand-strategy
A 7-part brand strategy framework for building comprehensive brand foundations. Trigger with phrases like "create brand strategy", "build brand brief", "define brand positioning", "brand messaging", "audience architecture", "brand truth", or "go-to-market brand plan". Use when working with brand strategy.
49
54%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/business-tools/brand-strategy-framework/skills/brand-strategy/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description does a good job of providing explicit trigger phrases and answering both what and when, making it functional for skill selection. However, it leans on listing trigger terms rather than describing concrete actions the skill performs (e.g., what the 7 parts are or what outputs it produces). The domain is reasonably distinct but could overlap with general marketing or messaging skills.
Suggestions
Replace trigger phrase listing with concrete action descriptions for each of the 7 parts (e.g., 'Defines brand positioning, maps audience architecture, crafts messaging frameworks, develops go-to-market brand plans').
Sharpen distinctiveness by specifying what outputs the skill produces (e.g., 'Generates a brand brief document with positioning statement, audience personas, and messaging hierarchy').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It mentions a '7-part brand strategy framework' and references some components like 'brand positioning', 'brand messaging', 'audience architecture', and 'brand truth', but these are listed as trigger phrases rather than concrete actions the skill performs. It doesn't clearly list specific actions like 'creates positioning statements' or 'maps audience segments'. | 2 / 3 |
Completeness | The description answers both 'what' (a 7-part brand strategy framework for building comprehensive brand foundations) and 'when' (explicitly lists trigger phrases and states 'Use when working with brand strategy'). The 'Trigger with phrases like...' clause serves as an explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | The description includes a strong set of natural trigger phrases that users would likely say: 'create brand strategy', 'build brand brief', 'define brand positioning', 'brand messaging', 'audience architecture', 'brand truth', and 'go-to-market brand plan'. These cover a good range of variations a user might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | While 'brand strategy' is a reasonably specific domain, the final clause 'Use when working with brand strategy' is quite broad. Terms like 'brand messaging' or 'go-to-market' could overlap with marketing, content strategy, or messaging-focused skills. The '7-part framework' adds some distinctiveness but the boundaries aren't sharply defined. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable brand strategy framework structure but suffers from significant verbosity, boilerplate filler sections (Prerequisites, Error Handling, Resources) that are clearly template artifacts unrelated to brand strategy, and lack of concrete output examples. The discovery questions per phase are useful but the skill would benefit greatly from trimming irrelevant sections, adding sample outputs, and defining validation criteria between phases.
Suggestions
Remove the boilerplate sections (Prerequisites, Instructions, Output, Error Handling, Resources) at the bottom — they are template filler with nonsensical content like 'Authentication failure' for a brand strategy skill.
Add at least one concrete example output for a phase (e.g., a sample Brand Truth statement or a sample persona) so Claude knows the expected quality and format.
Add validation criteria or quality gates between phases — e.g., 'A Brand Truth statement is ready when it answers: why the brand exists, what it believes, and what makes it authentic. Confirm with the user before proceeding.'
Consider splitting detailed phase content into separate referenced files (e.g., PHASE1_BRAND_TRUTH.md) to reduce the monolithic structure and improve token efficiency when only specific phases are needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines for what is essentially a consulting framework. It explains concepts Claude already knows (what brand truth is, what audience architecture means). The bottom sections (Prerequisites, Instructions, Output, Error Handling, Resources) are clearly boilerplate/template filler that add no value — 'Authentication failure' and 'Configuration conflict' errors are nonsensical for a brand strategy skill. Significant token waste throughout. | 1 / 3 |
Actionability | The discovery questions and output specifications for each phase provide moderately concrete guidance — Claude knows what to ask and what to produce. However, there are no concrete examples of actual outputs (e.g., a sample Brand Truth statement, a sample persona), no executable code/commands, and the boilerplate sections at the bottom ('Apply the recommended patterns from this skill') are vague and generic. | 2 / 3 |
Workflow Clarity | The 7-phase sequential workflow is clearly defined with explicit ordering and the 'Workflow Guidelines' section reinforces sequencing. However, there are no validation checkpoints between phases — no criteria for when a phase is 'complete enough' to proceed, no feedback loops for revising earlier phases based on later discoveries, and no quality gates for outputs. | 2 / 3 |
Progressive Disclosure | All content is in a single monolithic file with no references to supporting files. The 200+ lines could benefit significantly from splitting detailed phase content into separate files. The 'Resources' section references nothing specific. No bundle files exist to support progressive disclosure. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
6e9558f
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.