CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

95

6.18x
Quality

59%

Does it follow best practices?

Impact

99%

6.18x

Average score across 10 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/anthropic-brand-guidelines/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 delivers the essential brand data (hex palettes, font names with size thresholds and fallbacks) in a cleanly sectioned layout, but roughly a third of it is duplicated across three sections and it never shows how to apply anything. There are no steps or decision rules for color selection and accent cycling. As an instruction document it reads more like a feature list of an undescribed tool than actionable guidance.

Suggestions

Consolidate the duplicated font guidance: merge 'Smart Font Application', 'Text Styling', and 'Font Management' into a single typography section stating the rule once (Poppins for headings 24pt+, Lora for body, Arial/Georgia fallbacks).

Add a short executable example showing application in practice, e.g. a python-pptx snippet using RGBColor(0xd9, 0x77, 0x57) to set a heading color, since python-pptx is already referenced.

Define the ambiguous decision rules: specify how 'smart color selection based on background' works and the order/logic for cycling through orange, blue, and green accents.

DimensionReasoningScore

Conciseness

The font application rules are stated three times — 'Applies Poppins font to headings (24pt and larger)' in Smart Font Application, 'Headings (24pt+): Poppins font' in Text Styling, and 'Uses system-installed Poppins and Lora fonts when available' in Font Management — plus filler like 'Maintains visual interest while staying on-brand'. This matches the anchor for several unnecessary or padded sections; it avoids a 1 because it never explains concepts Claude already knows.

2 / 5

Actionability

Concrete parameters are present (hex values like '#d97757', 'Poppins (24pt and larger)', 'Applied via python-pptx's RGBColor class') but there is no executable code or command anywhere, so key execution details are missing. This sits between anchor 2 (high-level hints, missing steps) and anchor 3 (concrete guidance but incomplete).

3 / 5

Workflow Clarity

No sequence of steps exists — the body is a feature listing, and application rules are undefined ('Smart color selection based on background', 'Cycles through orange, blue, and green accents' with no logic or order given). The simple-skill exception does not apply because the single action is not unambiguous, placing this between anchor 1 (no sequence) and anchor 3 (sequence with gaps).

2 / 5

Progressive Disclosure

The body (~68 lines) has clear section headers (Brand Guidelines, Features, Technical Details) with no nested references and no bundle files, so nothing is buried or inlined that belongs elsewhere. It falls short of 5 because the Features and Technical Details sections overlap heavily, a minor organization gap matching anchor 4.

4 / 5

Total

11

/

20

Passed

Description

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

A strong description that clearly states both capability and explicit usage triggers, and is well niched to the Anthropic brand. Its main weakness is generality — 'any sort of artifact' and only two named actions keep specificity at the middle anchor. This is a solid, trigger-rich description with only minor overlap risk against generic styling skills.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — 'Applies Anthropic's official brand colors and typography' — but leaves the target generic ('any sort of artifact'), matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because it does not list several specific actions, and not a 2 because the actions are named rather than purely generic.

3 / 5

Completeness

It explicitly answers both 'what' ('Applies Anthropic's official brand colors and typography to any sort of artifact') and 'when' with concrete trigger phrases ('Use it when brand colors or style guidelines, visual formatting, or company design standards apply'). This matches the top anchor's structure and is clearly above the anchor-4 example whose 'when' clause is bare.

5 / 5

Trigger Term Quality

'brand colors', 'style guidelines', 'visual formatting', and 'company design standards' are natural phrases users would say, giving good keyword coverage. It falls short of 5 because common synonyms like 'on-brand', 'branding', or 'make it look Anthropic' are missing.

4 / 5

Distinctiveness Conflict Risk

'Anthropic's official brand' carves out a clear niche with distinct triggers, but 'visual formatting' and 'any sort of artifact' leave minor overlap risk with generic styling or design skills. It is mostly distinct rather than fully minimal-conflict, so it fits the anchor 4 example better than 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
boisenoise/skills-collections
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.