Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
59
Quality
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/brand-guidelines-community/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly communicates when to use the skill and provides good trigger terms. The main weakness is that the capabilities could be more specific about what concrete actions the skill performs beyond the general 'applies brand colors and typography'. Overall, it follows the good example pattern from the rubric closely.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (brand colors and typography) and general action (applies to artifacts), but doesn't list specific concrete actions like 'format headers', 'apply color palette to charts', or 'style text elements'. | 2 / 3 |
Completeness | Clearly answers both what ('Applies Anthropic's official brand colors and typography to artifacts') and when ('Use it when brand colors or style guidelines, visual formatting, or company design standards apply') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'brand colors', 'style guidelines', 'visual formatting', 'company design standards', 'Anthropic's look-and-feel'. These are terms users would naturally use when requesting brand styling. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Anthropic brand styling. The combination of 'Anthropic's official brand' with specific triggers like 'brand colors' and 'style guidelines' makes it unlikely to conflict with general formatting or other company-specific skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a bare table of contents rather than actionable guidance. It lacks any concrete instructions, examples, or workflow for applying Anthropic brand styling. The structure suggests progressive disclosure but fails to provide enough context in the main file to be useful without reading all sub-skills.
Suggestions
Add a quick-start section with a concrete example showing how to apply Anthropic brand colors/typography to a common artifact (e.g., HTML, CSS snippet)
Include brief descriptions for each sub-skill link explaining what it covers and when to use it
Add a simple workflow showing the typical sequence for applying brand styling (e.g., 1. Check colors, 2. Apply typography, 3. Verify contrast)
Remove the keywords section and 'Fractal Skills' jargon - these add no actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes unnecessary elements like the emoji, 'Knowledge Modules (Fractal Skills)' jargon, and a keywords section that adds little value. The overview sentence is somewhat redundant. | 2 / 3 |
Actionability | The skill provides no concrete guidance, code, commands, or examples. It only lists links to sub-skills without any executable or actionable content in the main file itself. | 1 / 3 |
Workflow Clarity | There is no workflow, sequence, or process described. The numbered list appears to be a table of contents rather than steps to follow, with no indication of when or how to apply these sub-skills. | 1 / 3 |
Progressive Disclosure | The skill does reference sub-skills appropriately (one level deep), but the references lack context about what each contains or when to use them. No quick-start content exists before jumping to references. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
3395991
Table of Contents
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.