CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brand

Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

64

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/brand/SKILL.md

The canonical home for this skill is brand in nextlevelbuilder/ui-ux-pro-max-skill

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, actionable skill body: copy-paste commands, a sync workflow with an explicit stop-on-conflict checkpoint and recovery guidance, and clean one-level-deep reference navigation. The only defects are a redundant 'When to Use' section and a dangling templates/ pointer.

DimensionReasoningScore

Conciseness

Tables and copy-paste command blocks keep the body lean, and the Script Paths paragraph conveys genuinely non-obvious path-resolution semantics. The 'When to Use' bullets largely duplicate the frontmatter description and could be trimmed, keeping it below anchor 5.

4 / 5

Actionability

Quick Start gives fully executable commands for the common cases ('node scripts/inject-brand-context.cjs --json', 'node scripts/validate-asset.cjs <asset-path>', 'node scripts/extract-colors.cjs --palette') with real flags and placeholders, and the sync workflow is copy-paste ready with a verify step.

5 / 5

Workflow Clarity

The Brand Sync Workflow is a clear edit → sync → verify sequence with an explicit conflict checkpoint ('The sync stops when it detects existing token files... Review the reported source before proceeding') and a recovery path (re-run with --force only when replacement is intentional), which is a genuine feedback loop.

5 / 5

Progressive Disclosure

References are well-signaled and one level deep (all 11 referenced references/*.md files exist, with no nested cross-references), and the Scripts table maps purposes clearly. However, the Templates table points to 'templates/brand-guidelines-starter.md', which does not exist in the bundle — a minor organization gap that keeps it below anchor 5.

4 / 5

Total

18

/

20

Passed

Description

65%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 distinct, well-triggered description with an explicit 'Activate for' clause and natural trigger terms. Its main weakness is the capability statement: it enumerates brand domains as nouns without a single concrete action or deliverable, leaving the 'what does this do' question only partially answered.

Suggestions

Replace the noun-list opening with concrete action verbs, e.g. 'Define brand voice, audit content for brand consistency, sync brand guidelines to design tokens, and validate marketing assets.'

Name the skill's actual deliverables (e.g. docs/brand-guidelines.md, design-token outputs) so the 'what' states outputs rather than only topic areas.

Add natural trigger synonyms such as 'brand guidelines', 'on-brand', or 'logo usage' to the 'Activate for' clause to broaden keyword coverage.

DimensionReasoningScore

Specificity

The 'what' is a list of domain nouns ('Brand voice, visual identity, messaging frameworks, asset management, brand consistency') with no action verbs anywhere — it never states what the skill does. It names the domain specifically (not pure abstraction like 'Helps with documents'), but anchor 3 requires 1-2 concrete actions, which are absent.

2 / 5

Completeness

Both parts are present: a 'what' (the domain list) and an explicit 'when' clause ('Activate for...') with concrete trigger phrases. Not 5 because the 'what' is a topic inventory rather than a statement of what the skill does or produces, so it answers 'what areas' more clearly than 'what it does'.

4 / 5

Trigger Term Quality

'Activate for branded content, tone of voice, marketing assets, brand compliance, style guides' provides natural phrases users would actually say. Not 5 because common synonyms like 'brand guidelines', 'on-brand', or 'logo usage' are missing.

4 / 5

Distinctiveness Conflict Risk

The brand niche is mostly distinct with brand-flavored triggers. Minor overlap risk remains: 'style guides' could match code style guides, and 'tone of voice'/'marketing assets' overlap with general content-writing skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Repository

nextlevelbuilder/ui-ux-pro-max-skill

Path

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