Sentry backend conventions for logging, tracing/spans, span/tag attribute naming, metrics tags, and the options system.
$ npx skills add getsentry/sentry --skill backend-conventions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getsentry/sentry backend-conventions --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/backend-conventions .claude/skills/backend-conventions && rm -rf skills-srcUse ~/.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/
Install the "backend-conventions" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/backend-conventions into .claude/skills/backend-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-conventions", 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 install https://github.com/getsentry/sentry/tree/master/.agents/skills/backend-conventionsType 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.
$ npx skills add getsentry/sentry --skill backend-conventions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getsentry/sentry backend-conventions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/backend-conventions .agents/skills/backend-conventions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "backend-conventions" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/backend-conventions into .agents/skills/backend-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-conventions", 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.
$ npx skills add getsentry/sentry --skill backend-conventions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getsentry/sentry backend-conventions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/backend-conventions .cursor/skills/backend-conventions && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "backend-conventions" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/backend-conventions into .cursor/skills/backend-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-conventions", 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 https://github.com/getsentry/sentry.git --path .agents/skills/backend-conventions--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add getsentry/sentry --skill backend-conventions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getsentry/sentry backend-conventions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/backend-conventions .gemini/skills/backend-conventions && rm -rf skills-srcUse ~/.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/
Install the "backend-conventions" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/backend-conventions into .gemini/skills/backend-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-conventions", 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.
$ gh skill install getsentry/sentry backend-conventionsInstalls 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).
$ npx skills add getsentry/sentry --skill backend-conventions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/backend-conventions .github/skills/backend-conventions && rm -rf skills-srcUse ~/.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/
Install the "backend-conventions" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/backend-conventions into .github/skills/backend-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-conventions", 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.
$ npx skills add getsentry/sentry --skill backend-conventions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getsentry/sentry backend-conventions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/backend-conventions .opencode/skills/backend-conventions && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "backend-conventions" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/backend-conventions into .opencode/skills/backend-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-conventions", 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.
backend-conventionsSentry backend conventions for logging, tracing/spans, span/tag attribute naming, metrics tags, and the options system.
Backend Conventions is an agent skill from getsentry/sentry, published by the product's own GitHub organization. Sentry backend conventions for logging, tracing/spans, span/tag attribute naming, metrics tags, and the options system. Use when adding or editing Python in src/ that logs (logger.info/exception), records metrics (metrics.incr/timing with tags), instruments spans/transactions, calls sentrysdk.settag/setattribute or setspantag/setspandata, or reads registered options with options.get(). Trigger on "add logging", "log an error", "add a metric", "add a span", "instrument tracing", "set an attribute", "add a tag"…
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 works with Sentry and Python. The repository describes itself as: Developer-first error tracking and performance monitoring.
Read from SKILL.md and the folder at commit 87d1203. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Backend Conventions loads about 1.3k tokens when it runs. Until then it costs about 155 tokens; SKILL.md has 323 words of instructions outside code blocks.
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.
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.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 323 words (~1,330 tokens).
“Sentry uses a centralized options system where all options are registered in src/sentry/options/defaults.py with required default values.”
Just SKILL.md in .agents/skills/backend-conventions of getsentry/sentry.
Open the folder on GitHubat commit 87d1203
Backend Conventions 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Backend Conventions this skillgetsentry/sentry | 45k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Aivisspeech Engine Sentry TriageAivis-Project/AivisSpeech-Engine | 181 | — | ~545 | Automated safety check: Pass | LGPL-3.0 | |
| Claude Settings Auditgetsentry/skills | 1k | 4 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Sentry Python SDKgetsentry/sentry-for-ai | 268 | — | ~4.1k | Automated safety check: Pass | Apache-2.0 | |
| Sentry Setup AI MonitoringLiorVainer/data-israel | 130 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Secret Serializationgetsentry/skills | 1k | — | ~2.6k | Automated safety check: Notes | Apache-2.0 |
Aivis-Project/AivisSpeech-Engine
AivisSpeech Engine の Sentry issue を調査し、修正すべきエンジン側の不具合と、入力値・ローカル環境・外部サービス由来のノイズを切り分けるためのスキルです。Sentry 側で既知ノイズを永続アーカイブする作業や、voicevoxengine/utility/sentryutility.py と関連テストを更新して既知ノイズを送信前に破棄する作業で使用します。
getsentry/skills
Analyze a repository to generate recommended Claude Code settings.json permissions.
getsentry/sentry-for-ai
Full Sentry SDK setup for Python. An agent skill from getsentry/sentry-for-ai.
LiorVainer/data-israel
Setup Sentry AI Agent Monitoring in any project. An agent skill from LiorVainer/data-israel.
getsentry/skills
Finds secrets, tokens, passwords, and API keys that can leak through generated serialization: Python dataclass repr and asdict, attrs, pydantic modeldump, NamedTuple, JavaScript JSON.stringify and…
Asymmetric-al/core
A skill your agent uses when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions, error tracking with Sentry, payload encryption for sensitive…
getsentry/sentry
Filter large Sentry Scraps design-system migration PRs for review by separating mechanical import-path changes, generated baseline updates, snapshot mocks, and pure renames from substantive…
getsentry/sentry
Instrument and discover analytics events in Sentry's frontend UI.
getsentry/sentry
Guide for creating and maintaining outbox-based eventually consistent operations in Sentry.
getsentry/sentry
Guide for creating, updating, and deprecating hybrid cloud RPC services in Sentry.
getsentry/sentry
Generate hybrid cloud tests for the Sentry codebase. An agent skill from getsentry/sentry.
getsentry/sentry
Fix violations of an eslintPluginScraps rule across the codebase.
Sentry backend conventions for logging, tracing/spans, span/tag attribute naming, metrics tags, and the options system. Backend Conventions is an agent skill from getsentry/sentry, published by the product's own GitHub organization. Sentry backend conventions for logging, tracing/spans, span/tag attribute naming, metrics tags, and the options system.
Backend Conventions fits situations like: editing Python in src/ that logs (logger.info/exception); records metrics (metrics.incr/timing with tags); instruments spans/transactions; calls sentrysdk.settag/setattribute.
Run `npx skills add getsentry/sentry --skill backend-conventions -a claude-code`. Or copy the skill folder (.agents/skills/backend-conventions in getsentry/sentry) into .claude/skills/backend-conventions in your project. Claude Code loads it when a task matches its description.
Run `npx skills add getsentry/sentry --skill backend-conventions -a codex`. Or copy the skill folder (.agents/skills/backend-conventions in getsentry/sentry) into .agents/skills/backend-conventions in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/sentry --skill backend-conventions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/backend-conventions, .gemini/skills/backend-conventions, .github/skills/backend-conventions and .opencode/skills/backend-conventions in your project.
SKILL.md names no scripts, command-line tools or credentials: Backend Conventions is instructions for the agent only. Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Backend Conventions has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Backend Conventions: Aivisspeech Engine Sentry Triage (Aivis-Project/AivisSpeech-Engine, 181 stars), Claude Settings Audit (getsentry/skills, 1k stars), Sentry Python SDK (getsentry/sentry-for-ai, 268 stars) and Sentry Setup AI Monitoring (LiorVainer/data-israel, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
getsentry (a GitHub organization, an official publisher) maintains it in getsentry/sentry, which has 45,495 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 7, 2026.
Source: getsentry/sentry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
