brand-guidelines-community

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

Quality

48%

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

53%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 well-structured, mostly concise brand reference with concrete color and typography values, but it repeats font guidance across sections, leaves the "smart" styling logic vague, and describes the workflow in prose rather than as a checkpointed sequence.

Suggestions

Consolidate the Poppins/Lora font rules into a single section to remove the repetition across Smart Font Application, Text Styling, and Font Management.

Specify how accent cycling and background-aware color selection should work (e.g., a concrete rule or a short python-pptx RGBColor snippet) to make the guidance executable.

Reformat the Example section as a numbered workflow with an explicit validate/inspect checkpoint, and either add the referenced license file or remove the dangling reference to it.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete color/font tables, but Poppins/Lora guidance is repeated across Smart Font Application, Text Styling, and Font Management sections, and the time-sensitive "Modified in AAS on 2026-09-05" note sits outside a deprecated/old-patterns section.	3 / 5
Actionability	Concrete hex codes, font names, a 24pt threshold, and fallbacks are actionable, but "Smart color selection based on background" and "Cycles through orange, blue, and green accents" are underspecified, and python-pptx RGBColor is named without any executable example.	3 / 5
Workflow Clarity	The Example section gives a prose sequence (inspect fonts, apply colors, export preview, check fallback/contrast) with an implicit verify step, but it lacks a numbered workflow with explicit validation checkpoints; the operation is non-destructive so no cap applies.	3 / 5
Progressive Disclosure	The skill is a compact, self-contained single-page reference with well-organized sections (Colors, Typography, Features, Technical Details, When to Use, Limitations), fitting the simple-skill exception; the only gap is a referenced license file that is not present in any bundle directory.	4 / 5
	Total	13 / 20 Passed

Description

43%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 conveys a clear domain and purpose but uses second-person imperative voice and omits an explicit trigger clause, capping completeness and depressing specificity. Trigger-term coverage is adequate but thin on synonyms.

Suggestions

Rewrite in third person with explicit triggers, e.g. "Applies Anthropic's official brand colors and typography to artifacts. Use when the user requests Anthropic branding, brand colors, visual identity, or company design standards."

Add 2-3 concrete actions (apply brand colors, set typography, style shapes) to lift specificity above the single generic verb "access".

Expand trigger terms with natural synonyms (branding, visual identity, typography, brand colors) to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Anthropic's official brand identity and style resources") but offers only one generic action ("access"), matching the anchor-2 example "Processes PDF files"; the second-person/imperative framing ("use this skill") triggers the voice penalty, reducing specificity by 1.	1 / 5
Completeness	The "what" is clear (access brand identity and style resources) but there is no "Use when..." trigger clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	"brand identity" and "style resources" are relevant keywords a user might say, but common synonyms and variations (brand colors, branding, visual identity, typography, company design standards) are missing, fitting the "some relevant keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The Anthropic-specific scope gives it a clear niche with minimal conflict risk against unrelated skills, though minor overlap remains with the canonical brand-guidelines-anthropic skill it aliases.	4 / 5
	Total	11 / 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: b1aebac

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