Give Your Agent the Sentry Brand-Guidelines Skill

Where this fits

You ask your coding agent to draft a 404 page and it returns 'Page not found. Please use the navigation menu to return to a valid URL.' It is technically correct, but it is not Sentry. This skill plugs the brand-voice gap: the agent sees Sentry's tone rules before writing any user-facing copy. That means fewer prompt rewrites, less manual editing, and a consistent plain-speech-vs-voice decision for every UI string.

Why agents benefit

• The agent selects Plain Speech for buttons, docs, errors, and settings; it reserves Sentry Voice for 404s, empty states, onboarding, and loading screens.
• It converts vague instructions like 'write in Sentry style' into checkable rules: concise, direct, active voice, no jargon.
• It prevents common over-polish: a 404 can be playful, but a Save button cannot.
• It works across generation types—UI text, documentation, marketing copy, and transactional email—without adding a long style guide to each prompt.
• The skill makes tone choices explainable, so you can audit why an empty state came back friendly instead of neutral.

Practical scenarios

New project empty state

You prompt: 'Write the empty state for a project with no events.' The skill routes to Sentry Voice and produces a short, friendly nudge to send the first event. It avoids both dead corporate copy and cheap jokes.

404 page

Sentry Voice is allowed to show personality. Instead of 'Requested resource not found,' the agent writes something like 'You've wandered off the map. Let's get you back.' It stays on-brand without being a creative-writing exercise.

API key validation error

This is Plain Speech territory. The agent renders 'Enter a valid API key'—not 'Your API key does not appear to conform to the expected format.' Users get the action, not a lecture.

Add it to your agent workflow

Install the skill:

npx skills add getsentry/skills --skill brand-guidelines

Then ask: 'Write a 404 message for a Sentry page using brand-guidelines.' The agent applies the tone table automatically. For a UI label, specify 'Plain Speech' to be explicit.

Compare before adopting

Look beyond the tag line. Compare on quality signals: does the README include concrete tone rules and examples? Maintenance freshness: is the repo active and is the author responsive? Alternatives: do you already have a custom brand-voice skill that conflicts with this one? Workflow fit: does your agent generate enough user-facing copy to justify one more skill?

Why it is worth tracking

The skill comes from getsentry, has 974 stars, and is backed by a real design system, not just generic advice. The main quality signal is its tone-selection table and examples, which make the skill useful even outside Sentry as a reference for agent copywriting. Add it to your stack if you often send agents to write UI microcopy; review the project at https://www.openagentskill.com/skills/getsentry-brand-guidelines for the latest community signals before adopting.