Name: brand
Rating: 60.8 (1 reviews)
Author: nextlevelbuilder

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

72%

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

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

Quality

Content

75%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 an efficient, well-structured overview with executable commands, a validated sync workflow including a stop-and-review safety guard for overwriting token files, and a clean one-level-deep reference layout. Weaknesses are minor: a missing templates file, undefined routing for the advertised review/create subcommands, and a slightly verbose path-resolution paragraph.

Suggestions

Add the missing templates/brand-guidelines-starter.md file (or remove the Templates section), since the body's reference to it is broken.

Either add references/review.md and references/create.md or narrow the argument-hint and Routing section to the 'update' subcommand that actually exists.

State what successful output of the Verify step ("inject-brand-context.cjs --json | head -20") should contain so the checkpoint is actionable.

Dimension	Reasoning	Score
Conciseness	The body is table-driven with copy-paste commands and no explanation of concepts Claude already knows, matching anchor 4 ("Efficient; minor instances of over-explanation"). Not a 5 because the "Script Paths" paragraph is a dense multi-clause explanation that could be tightened to two sentences.	4 / 5
Actionability	Quick Start and Brand Sync Workflow give fully executable commands ("node scripts/inject-brand-context.cjs --json", "node scripts/sync-brand-to-tokens.cjs") matching anchor 4. Not a 5 because placeholders like "<asset-path>" and "<image-path>" lack a concrete invocation example and no expected output is shown for any command.	4 / 5
Workflow Clarity	The sync workflow is a clear sequence (edit -> "node scripts/sync-brand-to-tokens.cjs" -> "inject-brand-context.cjs --json \| head -20") with a genuine safety checkpoint ("The sync stops when it detects existing token files... re-run with --force"), matching anchor 4. Not a 5 because the Verify step does not state what correct output looks like, and the Routing section handles only the 'update' subcommand while the argument-hint advertises '[update\|review\|create]'.	4 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references: a 10-entry References table, Subcommands table pointing to references/update.md, and a Scripts table, all with existing files — matching anchor 4. Not a 5 because the Templates table points to "templates/brand-guidelines-starter.md" which does not exist in the bundle, and 'review'/'create' subcommands are advertised with no corresponding references.	4 / 5
	Total	16 / 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 is compact, third-person, and covers a clear brand niche with an explicit 'Activate for...' trigger clause. Its main weakness is that capabilities are expressed as topic nouns rather than concrete actions, and a few natural trigger synonyms (brand guidelines, logo, colors) are absent.

Suggestions

Rewrite the 'what' portion with concrete action verbs, e.g., "Defines brand voice and tone, creates messaging frameworks, audits brand consistency, manages and validates brand assets".

Add natural trigger synonyms users would actually say, such as "brand guidelines", "logo usage", "company colors", or "on-brand".

Dimension	Reasoning	Score
Specificity	"Brand voice, visual identity, messaging frameworks, asset management, brand consistency" names five concrete capability areas but uses noun phrases with no action verbs, so it sits between anchor 2 ("actions are minimal or generic") and anchor 3 ("1-2 concrete actions"); breadth of coverage pulls it up to 3. It is not a 4 because no specific actions (e.g., 'define', 'audit', 'sync') are stated.	3 / 5
Completeness	It answers both 'what' ("Brand voice, visual identity, messaging frameworks, asset management, brand consistency") and 'when' ("Activate for branded content, tone of voice...") with an explicit trigger clause, matching anchor 4. Not a 5 because the 'what' is a topic list rather than concrete actions and the 'when' triggers could be more specific (e.g., mentioning logos or color palettes).	4 / 5
Trigger Term Quality	"Activate for branded content, tone of voice, marketing assets, brand compliance, style guides" provides good natural keyword coverage matching anchor 4. Not a 5 because common user phrases like "brand guidelines", "logo", "company colors", or "branding" are missing.	4 / 5
Distinctiveness Conflict Risk	"tone of voice", "brand compliance", and "style guides" carve out a clear brand niche with mostly distinct triggers (anchor 4). Not a 5 because terms like "marketing assets" and "visual identity" have minor overlap risk with general design or 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: 4 missing	Warning

	Total	14 / 16 Passed

Repository: nextlevelbuilder/ui-ux-pro-max-skill
Path: .claude/skills/brand/SKILL.md
Commit: 09170ee

Reviewed: 2 hours 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.