CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-style-guide

Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts. Use this skill whenever the user wants to create brand guidelines, document an existing brand, build a brand book, audit an existing style guide for completeness, or produce the artifact that other teams will reference for years. Triggers on style guide, brand guidelines, brand book, brand standards, brand manual, style sheet, brand documentation, brand reference. Also triggers when the brand identity is finished and needs to be documented for handoff to designers, developers, vendors, or future team members.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured reference-manual framework: lean, actionable checklists across eight sections, a clear sequenced workflow, and clean progressive disclosure to two real reference files. The main gap is the absence of an explicit validate-and-retry feedback loop in the workflow, though the task is non-destructive so this is a minor rather than critical gap.

Suggestions

Tighten editorial framing sentences (e.g., 'This is the artifact that lives longest', 'Most guides skip 2 or 3 of them') to lift conciseness toward the 5 anchor.

Add an explicit validation checkpoint to the workflow (e.g., after drafting each section, verify every rule has at least one real example and every 'forbidden' treatment has a do/don't pair) to strengthen workflow_clarity.

Surface one or two concrete inline examples from the template (e.g., a sample 'voice attributes' or 'clear space rule' entry) so the body is more self-contained without the reference file.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanations of what a brand/logo is), but a few framing sentences ('This is the artifact that lives longest', 'Most guides skip 2 or 3 of them') are editorial padding that could be trimmed, placing it just below the 5 anchor.

4 / 5

Actionability

Provides concrete, actionable guidance via eight section checklists, a 7-step workflow, and an explicit output file tree; as an instruction-only skill this is executable, though it leans on the template reference for fill-in detail rather than being fully self-contained, matching the 4 anchor.

4 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced (inventory inputs, confirm format, draft section by section, stress-test with examples, get review, version control, publish) with review/stress-test checkpoints present; it lacks an explicit validate-fix-retry feedback loop, but since this is non-destructive documentation work the cap-at-3 rule does not apply, so it sits at 4.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with two well-signaled one-level-deep references (style-guide-template.md linked in workflow step 3, maintenance-playbook.md) that both exist as real files, and content is appropriately split, matching the 5 anchor.

5 / 5

Total

17

/

20

Passed

Description

96%Weight 40%Scale 1-5

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 is strong: it states concrete actions, enumerates the full brand system, and provides explicit 'when to use' guidance with a rich set of natural trigger synonyms. Only minor distinctiveness risk exists against sibling brand/design skills, which the body's 'When NOT to use' section further disambiguates.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts') with comprehensive coverage of the system components, matching the 5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' ('Build or audit a comprehensive brand style guide...') and 'when' ('Use this skill whenever the user wants to create brand guidelines... Also triggers when the brand identity is finished and needs to be documented for handoff...'), matching the 5 anchor with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms via 'Triggers on style guide, brand guidelines, brand book, brand standards, brand manual, style sheet, brand documentation, brand reference', matching the 5 anchor's synonym coverage expectation.

5 / 5

Distinctiveness Conflict Risk

Clear niche (brand style guide documentation) with specific triggers and minimal conflict risk, but adjacent skills like brand-voice and design-system/design-standards share the broader brand/design domain, creating minor overlap risk consistent with the 4 anchor.

4 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
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.