brand-guidelines

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.

Quality

73%

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

Quality

Content

57%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-organized and appropriately short, but the body restates the font-fallback information several times and lacks any executable example or clear procedure, making it more of a feature catalog than actionable guidance.

Suggestions

Collapse the repeated Poppins/Lora fallback details into a single section to remove redundancy and tighten conciseness.

Add a minimal executable snippet (e.g. a python-pptx RGBColor example) so the styling guidance is concrete and copy-paste ready.

Reframe the 'Features'/'Technical Details' lists as a short step-by-step procedure for applying brand styling to an artifact.

Dimension	Reasoning	Score
Conciseness	Mostly efficient lists of colors and features, but the Poppins/Lora fallback information is restated across 'Smart Font Application', 'Text Styling', and 'Font Management', adding repetition rather than new value.	2 / 3
Actionability	Describes capabilities ('Applied via python-pptx's RGBColor class') but provides no executable code or concrete commands to actually apply the styling, so the guidance is incomplete.	2 / 3
Workflow Clarity	As a simple single-task skill it could score higher, but the body describes features rather than a clear single action or sequence, leaving the actual procedure ambiguous.	2 / 3
Progressive Disclosure	Under 50 lines with well-organized sections and no need for external references, satisfying the simple-skill exception for progressive disclosure.	3 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit trigger clause and natural, distinct keywords. It is only slightly limited on specificity, naming just two concrete actions rather than enumerating the full set.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions ('Applies Anthropic's official brand colors and typography') but lists only two actions rather than a comprehensive set of specific operations.	2 / 3
Completeness	Explicitly answers both what it does (applies brand colors and typography) and when to use it via an explicit 'Use it when ...' clause.	3 / 3
Trigger Term Quality	Includes natural terms users would say — 'brand colors', 'style guidelines', 'visual formatting', 'company design standards' — with good coverage.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Anthropic's brand look-and-feel) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: composio-community/open-claude-cowork
Path: .claude/skills/brand-guidelines/SKILL.md
Commit: 52335ef

Reviewed: ~1 month 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.