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.

70

Quality

86%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 guideline that avoids over-explaining and uses concrete examples effectively. The main gap is the absence of an explicitly sequenced writing workflow with validation checkpoints.

Suggestions

Add a short numbered workflow at the top (e.g., 1. identify content type, 2. select tone via the table, 3. apply rules, 4. check against Anti-Patterns) to make the process explicit rather than implicit.

Trim a few before/after example rows that simply restate their adjacent rule (e.g., the 'Please' -> '(omit)' row duplicates the word-choice rule) to tighten the token budget.

Consider moving the Dash Usage table and UI Element Guidelines into a short reference file if the skill grows, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Efficient use of tables and before/after examples to convey Sentry-specific voice guidance Claude would not already know; no padding with general concepts, though a few example rows slightly restate their adjacent rules and could be trimmed.

4 / 5

Actionability

Highly actionable for an instruction-only skill: concrete before/after copy swaps, explicit rules (max 2-3 words, no periods), and good/bad error-message and empty-state templates that are effectively copy-paste ready and cover common UI cases.

5 / 5

Workflow Clarity

A clear tone-selection decision table plus numbered step structures for error messages and empty states provide a usable sequence, but the overall pick-tone-then-write flow is implicit rather than explicitly sequenced with checkpoints.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and tables in a single self-contained file, plus two clearly signaled one-level-deep external URL references; no bundle files exist, and the inline content is appropriately sized so the lack of file splitting is not a defect.

4 / 5

Total

17

/

20

Passed

Description

91%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, well-constructed description that clearly states capability and trigger contexts with natural user-facing keywords. Minor improvement possible by sharpening the distinctiveness of broad triggers like 'documentation' and 'marketing copy'.

DimensionReasoningScore

Specificity

Names the domain ('Write copy following Sentry brand guidelines') and enumerates many concrete content contexts (UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy), giving broad coverage though the core verb is a single action rather than multiple distinct actions.

4 / 5

Completeness

Explicitly answers both 'what' ('Write copy following Sentry brand guidelines') and 'when' ('Use when writing UI text, error messages... or any user-facing content') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural keyword coverage — 'UI text', 'error messages', 'empty states', 'onboarding flows', '404 pages', 'documentation', 'marketing copy' are exactly the phrases a user would say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

The Sentry-specific brand framing and distinct tone triggers (404 pages, Sentry Voice) carve a clear niche, but broad terms like 'documentation' and 'marketing copy' create minor overlap risk with general writing skills.

4 / 5

Total

18

/

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.