CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brand-guidelines-community

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

40

Quality

51%

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

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 body works as a tolerable brand-reference sheet (accurate hex colors and font names) but is padded with thrice-repeated font-fallback details and filler sections, offers no executable example despite naming python-pptx, and defines no procedure for its multi-rule styling behavior. It reads more like a feature list than actionable skill guidance.

Suggestions

Collapse 'Smart Font Application', 'Text Styling', and 'Technical Details/Font Management' into one statement of the font/fallback rules, and delete the filler 'Keywords' and 'When to Use' sections.

Add a short executable example showing the colors applied via python-pptx RGBColor (e.g., RGBColor(0xD9, 0x77, 0x57) for a heading), since python-pptx is already invoked.

Define the ambiguous behaviors: what 'smart color selection based on background' means and how the orange/blue/green accent cycle is assigned to shapes.

DimensionReasoningScore

Conciseness

The body has several padded/redundant sections: font-fallback guidance is repeated nearly verbatim in three places ("Automatically falls back to Arial/Georgia", "Provides automatic fallback to Arial (headings) and Georgia (body)", "Uses system-installed Poppins and Lora fonts when available"), a filler "Keywords" section duplicates description duty, "Smart Font Application" and "Text Styling" restate each other, and "When to Use" is pure filler ('This skill is applicable to execute the workflow or actions described in the overview'). This matches anchor 2 ('Noticeably verbose; several unnecessary explanations or padded sections'); not 1 because it avoids explaining general concepts Claude already knows, and the hex values are real content.

2 / 5

Actionability

Concrete data is present — hex values ('#d97757 - Primary accent', 'Dark: #141413') and named fonts with fallbacks — but no executable guidance: it names "python-pptx's RGBColor class" yet gives no code example or command, and "Smart color selection based on background" is never defined. This matches anchor 3 ('Some concrete guidance but incomplete ... missing key details'); not 4 because there is no copy-paste-ready code or concrete usage step.

3 / 5

Workflow Clarity

No application procedure exists at all: multiple interacting rules are described (fonts to 24pt+ headings, body text in Lora, shapes cycling orange/blue/green, color selection based on background) with no sequence, precedence, or validation for how to actually apply them. This matches anchor 2 ('Rough sequence present but many gaps; steps poorly defined'); not 1 because the styling rules themselves are individually coherent, and the simple-skill exception to score 5 does not apply since the single action is not unambiguous — 'smart color selection' and accent cycling are undefined behaviors.

2 / 5

Progressive Disclosure

The skill is a self-contained single-page reference with no bundle files (references/, scripts/, assets/ absent) and no need for external references, and sections are clearly headed (Brand Guidelines, Features, Technical Details). It does not reach 5: the body runs ~66 lines (above the under-50-lines simple-skill bar) and includes content that should be trimmed (the redundant Keywords and When-to-Use sections), leaving minor organization gaps characteristic of anchor 4.

4 / 5

Total

11

/

20

Passed

Description

40%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 identifies a clear niche (Anthropic's brand) but says nothing concrete about what the skill does and provides no trigger guidance for when to invoke it. The vague verb 'access' and missing 'Use when...' clause leave both the what and the when underspecified, well below the rubric's good example for an identical skill.

Suggestions

Replace the vague 'access' phrasing with concrete actions, e.g., 'Applies Anthropic's official brand colors (#d97757, #6a9bcc, #788c5d) and typography (Poppins/Lora) to documents and presentations.'

Add an explicit trigger clause, e.g., 'Use when the user mentions brand colors, corporate identity, visual formatting, Anthropic styling, or company design standards.'

Include natural synonyms users would say (brand colors, look-and-feel, company design standards) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Anthropic's official brand identity and style resources") but the only action is the generic verb "access" — no concrete actions like applying colors or typography are stated. It matches anchor 2 ('Names the domain but actions are minimal or generic'); not 3 because no 1-2 concrete capabilities are listed, and not 1 because the domain itself is specific rather than abstract filler like 'Helps with documents'.

2 / 5

Completeness

The 'what' is vague — "To access ... brand identity and style resources" never states what the skill actually does (apply styling? retrieve values?) — and the 'when' is entirely absent, with no 'Use when...' clause or equivalent trigger guidance. This matches anchor 2 ('Has a vague what and no when'); not 3 because the 'what' lacks the concrete action level of that anchor's example ('Extract text and tables from PDF files...'), and the rubric's guideline caps completeness anyway when trigger guidance is missing.

2 / 5

Trigger Term Quality

It contains a few relevant natural keywords ("brand identity", "style") but misses common variations and synonyms users would say, such as 'brand colors', 'corporate identity', 'visual formatting', or 'look-and-feel'. This fits anchor 3 ('Some relevant keywords but missing common variations or synonyms'); not 4 because coverage is thin with several natural terms absent.

3 / 5

Distinctiveness Conflict Risk

The phrase "Anthropic's official brand identity and style resources" carves out a clear niche, distinguishable from most skills. Minor overlap remains with generic styling/design/branding skills since no distinct trigger phrases are provided to disambiguate; this fits anchor 4 ('Mostly distinct; minor overlap risk with closely related skills') rather than 5.

4 / 5

Total

11

/

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.

Validation — 15 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/brand-guidelines-community/SKILL.md

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.