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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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 highly actionable, with executable commands and a sequenced sync workflow. It loses points for a missing error-recovery feedback loop in the workflow and for several referenced bundle paths (design tokens, brand-guidelines.md, the starter template) that do not exist in the bundle.

Suggestions

Add a feedback loop to the Brand Sync Workflow (e.g., "If verification fails, fix docs/brand-guidelines.md and re-run sync-brand-to-tokens.cjs").

Either add the missing referenced files (docs/brand-guidelines.md, assets/design-tokens.json/.css, templates/brand-guidelines-starter.md) or remove the dangling references.

Clarify the Routing section's fallback when a subcommand has no matching references/{subcommand}.md file.

Dimension	Reasoning	Score
Conciseness	The body is lean and table-driven with no concept padding or unnecessary explanation; commands and short lists each earn their place and assume Claude's competence.	3 / 3
Actionability	Quick Start and Brand Sync Workflow give fully executable commands with real flags (e.g., "node scripts/inject-brand-context.cjs --json", "node scripts/extract-colors.cjs --palette"), copy-paste ready.	3 / 3
Workflow Clarity	The Brand Sync Workflow is clearly sequenced with an explicit "Verify" checkpoint (step 3), but it provides no error-recovery feedback loop describing what to do if verification fails, falling short of the score-3 anchor.	2 / 3
Progressive Disclosure	Content is appropriately split with one-level-deep reference and script tables, but several referenced paths (docs/brand-guidelines.md, assets/design-tokens.json, assets/design-tokens.css, templates/brand-guidelines-starter.md) point to files absent from the bundle, breaking navigation.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 clearly answers both what the skill does and when to activate it, with an explicit trigger clause. It is held back from top marks by categorical rather than action-oriented capabilities, missing common trigger variations (logo, brand colors, brand guidelines), and some overlap risk from asset/marketing terms.

Suggestions

Lead with concrete verbs (e.g., "Define brand voice, validate assets, sync design tokens, audit brand consistency") instead of categorical nouns.

Add common trigger terms users would say, such as "logo", "brand colors", and "brand guidelines".

Narrow "asset management" to a brand-specific framing (e.g., "brand asset organization") to reduce overlap with generic asset skills.

Dimension	Reasoning	Score
Specificity	The description enumerates domain facets ("Brand voice, visual identity, messaging frameworks, asset management, brand consistency") but these are categorical nouns rather than concrete actions like "extract", "validate", or "sync", so it names the domain without listing multiple specific actions.	2 / 3
Completeness	It states what the skill covers (brand voice, visual identity, messaging, asset management, consistency) and provides an explicit "Activate for ..." trigger clause, clearly answering both what and when.	3 / 3
Trigger Term Quality	The "Activate for branded content, tone of voice, marketing assets, brand compliance, style guides" clause supplies several natural terms, but omits common core variations a user would say such as "logo", "brand colors", or "brand guidelines".	2 / 3
Distinctiveness Conflict Risk	The brand niche is fairly distinct, but the broad terms "asset management" and "marketing assets" could overlap with generic asset or marketing skills, leaving some conflict risk.	2 / 3
	Total	9 / 12 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
Commit: cc3d1be

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