Sentry
Monitor and debug application errors via the Sentry CLI. Use when triaging production errors or managing releases.From its SKILL.md
npx -y skills add fworks-tech/agenthood --skill sentryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 161 tokens by cl100k_base, as published. Nobody here has run it
sentry-cli
Use sentry-cli for Sentry error monitoring.
Common Commands
Issues
- List issues:
sentry-cli issues list --org <org> - Resolve issue:
sentry-cli issues resolve <id> - Ignore issue:
sentry-cli issues ignore <id>
Releases
- Create release:
sentry-cli releases new <version> - Finalize release:
sentry-cli releases finalize <version> - List releases:
sentry-cli releases list
Source Maps
- Upload:
sentry-cli sourcemaps upload ./dist
Notes
- Auth token from https://sentry.io/settings/account/api/auth-tokens/
- Set
SENTRY_AUTH_TOKEN,SENTRY_ORGenv vars
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most log analysis skills give in 161 tokens
Counted across 325 of the 341 authors here whose files we hold, read 2026-09-06
- Use structured JSON loggingin 32 of 325, across 30 files
- Link every alert to a runbookin 15 of 325, across 13 files
- Alert on symptoms, not causesin 11 of 325, across 10 files
- Include correlation IDs in every log linein 10 of 325
- Propagate trace context across service boundariesin 9 of 325, across 8 files
- Include request IDs for correlationin 8 of 325, across 6 files
- Include trace_id in every structured log entryin 8 of 325, across 7 files
- Include request and user context in every log entryin 8 of 325
- Correlate logs and traces with shared trace IDin 7 of 325, across 6 files
- Record exceptions and set span status on errorsin 7 of 325
- Confirm connection is ACTIVE before running workflowsin 6 of 325, across 3 files
- Call RUBE_SEARCH_TOOLS first for current schemasin 6 of 325, across 3 files
Said here and by no other author read
- list Sentry issues with sentry-cli
- resolve issues with sentry-cli issues resolve
- ignore issues with sentry-cli issues ignore
- create releases with sentry-cli releases new
- finalize releases with sentry-cli releases finalize
- upload source maps with sentry-cli sourcemaps upload
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.