Expert brand strategist and guardian specializing in brand identity development, consistency maintenance, and strategic brand positioning
31
14%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./design-brand-guardian/skills/SKILL.mdQuality
Discovery
14%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description reads like a LinkedIn headline rather than a functional skill description. It relies heavily on abstract buzzwords ('expert brand strategist', 'guardian', 'strategic positioning') without specifying concrete actions Claude would take or when this skill should be triggered. It lacks both a 'Use when...' clause and specific, actionable capability statements.
Suggestions
Replace abstract phrases with concrete actions, e.g., 'Develops brand guidelines, audits content for brand consistency, creates brand voice documentation, and defines visual identity standards.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about brand guidelines, brand voice, logo usage, style guides, brand audits, or maintaining brand consistency across materials.'
Remove the 'Expert brand strategist and guardian' framing and use third-person action verbs to describe what the skill does rather than what it is.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'brand identity development', 'consistency maintenance', and 'strategic brand positioning' without listing any concrete actions Claude would perform. These are buzzword-heavy phrases rather than specific capabilities. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' with abstract domain terms and completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent instruction for Claude to know when to select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'brand identity', 'brand positioning', and 'brand consistency' that users might mention, but lacks common variations and natural phrases users would actually say (e.g., 'logo guidelines', 'brand voice', 'style guide', 'brand audit', 'naming'). | 2 / 3 |
Distinctiveness Conflict Risk | The description is very generic and could overlap with marketing skills, design skills, content strategy skills, or any brand-adjacent skill. 'Brand strategist and guardian' is too broad to carve out a clear niche. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a verbose persona description rather than an actionable skill document. It spends most of its token budget describing what a brand strategist is and does (which Claude already knows) rather than providing specific, novel instructions or executable guidance. The templates provide some structure but are placeholder-heavy, and the workflow lacks any concrete validation or feedback mechanisms.
Suggestions
Cut the document by 70%+ by removing sections Claude already knows (identity, personality, success metrics, advanced capabilities, learning & memory, communication style) and focus only on novel, project-specific instructions.
Replace the vague 4-step workflow with concrete, sequenced steps that include specific validation checkpoints (e.g., 'Verify color contrast ratios meet WCAG AA using [specific tool/method]').
Move the large templates (Brand Foundation, Visual Identity CSS, Voice Guidelines, Deliverable Template) into separate referenced files and keep SKILL.md as a concise overview with navigation links.
Add at least one complete, filled-in example (not just bracket placeholders) showing what a finished brand deliverable looks like for a specific scenario.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with content Claude already knows. Sections like 'Your Identity & Memory', 'Learning & Memory', 'Success Metrics', 'Advanced Capabilities', and 'Communication Style' are all unnecessary fluff that describe what a brand strategist does rather than providing actionable, novel instructions. The document is ~200+ lines of mostly generic brand strategy concepts. | 1 / 3 |
Actionability | The templates (Brand Foundation Framework, Visual Identity CSS, Voice Guidelines) provide some concrete structure, but they are placeholder-heavy with [bracket values] throughout and no real executable examples. The workflow steps are vague bash comments like '# Analyze business requirements' rather than concrete instructions. The CSS template is a reasonable starting point but not truly executable. | 2 / 3 |
Workflow Clarity | The 4-step workflow process is extremely vague with no validation checkpoints, no feedback loops, and no concrete sequencing. Steps like 'Create comprehensive brand strategy framework' and 'Establish brand compliance monitoring processes' are abstract descriptions, not actionable workflow steps. There's no guidance on how to verify outputs or handle issues. | 1 / 3 |
Progressive Disclosure | The entire document is a monolithic wall of text with no references to external files. All content is inline despite being very long. The final line references 'core training' which is meaningless. There's no separation of overview vs. detailed reference material, and the massive templates could easily be split into separate files. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
09aef5d
Table of Contents
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.