brand-guidelines-community

To access Anthropic's official brand identity and style resources, use this skill.

Quality

39%

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

Quality

Content

42%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 contains genuinely useful brand specifics (colors, fonts, fallback policy) but undermines them with heavy redundancy — the font guidance is stated four times — plus maintenance/date padding and references to support files that are not present. An instruction-only skill can score well without code, but here the guidance stops short of executable steps and the claimed bundle structure does not exist.

Suggestions

Collapse "Smart Font Application", "Text Styling", and "Font Management" into a single typography section stating the rule once (Poppins for headings 24pt+, Lora for body, Arial/Georgia fallbacks), which would fix the biggest conciseness problem.

Remove the compatibility-alias/AAS maintenance notes and dates from the model-facing body, or move them to a separate metadata file, per the time-sensitive-information guideline.

Either supply the claimed support files (license, referenced instructions) or delete the statements that they exist locally, since progressive disclosure is scored against the actual bundle.

Dimension	Reasoning	Score
Conciseness	The Poppins/Lora font rules are repeated across "Typography", "Smart Font Application", "Text Styling", and "Font Management", and the maintenance section carries time-sensitive dates ("Modified in AAS on 2026-09-05") that add tokens without operational value.	2 / 5
Actionability	Concrete data is present (hex color values, font names, Arial/Georgia fallbacks, python-pptx RGBColor mention), but there is no executable code or command and key details are missing, such as how to actually inspect installed fonts or apply colors in an authoring tool.	3 / 5
Workflow Clarity	"Example and prerequisites" implies a rough sequence (inspect fonts, apply colors, export a preview, check wrapping/contrast), but the steps are not explicitly sequenced and validation checkpoints are implicit rather than instructed.	3 / 5
Progressive Disclosure	Sections are reasonably organized, but the body claims local support content ("The full instructions and support files remain local", "This directory contains instructions and a license") while no such bundle files exist, and at ~90 lines with redundant sections it exceeds the simple-skill exception.	3 / 5
	Total	11 / 20 Passed

Description

36%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 is short and unambiguous about its domain but fails as a trigger description: it states no concrete capability and gives no explicit 'when to use' guidance. It reads closer to the bad examples ("Helps with documents") than to the good ones, which enumerate actions and trigger phrases.

Suggestions

State concrete actions, e.g., "Applies Anthropic's brand colors, typography, and visual styling to artifacts such as slides and documents" instead of the generic "access brand identity and style resources".

Add an explicit trigger clause, e.g., "Use when the user asks for Anthropic-branded styling, brand colors, or company design standards" — its absence currently caps completeness.

Include natural trigger synonyms users would say ("brand colors", "brand guidelines", "Anthropic look-and-feel", "visual formatting") to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Anthropic's official brand identity and style resources") but the only action is the generic "access"; no concrete actions like applying colors or styling artifacts are stated.	2 / 5
Completeness	The "what" is vague ("access brand identity and style resources") and there is no 'Use when...' clause or equivalent trigger guidance, matching the vague-what/no-when anchor.	2 / 5
Trigger Term Quality	"brand identity" and "style" are somewhat natural terms, but common variations users would actually say ("brand colors", "logo", "brand guidelines", "Anthropic brand") are missing.	3 / 5
Distinctiveness Conflict Risk	The Anthropic-brand niche is somewhat specific, but the generic "access style resources" phrasing could overlap with other styling or brand-related skills.	3 / 5
	Total	10 / 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: sickn33/agentic-awesome-skills
Path: skills/brand-guidelines-community/SKILL.md
Commit: 7b534bc

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