You're adding Sentry instrumentation and can't decide if something should be an error, span, log, or metric. This skill is the decision framework: errors need stack traces and get tracked as Issues, traces show where time went in the request waterfall, logs capture what was true at one decision point, and metrics let you chart trends and alert on rates. It walks through the overlaps (span attribute vs metric, log vs span) with a tiebreaker table, then shows a fully instrumented request handler in Python and TypeScript. Decides what to emit, not how to wire it up. Hand off to the language specific SDK skills for actual implementation once you know which signal you need.
npx -y skills add getsentry/sentry-for-ai --skill sentry-instrumentation-guide --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
supercent-io/skills-template
supercent-io/skills-template
huangjia2019/claude-code-engineering
reactjs/react.dev
reactjs/react.dev