CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-guidelines-anthropic

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

40

Quality

38%

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/skills/brand-guidelines-anthropic/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

28%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 tidy, well-headed reference for brand colors and typography but is descriptive rather than instructional: it repeats font facts across three sections and provides no executable code or workflow despite being a code-driven styling skill. Its strongest point is clear section structure.

Suggestions

Add an executable python-pptx snippet showing RGBColor usage and font application so the guidance is copy-paste ready.

Collapse the duplicated Poppins/Lora/Arial/Georgia material into a single typography section to remove the padding across 'Smart Font Application', 'Text Styling', and 'Font Management'.

Provide a short sequenced workflow (load presentation -> apply heading/body fonts -> apply accent colors -> verify) so the styling process is unambiguous.

DimensionReasoningScore

Conciseness

The Poppins/Lora/Arial/Georgia facts are restated nearly verbatim across 'Smart Font Application', 'Text Styling', and 'Font Management', and the Overview repeats the description, constituting several padded redundant sections that fit the 'noticeably verbose' anchor.

2 / 5

Actionability

Despite referencing python-pptx's RGBColor class and system fonts, the body gives only high-level descriptions ('Applies Poppins font to headings', 'Cycles through accents') with no executable code, imports, or commands, matching the 'minimal concrete guidance; high-level hints' anchor.

2 / 5

Workflow Clarity

The body is a descriptive feature/technical-detail list with no real sequence from input to styled output and no validation; the implicit order (fonts then colors then accents) is at best a rough sequence with major gaps, fitting the score-2 anchor.

2 / 5

Progressive Disclosure

No bundle files exist, so the single ~70-line document relies on clean section headers but keeps color/typography/reference material inline with some organizational redundancy, landing at 'some structure but could be better organized'.

3 / 5

Total

9

/

20

Passed

Description

48%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 domain but is light on concrete actions and lacks an explicit trigger clause, capping completeness at 3. It is reasonably distinct from other skills, which is its strongest dimension.

Suggestions

Replace the generic verb 'access' with 2-3 concrete actions, e.g. 'Applies Anthropic's brand colors, typography, and visual styling to artifacts'.

Add an explicit trigger clause such as 'Use when the user wants to apply Anthropic branding, brand colors, or visual style to a document or presentation'.

Surface natural trigger synonyms users actually say ('brand colors', 'Anthropic look-and-feel', 'style my slides') directly in the description rather than only in the body keywords list.

DimensionReasoningScore

Specificity

The description names the domain ('Anthropic's official brand identity and style resources') but offers only the single generic verb 'access', matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions needed for a 3.

2 / 5

Completeness

It gives a clear 'what' (access brand identity/style resources) but the 'when' is only the weak boilerplate 'use this skill' with no explicit trigger conditions, so per the missing-'Use when'-clause cap it stays at 3.

3 / 5

Trigger Term Quality

The phrase 'brand identity and style resources' supplies some relevant keywords, but natural user variations like 'brand colors', 'style my slides', or 'Anthropic look-and-feel' are missing, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Anthropic's official brand identity and style resources' carves a fairly distinct niche with only minor overlap risk against general styling/formatting skills, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.