CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

93%

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

88%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.

A well-structured, highly actionable instruction-only skill with a clear framework, sequenced workflow including review/versioning checkpoints, and real reference files. The main improvement opportunity is pushing the detailed per-section checklists into the template reference to tighten the main file.

Suggestions

Move the detailed per-section bullet checklists (sections 1-8) into references/style-guide-template.md and keep only a one-line summary of each section in SKILL.md, since the template already covers the same ground.

Add a brief "Distinct triggers" note in the description or When NOT to use section clarifying the boundary with brand-identity and brand-voice (e.g., voice work happens in brand-voice and is only integrated here).

In the workflow, name which reference file to open at each step (maintenance-playbook.md is only listed at the end; link it where versioning/publishing is discussed).

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes competence, but the per-section bullet checklists (e.g., "Per color: hex, RGB, HSL, CMYK, Pantone") substantially duplicate the fillable template in references/style-guide-template.md and could be trimmed from SKILL.md.

4 / 5

Actionability

As an instruction-only skill the guidance is fully concrete and executable: specific counts ("Values (3 to 5)"), precise requirements ("Contrast ratios documented", "Open-source alternatives for licensing-restricted contexts"), an exact output file tree, and a usable 8-section framework.

5 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced with explicit validation and feedback checkpoints ("Stress-test with real examples", "Get review from the people who will use it", "Version control") plus a failure-patterns section; no destructive or batch operations that would require additional validation.

5 / 5

Progressive Disclosure

Well-organized sections with two real, one-level-deep references clearly signaled in a dedicated "Reference files" section and linked from the workflow; however, the full 8-section specification is inlined in SKILL.md when the template reference is its natural home, leaving a minor organization gap.

4 / 5

Total

18

/

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.

A strong description that explicitly states what the skill does, when to use it, and a rich set of natural trigger terms. The only weakness is slight overlap with adjacent brand skills via broad terms like "brand documentation" and "brand reference".

DimensionReasoningScore

Specificity

"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" names multiple concrete actions and enumerates comprehensive coverage of the deliverable's scope.

5 / 5

Completeness

Explicitly answers both "what" (build/audit/document a comprehensive style guide with the section list) and "when" ("Use this skill whenever the user wants to…", "Also triggers when the brand identity is finished and needs to be documented for handoff…") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Triggers on style guide, brand guidelines, brand book, brand standards, brand manual, style sheet, brand documentation, brand reference" provides comprehensive natural-term coverage with abundant synonyms users would actually say; file extensions are not applicable to this domain.

5 / 5

Distinctiveness Conflict Risk

The niche (the canonical documentation artifact for a finished identity) is clear and triggers are distinctive, but generic terms like "brand documentation"/"brand reference" and inclusion of "voice" in the scope list create minor overlap risk with closely related brand-identity/brand-voice skills, so it is not fully minimal conflict risk.

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.

Validation — 15 / 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

Path

skills/brand-style-guide/SKILL.md

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.