brand-guidelines-community

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

Quality

36%

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-claude/skills/brand-guidelines-community/SKILL.md

Quality

Content

40%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 content is well-sectioned and concise enough, but it describes the skill's behavior rather than instructing how to execute it — there is no code, no sequenced workflow, and no validation. It works as an overview but not as actionable guidance.

Suggestions

Add at least one copy-paste-ready code example showing how to apply a brand color and font via python-pptx (e.g. RGBColor usage and run.font.name assignment).

Provide a short numbered workflow (open presentation -> apply colors -> apply fonts -> save) with a validation/verification step before final save.

Deduplicate the font-fallback information so it appears once, removing the repetition across Features and Technical Details.

Dimension	Reasoning	Score
Conciseness	The body is list-based and reasonably short, but the font-fallback behavior is restated across 'Smart Font Application', 'Text Styling', and 'Technical Details', and color/font assignments are duplicated between Features sections.	3 / 5
Actionability	The skill describes features (e.g. 'Applied via python-pptx's RGBColor class', specific hex values) but provides no executable code or commands, so Claude cannot act on it without inventing the implementation.	2 / 5
Workflow Clarity	No sequenced workflow or validation is given; the 'When to Use' section is circular ('execute the workflow or actions described in the overview'), and applying formatting to presentations is a batch-style operation with no checkpoints.	2 / 5
Progressive Disclosure	The body is under 50 lines with clear section headers and needs no external references, but the overlap between 'Features' and 'Technical Details' leaves minor organization gaps.	4 / 5
	Total	11 / 20 Passed

Description

32%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 names a recognizable niche, but it is vague on concrete actions and lacks an explicit trigger clause, leaving both the 'what' and 'when' underspecified. It reads more as a pointer than an actionable, well-triggered description.

Suggestions

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

Add an explicit 'Use when...' trigger clause listing natural phrases users would say, such as 'Use when the user mentions brand colors, styling, visual formatting, or company design standards.'

Drop the filler 'use this skill' tail and instead state the capability directly in third person.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Anthropic's official brand identity and style resources') but the only action is the generic verb 'access', with no concrete actions such as applying colors or typography.	2 / 5
Completeness	It offers only a vague 'what' ('access... resources') and no explicit 'when' trigger clause — the guidance 'use this skill' is circular rather than a real usage trigger.	2 / 5
Trigger Term Quality	'brand identity and style resources' provides a couple of relevant keywords, but it omits the natural trigger phrases users would actually say (e.g., 'brand colors', 'styling', 'visual formatting') that only appear in the body.	2 / 5
Distinctiveness Conflict Risk	'Anthropic's official brand identity' carves out a fairly distinct niche with only minor overlap risk against general styling/design skills.	4 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/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.