Error Handler
EliasOulkadi/shokunin
Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead…
Review code for correct logging and error handling patterns.
Install Logging Observability
$ npx skills add getsentry/toolkit --skill logging-observability -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getsentry/toolkit logging-observability --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/toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/logging-observability .claude/skills/logging-observability && 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 "logging-observability" agent skill from https://github.com/getsentry/toolkit/tree/main/.agents/skills/logging-observability into .claude/skills/logging-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-observability", 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/toolkit/tree/main/.agents/skills/logging-observabilityType 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/toolkit --skill logging-observability -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getsentry/toolkit logging-observability --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/logging-observability .agents/skills/logging-observability && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "logging-observability" agent skill from https://github.com/getsentry/toolkit/tree/main/.agents/skills/logging-observability into .agents/skills/logging-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-observability", 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/toolkit --skill logging-observability -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getsentry/toolkit logging-observability --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/logging-observability .cursor/skills/logging-observability && 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 "logging-observability" agent skill from https://github.com/getsentry/toolkit/tree/main/.agents/skills/logging-observability into .cursor/skills/logging-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-observability", 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/toolkit.git --path .agents/skills/logging-observability--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/toolkit --skill logging-observability -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getsentry/toolkit logging-observability --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/logging-observability .gemini/skills/logging-observability && 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 "logging-observability" agent skill from https://github.com/getsentry/toolkit/tree/main/.agents/skills/logging-observability into .gemini/skills/logging-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-observability", 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/toolkit logging-observabilityInstalls 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/toolkit --skill logging-observability -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getsentry/toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/logging-observability .github/skills/logging-observability && 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 "logging-observability" agent skill from https://github.com/getsentry/toolkit/tree/main/.agents/skills/logging-observability into .github/skills/logging-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-observability", 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/toolkit --skill logging-observability -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/toolkit logging-observability --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/logging-observability .opencode/skills/logging-observability && 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 "logging-observability" agent skill from https://github.com/getsentry/toolkit/tree/main/.agents/skills/logging-observability into .opencode/skills/logging-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-observability", 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
logging-observability- GitHub stars
- 917
- Token cost
- ~2.6k tokens
- SKILL.md length
- 697 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Review code for correct logging and error handling patterns.
- Works in 6 steps: Logging 4xx Errors with logIssue() → Missing logIssue() for 5xx Errors → Using Raw console.log/warn/error → …
- Reviewing code that handles errors
- SKILL.md covers Error Hierarchy, Logging Functions…, Anti-Patterns to Catch and Correct Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Logging Observability is an agent skill from getsentry/toolkit, published by the product's own GitHub organization. Review code for correct logging and error handling patterns. Use when reviewing code that handles errors, uses logging functions, or captures exceptions. Enforces the error hierarchy where 4xx errors are never logged to Sentry and 5xx errors always are. Trigger phrases include "review logging", "check error handling", "audit observability", or verify correct use of logIssue vs logError.
Its SKILL.md is about 2.6k 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 DevOps & Cloud, covering Observability, Error handling and Code review. It works with Sentry and Model Context Protocol. The repository describes itself as: Agentic tooling for Sentry.
When your agent uses it
- Reviewing code that handles errors
- Uses logging functions
- Captures exceptions
- Phrases include review logging
Example prompts
- “review logging”
- “check error handling”
- “audit observability”
- “/logging-observability”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Logging 4xx Errors with logIssue()
- Missing logIssue() for 5xx Errors
- Using Raw console.log/warn/error
- Catching All Errors Indiscriminately
- Missing Structured Context
- Using captureException() Directly
What it can do on your machine
Read from SKILL.md and the folder at commit 626f869. 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 (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Logging Observability loads about 2.6k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 697 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.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 697 words (~2,631 tokens).
“Enforce correct logging and error handling patterns in the sentry-mcp codebase. The core principle: 4xx errors (user-correctable) must NEVER create Sentry issues. 5xx errors (system failures) must ALWAYS create Sentry issues.”
- name
- logging-observability
Files
Just SKILL.md in .agents/skills/logging-observability of getsentry/toolkit.
Open the folder on GitHubat commit 626f869
Compare with similar skills
Logging Observability 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 |
|---|---|---|---|---|---|---|
| Logging Observability this skillgetsentry/toolkit | 917 | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Error HandlerEliasOulkadi/shokunin | 114 | — | ~3.6k | Automated safety check: Notes | MIT | |
| Sentry v8 Error Trackingdiet103/claude-code-infrastructure-showcase | 10k | 2 repos | ~2.3k | Automated safety check: Notes | MIT | |
| fp-go Logging PatternsIBM/fp-go | 2k | — | ~3.7k | Automated safety check: Pass | Apache-2.0 | |
| Crash Instrumentationnexus-labs-automation/mobile-observability | 116 | — | ~744 | Automated safety check: Pass | MIT | |
| Logging and Error Reporting for Warpwarpdotdev/warp | 65k | 1 repos | ~5.6k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Sentry v8 Error Tracking
diet103/claude-code-infrastructure-showcase
Enforces that every error in a service is captured to Sentry v8, with patterns for controllers, routes, cron jobs and database performance spans instead of console logging alone.
- Official
fp-go Logging Patterns
IBM/fp-go
Adds logging to fp-go functional pipelines with Tap operators, entry and exit logs and error context, so that logging never changes the value or error flowing through.
Crash Instrumentation
nexus-labs-automation/mobile-observability
Set up crash instrumentation with actionable context. An agent skill from nexus-labs-automation/mobile-observability.
Logging and Error Reporting for Warp
warpdotdev/warp
Guides log level choices and when to raise a structured Sentry event instead of a plain log line in the Warp Rust codebase, keeping secrets out of logs.
Golang Error Handling
unxed/f4
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog…
More from getsentry/toolkit
- Official
MCP QA
getsentry/toolkit
QA MCP tool changes with local CLI and real agent clients. An agent skill from getsentry/toolkit.
- Official
MCP Audit
getsentry/toolkit
Audit MCP servers for protocol compliance, metadata drift, and compatibility regressions.
- Official
Testing Guidelines
getsentry/toolkit
Guide for writing tests. An agent skill from getsentry/toolkit.
Related
Works with
Categories
Questions about Logging Observability
What does Logging Observability do?
Review code for correct logging and error handling patterns. Logging Observability is an agent skill from getsentry/toolkit, published by the product's own GitHub organization. Review code for correct logging and error handling patterns.
When should I use Logging Observability?
Logging Observability fits situations like: reviewing code that handles errors; uses logging functions; captures exceptions; phrases include review logging.
How do I install Logging Observability in Claude Code?
Run `npx skills add getsentry/toolkit --skill logging-observability -a claude-code`. Or copy the skill folder (.agents/skills/logging-observability in getsentry/toolkit) into .claude/skills/logging-observability in your project. Claude Code loads it when a task matches its description.
How do I install Logging Observability in Codex?
Run `npx skills add getsentry/toolkit --skill logging-observability -a codex`. Or copy the skill folder (.agents/skills/logging-observability in getsentry/toolkit) into .agents/skills/logging-observability in your project. Codex loads it when a task matches its description.
Can I use Logging Observability 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/toolkit --skill logging-observability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/logging-observability, .gemini/skills/logging-observability, .github/skills/logging-observability and .opencode/skills/logging-observability in your project.
What does Logging Observability need to run?
SKILL.md names no scripts, command-line tools or credentials: Logging Observability is instructions for the agent only.
Does Logging Observability access the network?
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.
Is Logging Observability 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 Logging Observability use?
Logging Observability has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Logging Observability use?
About 2.6k tokens (SKILL.md is roughly 11k 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 Logging Observability?
Skills that share tags, products or a category with Logging Observability: Error Handler (EliasOulkadi/shokunin, 114 stars), Sentry v8 Error Tracking (diet103/claude-code-infrastructure-showcase, 10k stars), fp-go Logging Patterns (IBM/fp-go, 2k stars) and Crash Instrumentation (nexus-labs-automation/mobile-observability, 116 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Logging Observability?
getsentry (a GitHub organization, an official publisher) maintains it in getsentry/toolkit, which has 917 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: getsentry/toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.