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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, actionable style guide skill with excellent use of tables and concrete examples that make it immediately usable. Its main weakness is that all content is inlined in a single file rather than using progressive disclosure to separate the overview from detailed reference material. The tone selection table and before/after examples are particularly effective at providing unambiguous guidance.

Suggestions

Split detailed sections like 'UI Element Guidelines', 'Anti-Patterns', and 'Dash Usage' into a separate REFERENCE.md file, keeping only a summary and link in the main SKILL.md

Add a brief review/validation checklist at the end (e.g., 'Before finalizing: check against anti-patterns list, verify tone matches context table, confirm punctuation rules') to strengthen workflow clarity

Dimension	Reasoning	Score
Conciseness	The content is well-organized and mostly efficient. Tables and examples are used effectively to convey information densely. Minor verbosity exists in some sections (e.g., the 'Principles' list under Sentry Voice could be tighter, and some rules like 'Be concise' are things Claude already knows), but overall it respects token budget well for a style guide.	4 / 5
Actionability	Highly actionable with concrete before/after examples, specific word choice tables, clear rules for each UI element type, and structured patterns for error messages, empty states, and confirmation dialogs. The tone selection table provides unambiguous guidance on which tone to use in which context.	5 / 5
Workflow Clarity	For a style/copywriting skill, the workflow is clear: determine context via the tone selection table, apply the appropriate tone's rules, follow general rules. The error message section has a clear 3-step sequence. However, there's no explicit validation step (e.g., 'review against anti-patterns checklist before finalizing'). Since this is not a destructive/batch operation, the missing validation doesn't cap the score, but a review checkpoint would improve it.	4 / 5
Progressive Disclosure	The content is well-structured with clear headers and sections, but at ~150 lines it's moderately long and could benefit from splitting detailed sections (e.g., UI Element Guidelines, Anti-Patterns) into separate reference files. The two external links at the bottom are references rather than structured bundle files. No bundle files are provided to offload detail.	3 / 5
	Total	16 / 20 Passed

Description

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

This is a strong skill description that clearly communicates its purpose, provides an explicit 'Use when' clause with diverse trigger scenarios, and is distinctly scoped to Sentry's brand. Minor improvements could include expanding the action verbs beyond 'write' (e.g., review, edit) and adding a few more synonym trigger terms like 'microcopy' or 'UX writing'.

Dimension	Reasoning	Score
Specificity	Lists several specific content types (UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy) and mentions two tones (Plain Speech and Sentry Voice). Minor gap in not describing what the skill actually does beyond 'write copy' — e.g., does it review, edit, generate from scratch?	4 / 5
Completeness	Clearly answers both 'what' (write copy following Sentry brand guidelines, covering Plain Speech and Sentry Voice tones) and 'when' (explicit 'Use when' clause with a comprehensive list of concrete trigger scenarios).	5 / 5
Trigger Term Quality	Includes many natural trigger terms users would say: 'UI text', 'error messages', 'empty states', 'onboarding flows', '404 pages', 'documentation', 'marketing copy', 'brand guidelines'. Missing some synonyms like 'microcopy', 'UX writing', 'tone of voice', or 'copywriting'.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive — specifically scoped to Sentry brand guidelines with named tones (Plain Speech, Sentry Voice). Very unlikely to conflict with generic writing or other brand skills.	5 / 5
	Total	18 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/brand-guidelines/SKILL.md
Commit: 57c135b

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.