brand-guidelines

Apply Anthropic's official brand colors and typography to artifacts for consistent visual identity and professional design standards. A reference for shaping your own.

Quality

51%

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 ./skills/brand-guidelines/SKILL.md

Quality

Content

46%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.

This is a well-structured but thin catalogue stub: it is honest about being a pointer to the upstream skill, yet it provides no executable path to actually installing or running that skill. Sections are clear and short, with some redundancy against the frontmatter.

Suggestions

Replace the vague install direction with a concrete, executable command (e.g., a git clone or copy into the skills directory with real paths) so the main workflow step is actionable.

Delete the "What it does" section (it repeats the frontmatter description verbatim) and trim the "Source" section's duplication of frontmatter metadata.

Fix the "How to use" flow so the code block matches the step it claims to illustrate — currently the colon promises installation but the block only opens the upstream URL.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept over-explanation, but "What it does" duplicates the frontmatter description verbatim and "Source" restates the upstream URL and category already present in the YAML — clear tightening opportunities.	3 / 5
Actionability	The only executable command is `open <upstream URL>`, which just opens a browser to inspect the README; the critical step "install the upstream bundle into your active agent's skills directory" is a high-level hint with no command, path, or method, so the actual task has no concrete steps.	2 / 5
Workflow Clarity	A rough ordered sequence exists (inspect upstream → install bundle → invoke by name or trigger phrase), but the central install step is undefined, and the colon before the code block misleadingly suggests it performs the install rather than mere inspection. No destructive or batch operations, so no hard cap applies.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent), so this scores on structure alone: the body is short with clean, well-labeled sections and a clearly signaled one-level pointer to the upstream repository. Not 5 because all real reference material lives outside the bundle entirely.	4 / 5
	Total	12 / 20 Passed

Description

56%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 states a clear, distinctive capability but omits any usage trigger guidance, and it is undercut by the vague second-person meta fragment "A reference for shaping your own". Trigger-term coverage within the description itself is decent but misses several natural synonyms.

Suggestions

Add an explicit 'Use when...' clause (e.g., "Use when brand colors or style guidelines, visual formatting, or company design standards apply") to satisfy completeness.

Remove the vague meta fragment "A reference for shaping your own" and write the capability in third person ("Applies Anthropic's official brand colors and typography...").

Broaden natural trigger terms to include "brand guidelines", "style guidelines", "look-and-feel", and "design standards" synonyms for fuller keyword coverage.

Dimension	Reasoning	Score
Specificity	"Apply Anthropic's official brand colors and typography to artifacts" names the domain and 1-2 concrete actions (anchor 3), but the trailing second-person fragment "A reference for shaping your own" triggers the rubric's -1 voice penalty, and that fragment is vague filler rather than a capability.	2 / 5
Completeness	The 'what' is clear (apply Anthropic brand colors and typography), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description; "for consistent visual identity" states a purpose, not a usage condition.	3 / 5
Trigger Term Quality	Natural terms are present — "brand colors", "brand typography", "visual identity", "professional design standards" — giving good keyword coverage, though common variants like "brand guidelines", "style guidelines", and "look-and-feel" are missing.	4 / 5
Distinctiveness Conflict Risk	"Anthropic's official brand colors and typography" carves a clear niche with minimal conflict risk, though generic design/styling phrasing ("visual identity", "professional design standards") leaves minor overlap with general design skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/brand-guidelines/SKILL.md
Commit: 1b47e60

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