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

54%

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

47%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 a concise, well-structured catalogue stub that advertises an upstream skill, but it provides little actionable or workflow guidance beyond pointing to an external repo. It is lean and navigable but lacks concrete execution steps.

Suggestions

Replace the vague 'install the upstream bundle' instruction with concrete, copy-paste-ready commands for locating and installing the upstream skill files.

Inline a minimal Quick Start example (e.g. a sample color/typography snippet or import instruction) so the skill is actionable without leaving SKILL.md.

Remove the verbatim repetition of the frontmatter description in the 'What it does' section to tighten the body further.

Dimension	Reasoning	Score
Conciseness	The body is lean and well under a reasonable token budget, but the 'What it does' section repeats the frontmatter description verbatim and 'A reference for shaping your own' is minor padding that could be trimmed.	4 / 5
Actionability	It offers only one concrete command (`open https://...`) and otherwise high-level hints ('install the upstream bundle into your active agent's skills directory', 'ask the agent to invoke') without the specific steps needed to execute.	2 / 5
Workflow Clarity	A rough sequence is present (inspect upstream README → install bundle → invoke by name/trigger), but the 'install the upstream bundle' step is poorly defined with no concrete commands, leaving significant gaps.	2 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections (What it does, Source, How to use) and the single external reference (upstream repo URL) is one level deep and clearly signaled, though the stub-like nature leaves minor organization gaps.	4 / 5
	Total	12 / 20 Passed

Description

61%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 clearly states what the skill does and uses good natural keywords, but lacks an explicit 'when to use' clause, which caps its completeness. It is reasonably distinct from other skills thanks to the Anthropic-brand niche.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger scenarios (e.g. 'Use when applying Anthropic brand colors, typography, or visual identity to artifacts').

Expand the action list beyond 'colors and typography' to cover what else the skill applies (e.g. logos, spacing, color palettes) for more comprehensive specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (brand colors and typography) and two concrete actions ('Apply ... brand colors and typography'), but coverage is limited to those two actions and not comprehensive.	3 / 5
Completeness	Has a clear 'what' (apply brand colors and typography) but no explicit 'Use when...' clause or equivalent trigger guidance in the description field, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Contains several natural terms a user would say — 'brand colors', 'brand typography', 'visual identity', 'professional design standards' — giving good keyword coverage, though a few synonyms (e.g. 'style guide', 'color palette') are missing.	4 / 5
Distinctiveness Conflict Risk	The 'Anthropic's official brand colors and typography' niche is mostly distinct, but 'visual identity' and 'design standards' terms carry minor overlap risk with general design skills.	4 / 5
	Total	14 / 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: 1a7a23d

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