CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-guidelines-community

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

44

Quality

31%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/brand-guidelines-community/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

40%

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 lacks explicit trigger guidance for when Claude should select it. It also uses second-person voice ('use this skill') rather than third-person, and fails to enumerate specific capabilities like applying brand colors, typography, or generating branded artifacts.

Suggestions

List specific concrete actions the skill performs, e.g., 'Applies Anthropic's official brand colors, typography, and logo guidelines to artifacts and designs.'

Add an explicit 'Use when...' clause with natural trigger terms like 'brand colors', 'Anthropic style', 'brand guidelines', 'logo usage', 'design standards'.

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

Implementation

22%

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

This skill provides a reasonable brand reference (colors, fonts) but critically lacks actionability—there are no code examples, commands, or step-by-step instructions for actually applying the brand styling. Key information is repeated across multiple sections without adding value, and the 'When to Use' section is a vacuous tautology. To be useful, this skill needs executable code showing how to apply these styles to presentations or documents.

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 workflow: e.g., 1. Open presentation, 2. Iterate slides, 3. Apply heading fonts, 4. Apply body fonts, 5. Apply accent colors to shapes, 6. Save and verify output.

Remove duplicated content—consolidate 'Typography', 'Smart Font Application', 'Text Styling', and 'Font Management' into a single section with the reference values and one code example.

Replace the 'When to Use' section with a concrete trigger description, e.g., 'Use when the user asks to apply Anthropic branding to a PowerPoint file.'

DimensionReasoningScore

Conciseness

The skill contains some redundancy—font application details are repeated across 'Typography', 'Smart Font Application', 'Text Styling', and 'Font Management' sections. The 'When to Use' section is a meaningless tautology. However, the color/typography reference tables themselves are reasonably lean.

2 / 3

Actionability

There is no executable code, no concrete commands, and no examples of how to actually apply these brand styles. It describes what happens ('Applies Poppins font to headings') but never shows how to do it—no python-pptx code snippets, no function calls, no copy-paste ready examples.

1 / 3

Workflow Clarity

There is no workflow, no sequenced steps, and no process for applying brand styling to a document. The content reads as a reference sheet of facts rather than an actionable procedure Claude can follow.

1 / 3

Progressive Disclosure

The content is organized into logical sections with clear headings, which aids navigation. However, there are no references to external files for deeper detail, and the repeated information across sections suggests the structure could be tightened significantly.

2 / 3

Total

6

/

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
sickn33/antigravity-awesome-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.