brand-guidelines-community

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

Quality

40%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/brand-guidelines-community/SKILL.md

Quality

Content

38%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 skill body is well-structured and self-contained for a simple brand-styling task, but it is padded with repeated font/color details and provides no executable code or concrete application sequence. It describes what the skill does rather than showing how to do it.

Suggestions

Consolidate the repeated Poppins/Lora fallback details into a single Typography section and remove the near-verbatim "When to Use" restatement.

Add at least one executable code snippet showing how to apply brand colors (RGBColor) and fonts to an artifact via python-pptx.

Specify how accent colors are chosen (the selection rule for "smart color selection based on background") so the single action is unambiguous.

Dimension	Reasoning	Score
Conciseness	The Poppins/Lora-with-Arial/Georgia-fallback detail is repeated across three sections (Smart Font Application, Text Styling, Font Management) and the "When to Use" section restates the description verbatim, making it noticeably padded.	2 / 5
Actionability	The body only describes behavior in bullets (e.g., "Applied via python-pptx's RGBColor class") without any executable code or commands, leaving the specific steps to execute missing.	2 / 5
Workflow Clarity	As a single-purpose styling skill the action is described, but "smart color selection" and "cycles through accents" are not precisely sequenced and there is no validation checkpoint, so the workflow is only partially clear.	3 / 5
Progressive Disclosure	The body is well-organized into clear sections with no external references and is appropriately self-contained for a simple skill, though it slightly exceeds the 50-line simple-skill threshold and carries some redundant detail.	4 / 5
	Total	11 / 20 Passed

Description

41%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 correctly identifies the brand-styling niche and includes an explicit trigger directive, but it is vague on concrete actions and lacks natural trigger phrases and a concrete "when" scenario. It reads as a generic access pointer rather than a precise, comprehensive trigger.

Suggestions

Replace the generic verb "access" with concrete actions (e.g., "Applies Anthropic's brand colors and typography to artifacts").

Add a concrete 'Use when...' clause naming natural triggers (e.g., "Use when styling slides or documents with Anthropic brand colors, fonts, or visual identity").

Fold one or two natural user keywords (brand colors, typography, styling, company design standards) into the description itself rather than only the body.

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," which is minimal rather than a discrete concrete operation.	2 / 5
Completeness	It offers a weak "what" (access brand resources) and an explicit but generic "use this skill" directive with no concrete trigger scenario, so the "when" is only weakly implied and caps the score at 3.	3 / 5
Trigger Term Quality	The description contains no natural trigger phrases a user would say; "brand identity and style resources" is domain-specific but lacks the conversational keywords that live only in the body.	2 / 5
Distinctiveness Conflict Risk	Brand identity and style styling is a fairly distinct niche with minor overlap risk against general design/styling skills, though "access...resources" is generic enough to leave a small conflict window.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/brand-guidelines-community/SKILL.md
Commit: 57c135b

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