brand

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

71%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 concise and actionable with executable commands and a sequenced sync workflow that includes verification. Its chief weakness is progressive disclosure: multiple file paths referenced in the body do not exist in the bundle, undermining navigation.

Suggestions

Create the missing referenced files (templates/brand-guidelines-starter.md, assets/design-tokens.json, assets/design-tokens.css, docs/brand-guidelines.md) or remove the references to them so navigation links resolve.

Add references/review.md and references/create.md to match the argument-hint subcommands and Routing section, or narrow the documented subcommands to those that have reference files.

Add an explicit error-recovery feedback loop to the Brand Sync Workflow (e.g., 'if the verify step shows stale tokens, re-edit the source and re-run sync') to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean with section headers, command tables, and a brief workflow, assuming Claude's competence; minor redundancy exists since the Quick Start scripts reappear in the Scripts table and the Subcommands table overlaps the Routing section.	4 / 5
Actionability	It provides concrete, copy-paste-ready `node scripts/...` commands with flags and a numbered sync workflow, but the Routing logic is high-level and subcommand arguments beyond `update` are not shown, leaving minor gaps.	4 / 5
Workflow Clarity	The Brand Sync Workflow is a clear 3-step sequence (edit -> sync -> verify) with a verification step, satisfying the validation requirement for batch/destructive token-file writes; it falls short of 5 because there is no explicit error-recovery feedback loop.	4 / 5
Progressive Disclosure	The body is a well-structured overview with clearly signaled one-level-deep reference tables (and all listed references/ files exist), but several referenced paths are missing from the bundle (`templates/brand-guidelines-starter.md`, `assets/design-tokens.json`, `assets/design-tokens.css`, `docs/brand-guidelines.md`, and the implied `references/review.md`/`create.md`), breaking navigation.	3 / 5
	Total	15 / 20 Passed

Description

70%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 gives a clear, third-person statement of both what the skill covers and when to activate it, with natural trigger terms. Its main weakness is that it catalogs capability areas rather than naming concrete actions.

Dimension	Reasoning	Score
Specificity	It clearly enumerates the domain ("Brand voice, visual identity, messaging frameworks, asset management, brand consistency") but lists topic areas rather than concrete actions like extract/fill/merge, so it sits at the boundary of domain-naming with minimal actions rather than comprehensive verbs.	3 / 5
Completeness	The first sentence answers "what" with enumerated capabilities and "Activate for..." provides an equivalent explicit "when" clause with concrete triggers; it is not a 5 because the trigger phrasing could be slightly more specific and exhaustive.	4 / 5
Trigger Term Quality	"Activate for branded content, tone of voice, marketing assets, brand compliance, style guides" provides good natural keyword coverage a user would say, though it lacks synonym/file-extension-style variants to reach comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The brand niche is mostly distinct with brand-specific triggers ("tone of voice", "brand compliance", "style guides"), carrying only minor overlap risk with generic content/marketing skills.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Path: .claude/skills/brand/SKILL.md
Commit: f232671

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.