CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-guidelines

Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.

65

Quality

79%

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/SKILL.md

The canonical home for this skill is brand-guidelines in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable brand-voice reference that uses tables and good/bad examples to deliver concrete guidance without over-explaining concepts Claude already knows. It is a single-purpose reference skill whose tone-selection decision procedure is clear, with only minor organization and conciseness refinements possible.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — rules and examples live in tight tables ("Instead of / Write," "Avoid / Prefer") with no padding about what a 404 or empty state is; a few prose sections like the dash-usage paragraph could be trimmed, keeping it just below 5.

4 / 5

Actionability

As an instruction-only skill it provides concrete, copy-paste-ready guidance: explicit do/don't example tables, numbered error-message structure ("Say what happened / why / what to do next"), and good/bad pairs; minor gaps (e.g., no example for confirmation dialogs) hold it at 4.

4 / 5

Workflow Clarity

Tone selection is a clear decision procedure (context table + "Default to Plain Speech" rule) and element guidelines are well-sequenced; it is a reference guideline rather than a multi-step destructive process, so checkpoints are not strictly required, but the absence of an explicit review/validate step keeps it at 4.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Tone Selection, Plain Speech, Sentry Voice, General Rules, UI Element Guidelines, Anti-Patterns) with two one-level-deep external references signaled at the end; no bundle files exist, and inlining the guideline is appropriate, but a couple of sections (dash usage, word choices) could arguably live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

83%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, third-person description that clearly states what the skill does and when to use it with concrete trigger phrases. It is specific and well-scoped to Sentry brand voice, with only minor gaps in trigger synonym coverage.

DimensionReasoningScore

Specificity

Names the domain (Sentry brand copy) and enumerates many concrete content types — "UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy" — but the underlying action is a single "Write copy" applied across surfaces, so it falls just below the comprehensive multi-action anchor of 5.

4 / 5

Completeness

Explicitly answers both what ("Write copy following Sentry brand guidelines... Covers both Plain Speech (default) and Sentry Voice tones") and when ("Use when writing UI text, error messages, empty states...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural keyword coverage ("error messages," "empty states," "404 pages," "marketing copy," "user-facing content") that users would realistically say; stops short of 5 because it lacks synonyms and file/format extensions for full comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The "Sentry brand guidelines" framing carves a clear niche with distinct triggers and minimal conflict risk, but the underlying surfaces (UI text, docs, marketing) overlap with general copywriting skills, keeping it just below 5.

4 / 5

Total

17

/

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.