CtrlK
BlogDocsLog inGet started
Tessl Logo

brand

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

69

Quality

86%

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

90%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, concise, and actionable skill body that uses tables and executable commands effectively. The two gaps are a missing fix-and-retry feedback loop in the sync workflow and several dangling file references that break navigation.

Suggestions

Add an explicit feedback loop to the Brand Sync Workflow after the Verify step, e.g. 'If the verify output shows mismatches, re-edit docs/brand-guidelines.md and re-run node scripts/sync-brand-to-tokens.cjs', so validation has a retry path.

Resolve the dangling references: templates/brand-guidelines-starter.md, docs/brand-guidelines.md, assets/design-tokens.json, and assets/design-tokens.css are cited in the body but are not present in the bundle — either add these files or remove/qualify the references.

Clarify Routing for subcommands other than `update` (the only one with a references/update.md entry), noting how bare invocation or unknown subcommands should be handled.

DimensionReasoningScore

Conciseness

The body is lean and table-driven with no over-explanation of concepts Claude already knows (no 'what is a brand' padding); every section earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

Quick Start and Brand Sync Workflow give copy-paste-ready executable commands (e.g. `node scripts/inject-brand-context.cjs --json`, `node scripts/validate-asset.cjs <asset-path>`, `node scripts/extract-colors.cjs --palette`) covering the common cases, fitting the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

The Brand Sync Workflow is a clear numbered sequence with a 'Verify' checkpoint (`inject-brand-context.cjs --json | head -20`), but it lacks an explicit feedback loop (fix-and-retry on failure), so it matches 'clear sequence with most checkpoints present; minor validation gaps' rather than the full error-recovery loop of 5.

4 / 5

Progressive Disclosure

The body is a clean overview with well-signaled one-level-deep reference/script tables, but the Templates and 'Files synced' sections point to paths absent from the bundle (templates/brand-guidelines-starter.md, docs/brand-guidelines.md, assets/design-tokens.json, assets/design-tokens.css), matching 'good structure; references mostly clear; minor organization gaps' rather than the clean navigation of 5.

4 / 5

Total

18

/

20

Passed

Description

82%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 with an explicit 'Activate for ...' trigger clause and a clear brand niche, yielding high completeness and distinctiveness. The main weakness is phrasing capabilities as noun phrases rather than concrete actions, which limits specificity.

DimensionReasoningScore

Specificity

The description names five distinct domain areas ("Brand voice, visual identity, messaging frameworks, asset management, brand consistency") but lists them as noun phrases rather than concrete actions/verbs, so it sits between the 'minimal actions' (2) and 'concrete actions' (3) anchors, landing at 3 for naming the domain comprehensively without verbs.

3 / 5

Completeness

It explicitly answers both 'what' (the five capability areas) and 'when' via the concrete 'Activate for ...' trigger clause with multiple explicit trigger phrases, satisfying the 'clearly and explicitly answers both what AND when with concrete trigger phrases' anchor.

5 / 5

Trigger Term Quality

"Activate for branded content, tone of voice, marketing assets, brand compliance, style guides" provides good coverage of natural phrases a user would say, matching the 'good keyword coverage; a few natural terms missing' (4) anchor rather than the fully comprehensive synonym/extension coverage of 5.

4 / 5

Distinctiveness Conflict Risk

"Brand" is a clear niche and the trigger phrases (brand compliance, style guides, tone of voice) are distinct to brand work with minimal overlap risk against other skills, fitting the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

17

/

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.

Validation14 / 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: 2 missing

Warning

Total

14

/

16

Passed

Repository
nextlevelbuilder/ui-ux-pro-max-skill
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.