Official agent skill

Brand Guidelines

Write copy following Sentry brand guidelines. An agent skill from getsentry/skills.

OfficialApache-2.0Auto-check passedMarketing & SEO

Install Brand Guidelines

skills CLI

$ npx skills add getsentry/skills --skill brand-guidelines -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install getsentry/skills brand-guidelines --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brand-guidelines .claude/skills/brand-guidelines && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "brand-guidelines" agent skill from https://github.com/getsentry/skills/tree/main/skills/brand-guidelines into .claude/skills/brand-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-guidelines", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/getsentry/skills/tree/main/skills/brand-guidelines

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add getsentry/skills --skill brand-guidelines -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install getsentry/skills brand-guidelines --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/brand-guidelines .agents/skills/brand-guidelines && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "brand-guidelines" agent skill from https://github.com/getsentry/skills/tree/main/skills/brand-guidelines into .agents/skills/brand-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-guidelines", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add getsentry/skills --skill brand-guidelines -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install getsentry/skills brand-guidelines --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/brand-guidelines .cursor/skills/brand-guidelines && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "brand-guidelines" agent skill from https://github.com/getsentry/skills/tree/main/skills/brand-guidelines into .cursor/skills/brand-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-guidelines", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/getsentry/skills.git --path skills/brand-guidelines

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add getsentry/skills --skill brand-guidelines -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install getsentry/skills brand-guidelines --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/brand-guidelines .gemini/skills/brand-guidelines && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "brand-guidelines" agent skill from https://github.com/getsentry/skills/tree/main/skills/brand-guidelines into .gemini/skills/brand-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-guidelines", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install getsentry/skills brand-guidelines

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add getsentry/skills --skill brand-guidelines -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/brand-guidelines .github/skills/brand-guidelines && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "brand-guidelines" agent skill from https://github.com/getsentry/skills/tree/main/skills/brand-guidelines into .github/skills/brand-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-guidelines", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add getsentry/skills --skill brand-guidelines -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install getsentry/skills brand-guidelines --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/brand-guidelines .opencode/skills/brand-guidelines && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "brand-guidelines" agent skill from https://github.com/getsentry/skills/tree/main/skills/brand-guidelines into .opencode/skills/brand-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-guidelines", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: brand-guidelines
GitHub stars: 1k
Used in: 3 other repos
Token cost: ~1.3k tokens
SKILL.md length: 644 words
Files: 1
Skills in repo: 27
Repo updated: Oct 2, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Write copy following Sentry brand guidelines. An agent skill from getsentry/skills.

Works in 5 steps: Be concise - Use the fewest words needed → Be direct - Tell users what to do, not… → Use active voice - "Save your changes"… → …
Writing UI text
SKILL.md covers Tone Selection, Plain Speech (Default), Sentry Voice and General Rules, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Brand Guidelines is an agent skill from getsentry/skills, published by the product's own GitHub organization. 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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Brand strategy and identity and Copywriting. It works with Sentry. The repository describes itself as: Agent Skills used by the Sentry team for development. The licence is Apache-2.0.

When your agent uses it

Writing UI text
Onboarding flows
Any user-facing content

Example prompts

“/brand-guidelines”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Be concise - Use the fewest words needed
Be direct - Tell users what to do, not what they can do
Use active voice - "Save your changes" not "Your changes will be saved"
Avoid jargon - Use simple words users understand
Be specific - "3 errors found" not "Some errors found"

What it can do on your machine

Read from SKILL.md and the folder at commit d18b7aa. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- develop.sentry.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Brand Guidelines loads about 1.3k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 644 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~66
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from getsentry/skills at commit d18b7aa, republished under its Apache-2.0 licence (© getsentry). 644 words, ~1,310 tokens.

Download SKILL.mdSave it as .claude/skills/brand-guidelines/SKILL.md (or your agent's skills folder).

name: brand-guidelines
description: 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.

Brand Guidelines

Write user-facing copy following Sentry's brand guidelines.

Tone Selection

Choose the appropriate tone based on context:

Use Plain Speech	Use Sentry Voice
Product UI (buttons, labels, forms)	404 pages
Documentation	Empty states
Error messages	Onboarding flows
Settings pages	Loading states
Transactional emails	"What's New" announcements
Help text	Marketing copy

Default to Plain Speech unless the context specifically calls for personality.

Plain Speech (Default)

Plain Speech is clear, direct, and functional. Use it for most UI elements.

Rules

Be concise - Use the fewest words needed
Be direct - Tell users what to do, not what they can do
Use active voice - "Save your changes" not "Your changes will be saved"
Avoid jargon - Use simple words users understand
Be specific - "3 errors found" not "Some errors found"

Examples

Instead of	Write
"Click here to save your changes"	"Save"
"You can filter results by date"	"Filter by date"
"An error has occurred"	"Something went wrong"
"Please enter a valid email address"	"Enter a valid email"
"Are you sure you want to delete?"	"Delete this item?"

Sentry Voice

Sentry Voice adds personality in appropriate moments. It's empathetic, self-aware, and occasionally snarky.

Principles

Empathetic snark - Direct frustration at the situation, never the user
Self-aware - Acknowledge the absurdity of software
Fun but functional - Personality should enhance, not obscure meaning
Earned moments - Only use when users have time to appreciate it

Examples

404 Pages:

"This page doesn't exist. Maybe it never did. Maybe it was a dream. Either way, let's get you back on track."

Empty States:

"No errors yet. Enjoy this moment of peace while it lasts."

Onboarding:

"Let's get your first error. Don't worry, it's not as scary as it sounds."

Loading States:

"Crunching the numbers..." "Fetching your data..."

When NOT to Use Sentry Voice

Error messages (users are frustrated)
Settings pages (users are focused)
Documentation (users need information)
Billing/payment flows (users need trust)

General Rules

Spelling and Grammar

Use American English spelling (color, not colour)
Use Title Case for headings and page titles
Use Sentence case for body text, buttons, and labels

Punctuation

No exclamation marks in UI text (exception: celebratory moments)
No periods in short UI labels or button text
Use periods in complete sentences and help text
No ALL CAPS except for acronyms (API, SDK, URL)

Show full SKILL.md (260 more words)Show less

Word Choices

Avoid	Prefer
Please	(omit)
Sorry	(be specific about the problem)
Error occurred	Something went wrong
Invalid	(explain what's wrong)
Success!	(describe what happened)
Oops	(be specific)

Dash Usage

Type	Use	Example
Hyphen (-)	Compound words, ranges	"real-time", "1-10"
En-dash (--)	Ranges, relationships	"2023--2024", "parent--child"
Em-dash (---)	Interruption, emphasis	"Errors---even small ones---matter"

In most UI contexts, use hyphens. Reserve en-dashes for date ranges and em-dashes for longer prose.

UI Element Guidelines

Buttons

Use action verbs: "Save", "Delete", "Create"
Be specific: "Create Project" not just "Create"
Max 2-3 words when possible
No periods or exclamation marks

Error Messages

Say what happened
Say why (if helpful)
Say what to do next

Good: "Could not save changes. Check your connection and try again." Bad: "Error: Save failed."

Empty States

Explain what would normally be here
Provide a clear action to populate the state
Sentry Voice is appropriate here

Good: "No projects yet. Create your first project to start tracking errors."

Confirmation Dialogs

Make the action clear in the title
Explain consequences if destructive
Use specific button labels ("Delete Project", not "OK")

Tooltips and Help Text

Keep under 2 sentences
Explain the "why", not just the "what"
Link to docs for complex topics

Anti-Patterns

Avoid these common mistakes:

Robot speak: "Item has been successfully deleted" -> "Deleted"
Passive voice: "Changes were saved" -> "Changes saved"
Unnecessary words: "In order to" -> "To"
Hedging: "This might cause..." -> "This will cause..."
Double negatives: "Not unlike..." -> "Similar to..."
Marketing speak in UI: "Supercharge your workflow" -> "Speed up your workflow"

References

Files

Just SKILL.md in skills/brand-guidelines of getsentry/skills.

Open the folder on GitHubat commit d18b7aa

Used in 3 other repositories

We found 12 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in getsentry/skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Brand Guidelines next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Brand Guidelines compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Brand Guidelines this skillgetsentry/skills	1k	3 repos	~1.3k	Automated safety check: Pass	Apache-2.0	5 days ago
Ad CreativeLeoYeAI/openclaw-marketing-skills	1k	8 repos	~3.4k	Automated safety check: Pass	Custom licence	4 mo ago
Amazon Listing Optimizationnexscope-ai/Amazon-Skills	735	2 repos	~4.3k	Automated safety check: Pass	MIT	1 mo ago
Meta Ad Builderkrusemediallc/arcads-claude-code	1.6k	—	~1.7k	Automated safety check: Notes	MIT	15 days ago
Hook MethodologyDV0x/creative-ad-agent	119	—	~3.1k	Automated safety check: Pass	MIT	1 mo ago
Launch ItAIDevGTM/gtm-cofounder	310	—	~1.4k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Ad Creative
LeoYeAI/openclaw-marketing-skills
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform.
1k GitHub starsUsed in 8 repos~3.4k tokens
Marketing & SEOAuto-check passed
Amazon Listing Optimization
nexscope-ai/Amazon-Skills
Amazon listing builder and optimizer for sellers. An agent skill from nexscope-ai/Amazon-Skills.
735 GitHub starsUsed in 2 repos~4.3k tokens
Marketing & SEOAuto-check passed
Meta Ad Builder
krusemediallc/arcads-claude-code
Publish finished creatives as live Meta (Facebook/Instagram) ads via the Meta Marketing API, plus research and ad-copy support.
1.6k GitHub stars~1.7k tokensUpdated 15 days ago
Marketing & SEOAuto-check: notes
Hook Methodology
DV0x/creative-ad-agent
Generates conversion-focused ad copy through research-first extraction.
119 GitHub stars~3.1k tokensUpdated 1 mo ago
Marketing & SEOAuto-check passed
Launch It
AIDevGTM/gtm-cofounder
Plan a developer launch (Show HN, Reddit, Product Hunt) that earns goodwill instead of a flaming.
310 GitHub stars~1.4k tokensUpdated 2 days ago
Marketing & SEOAuto-check passed
Ad Creative
freekmurze/dotfiles
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform.
1k GitHub starsUsed in 2 repos~3.3k tokens
Marketing & SEOAuto-check passed

Questions about Brand Guidelines

What does Brand Guidelines do?

Write copy following Sentry brand guidelines. An agent skill from getsentry/skills. Brand Guidelines is an agent skill from getsentry/skills, published by the product's own GitHub organization. Write copy following Sentry brand guidelines.

When should I use Brand Guidelines?

Brand Guidelines fits situations like: writing UI text; onboarding flows; any user-facing content.

How do I install Brand Guidelines in Claude Code?

Run `npx skills add getsentry/skills --skill brand-guidelines -a claude-code`. Or copy the skill folder (skills/brand-guidelines in getsentry/skills) into .claude/skills/brand-guidelines in your project. Claude Code loads it when a task matches its description.

How do I install Brand Guidelines in Codex?

Run `npx skills add getsentry/skills --skill brand-guidelines -a codex`. Or copy the skill folder (skills/brand-guidelines in getsentry/skills) into .agents/skills/brand-guidelines in your project. Codex loads it when a task matches its description.

Can I use Brand Guidelines in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/skills --skill brand-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brand-guidelines, .gemini/skills/brand-guidelines, .github/skills/brand-guidelines and .opencode/skills/brand-guidelines in your project.

What does Brand Guidelines need to run?

SKILL.md names no scripts, command-line tools or credentials: Brand Guidelines is instructions for the agent only.

Does Brand Guidelines access the network?

SKILL.md names 1 domain. As links in the text: develop.sentry.dev. This is read from the text; nothing was executed.

Is Brand Guidelines safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Brand Guidelines use?

Brand Guidelines is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brand Guidelines use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Brand Guidelines?

Skills that share tags, products or a category with Brand Guidelines: Ad Creative (LeoYeAI/openclaw-marketing-skills, 1k stars), Amazon Listing Optimization (nexscope-ai/Amazon-Skills, 735 stars), Meta Ad Builder (krusemediallc/arcads-claude-code, 1.6k stars) and Hook Methodology (DV0x/creative-ad-agent, 119 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brand Guidelines?

getsentry (a GitHub organization, an official publisher) maintains it in getsentry/skills, which has 1,037 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 2, 2026.

Source: getsentry/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Brand Guidelines

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Brand Guidelines

Tone Selection

Plain Speech (Default)

Rules

Examples

Sentry Voice

Principles

Examples

When NOT to Use Sentry Voice

General Rules

Spelling and Grammar

Punctuation

Word Choices

Dash Usage

UI Element Guidelines

Buttons

Error Messages

Empty States

Confirmation Dialogs

Tooltips and Help Text

Anti-Patterns

References

Files

Used in 3 other repositories

Compare with similar skills

Similar skills

More from getsentry/skills

Related

Questions about Brand Guidelines