CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-guidelines-community

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

35

Quality

31%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

22%Scale 1-3

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

This skill provides brand color hex values and font names but fails to give Claude any actionable instructions on how to apply them. It reads more like a design spec document than a skill—there are no code examples, no workflow steps, and no concrete commands. The repeated font fallback information and vacuous 'When to Use' section waste tokens without adding value.

Suggestions

Add executable python-pptx code examples showing how to apply brand colors and fonts to slides (e.g., setting font family, applying RGBColor to shapes).

Define a clear step-by-step workflow: e.g., 1. Open presentation, 2. Iterate slides, 3. Apply heading fonts, 4. Apply body fonts, 5. Recolor shapes, 6. Save and verify.

Remove the redundant 'When to Use' section and consolidate the repeated font fallback information into a single location.

Add a concrete example showing input (a plain slide) and expected output (a branded slide) to make the skill truly actionable.

DimensionReasoningScore

Conciseness

Contains some redundancy—font fallback information is repeated across multiple sections (Typography, Smart Font Application, Font Management). The 'When to Use' section is a meaningless tautology. Some sections like 'Features' describe capabilities rather than instruct.

2 / 3

Actionability

No executable code, no concrete commands, no examples of how to actually apply these brand styles. It describes what the styling does but never shows how to do it—no python-pptx code snippets, no workflow for applying colors or fonts to a presentation.

1 / 3

Workflow Clarity

There is no workflow at all—no steps, no sequence, no process for applying brand styling to any artifact. The skill reads as a reference sheet of values without any guidance on how to use them in practice.

1 / 3

Progressive Disclosure

The content is organized into logical sections with clear headings, which is good. However, it's somewhat monolithic with repeated information, and there are no references to external files for deeper details like code examples or templates.

2 / 3

Total

6

/

12

Passed

Description

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.

The description is too vague about what concrete actions the skill performs and uses second-person imperative voice ('use this skill') rather than third-person declarative. It lacks explicit trigger terms and a clear 'Use when...' clause, making it difficult for Claude to reliably select this skill from a large pool.

Suggestions

List specific concrete actions the skill performs, e.g., 'Provides Anthropic's official brand colors, typography, logo usage guidelines, and visual formatting standards.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Anthropic brand colors, logo guidelines, typography, design standards, or visual identity.'

Rewrite in third-person voice (e.g., 'Provides access to...' instead of 'use this skill') to match expected description conventions.

DimensionReasoningScore

Specificity

The description says 'access Anthropic's official brand identity and style resources' which is vague — it doesn't list any concrete actions like applying colors, typography, generating branded assets, etc.

1 / 3

Completeness

The 'what' is weakly stated (access brand resources) and the 'when' is implied by the phrasing 'To access... use this skill' but there is no explicit 'Use when...' clause with trigger scenarios. Per rubric guidelines, missing explicit trigger guidance caps this at 2.

2 / 3

Trigger Term Quality

Contains some relevant keywords like 'brand identity', 'style resources', and 'Anthropic', but misses common variations users might say such as 'brand colors', 'logo', 'typography', 'design guidelines', 'brand guide', or 'visual style'.

2 / 3

Distinctiveness Conflict Risk

Mentioning 'Anthropic's official brand identity' provides some specificity, but 'style resources' is broad enough to overlap with general design or styling skills. It's somewhat distinguishable but not sharply defined.

2 / 3

Total

7

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.