
Sentry Monitoring
- 60 installs
- 36 repo stars
- Updated July 14, 2026
- oimiragieo/agent-studio
Helps with ai & agent building tasks.
About
sentry-monitoring is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.
- sentry-monitoring
- AI & Agent Building
- AI-coding skill
Sentry Monitoring by the numbers
- 60 all-time installs (skills.sh)
- +1 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #6,460 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/oimiragieo/agent-studio --skill sentry-monitoringAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 60 |
|---|---|
| repo stars | ★ 36 |
| Last updated | July 14, 2026 |
| Repository | oimiragieo/agent-studio ↗ |
What it does
Helps with ai & agent building tasks.
Files
Mode: Cognitive/Prompt-Driven — No standalone utility script; use via agent context.
Sentry Monitoring Skill
Overview
Provides 90%+ context savings vs raw Sentry API calls. Progressive disclosure by feature category: error tracking, performance monitoring, release management, and project configuration.
Requirements
- Sentry account with project configured
SENTRY_AUTH_TOKENenvironment variable (optional, for authenticated API calls)SENTRY_ORGenvironment variable (optional, defaults to first organization)SENTRY_PROJECTenvironment variable (optional, defaults to first project)
Tools (Progressive Disclosure)
Error Tracking
| Tool | Description | Confirmation |
|---|---|---|
| list-issues | List recent issues/errors | No |
| issue-details | Get detailed issue info | No |
| resolve-issue | Mark issue as resolved | Yes |
| ignore-issue | Ignore/snooze issue | Yes |
Performance Monitoring
| Tool | Description | Confirmation |
|---|---|---|
| list-transactions | List performance transactions | No |
| transaction-summary | Get transaction performance stats | No |
| slow-queries | Identify slow database queries | No |
Release Management
| Tool | Description | Confirmation |
|---|---|---|
| list-releases | List releases | No |
| create-release | Create new release | Yes |
| set-commits | Associate commits with release | Yes |
Project Configuration
| Tool | Description | Confirmation |
|---|---|---|
| list-projects | List Sentry projects | No |
| project-settings | View project settings | No |
| list-alerts | List alert rules | No |
Quick Reference
# List recent issues
curl -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \
"https://sentry.io/api/0/projects/$SENTRY_ORG/$SENTRY_PROJECT/issues/?query=is:unresolved"
# Get issue details
curl -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \
"https://sentry.io/api/0/issues/{issue_id}/"
# Resolve issue
curl -X PUT -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \
"https://sentry.io/api/0/issues/{issue_id}/" \
-d '{"status": "resolved"}'
# List transactions
curl -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \
"https://sentry.io/api/0/organizations/$SENTRY_ORG/events/?field=transaction"
# Create release
curl -X POST -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \
"https://sentry.io/api/0/organizations/$SENTRY_ORG/releases/" \
-d '{"version": "1.0.0", "projects": ["project-slug"]}'
# List projects
curl -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \
"https://sentry.io/api/0/organizations/$SENTRY_ORG/projects/"Configuration
Environment Variables
| Variable | Required | Description |
|---|---|---|
SENTRY_AUTH_TOKEN | Optional | Sentry authentication token for API calls |
SENTRY_ORG | Optional | Organization slug (defaults to first org) |
SENTRY_PROJECT | Optional | Project slug (defaults to first project) |
SENTRY_DSN | No | For SDK integration (not used by this skill) |
Getting Auth Token
1. Navigate to Sentry Settings → Account → API → Auth Tokens 2. Create new token with scopes: project:read, project:write, event:read 3. Set as environment variable: export SENTRY_AUTH_TOKEN=your_token_here
Security
⚠️ Never expose auth tokens in output ⚠️ Destructive operations (resolve-issue, ignore-issue, create-release, set-commits) require confirmation ⚠️ Use environment variables for credentials, never hardcode
Agent Integration
- devops (primary): Production monitoring, incident response
- incident-responder (primary): Error triage, issue resolution
- developer (secondary): Debugging, performance optimization
- qa (secondary): Test environment monitoring
Error Handling
If tool execution fails:
1. Verify SENTRY_AUTH_TOKEN is set: echo $SENTRY_AUTH_TOKEN 2. Check token permissions include required scopes 3. Verify organization and project slugs are correct 4. Review Sentry API rate limits (default: 3000 requests/minute)
Common Workflows
Incident Response
1. list-issues - Get recent unresolved errors 2. issue-details - Investigate specific issue 3. resolve-issue - Mark as resolved after fix deployed
Performance Optimization
1. list-transactions - Identify slow endpoints 2. transaction-summary - Analyze performance patterns 3. slow-queries - Find database bottlenecks
Release Management
1. create-release - Create new release version 2. set-commits - Associate commits with release 3. list-releases - Track release health
Troubleshooting
| Issue | Solution |
|---|---|
| 401 Unauthorized | Check SENTRY_AUTH_TOKEN is valid and not expired |
| 403 Forbidden | Verify token has required scopes (project:read, project:write, event:read) |
| 404 Not Found | Verify SENTRY_ORG and SENTRY_PROJECT are correct slugs |
| Rate limit exceeded | Wait 1 minute, reduce request frequency |
Related
- Sentry API Documentation: <https://docs.sentry.io/api/>
- Sentry Error Tracking: <https://docs.sentry.io/product/issues/>
- Sentry Performance: <https://docs.sentry.io/product/performance/>
- Sentry Releases: <https://docs.sentry.io/product/releases/>
Memory Protocol (MANDATORY)
Before starting: Read .claude/context/memory/learnings.md
After completing:
- New pattern ->
.claude/context/memory/learnings.md - Issue found ->
.claude/context/memory/issues.md - Decision made ->
.claude/context/memory/decisions.md
ASSUME INTERRUPTION: If it's not in memory, it didn't happen.
OpenTelemetry + Grafana Stack
Auto-instrument with OTel, export to Sentry + Grafana simultaneously:
import { NodeSDK } from '@opentelemetry/sdk-node';
import { SentrySpanProcessor } from '@sentry/opentelemetry';
const sdk = new NodeSDK({ spanProcessor: new SentrySpanProcessor() });
sdk.start();Continuous Profiling (Pyroscope)
# pyroscope.configure({ applicationName: 'api', serverAddress: 'http://pyroscope:4040' })Grafana + Prometheus
services:
prometheus: { image: prom/prometheus }
grafana: { image: grafana/grafana }
otel-collector: { image: otel/opentelemetry-collector-contrib }Invoke the sentry-monitoring skill and follow it exactly as presented to you
#!/usr/bin/env node
/**
* sentry-monitoring - Post-Execute Hook
* Runs after the skill executes for cleanup, logging, or follow-up actions.
*/
const fs = require('fs');
const path = require('path');
const { safeParseJSON } = require('../../../lib/utils/safe-json.cjs');
// Parse hook input
const result = safeParseJSON(process.argv[2] || '{}');
console.log('📝 [SENTRY-MONITORING] Post-execute processing...');
/**
* Process execution result
*/
function processResult(_result) {
// TODO: Add your post-processing logic here
return { success: true };
}
// Run post-processing
const outcome = processResult(result);
if (outcome.success) {
console.log('✅ [SENTRY-MONITORING] Post-processing complete');
process.exit(0);
} else {
console.error('⚠️ [SENTRY-MONITORING] Post-processing had issues');
process.exit(0);
}
#!/usr/bin/env node
/**
* sentry-monitoring - Pre-Execute Hook
* Runs before the skill executes to validate input or prepare context.
*/
const fs = require('fs');
const path = require('path');
const { safeParseJSON } = require('../../../lib/utils/safe-json.cjs');
// Parse hook input
const input = safeParseJSON(process.argv[2] || '{}');
console.log('🔍 [SENTRY-MONITORING] Pre-execute validation...');
/**
* Validate input before execution
*/
function validateInput(_input) {
const errors = [];
// TODO: Add your validation logic here
return errors;
}
// Run validation
const errors = validateInput(input);
if (errors.length > 0) {
console.error('❌ Validation failed:');
errors.forEach(e => console.error(' - ' + e));
process.exit(1);
}
console.log('✅ [SENTRY-MONITORING] Validation passed');
process.exit(0);
sentry-monitoring Research Requirements
Generated: 2026-02-28
Skill Description
Sentry error tracking and performance monitoring for real-time visibility into application errors, performance issues, and release health
Research Areas
- Current best practices for sentry-monitoring
- Industry standards and tooling
- Integration patterns
Source References
- To be populated by skill-updater research phase
sentry-monitoring Rules
Purpose
Sentry error tracking and performance monitoring for real-time visibility into application errors, performance issues, and release health
Best Practices
- Never expose auth tokens in output
- Require confirmation for destructive operations
- Use environment variables for credentials
Integration Points
See SKILL.md for complete documentation.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "sentry-monitoring Input Schema",
"description": "Input validation schema for sentry-monitoring skill",
"type": "object",
"required": [],
"properties": {},
"additionalProperties": true
}
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "sentry-monitoring Output Schema",
"description": "Output validation schema for sentry-monitoring skill",
"type": "object",
"required": ["success"],
"properties": {
"success": {
"type": "boolean",
"description": "Whether the skill executed successfully"
},
"result": {
"type": "object",
"description": "The skill execution result",
"additionalProperties": true
},
"error": {
"type": "string",
"description": "Error message if execution failed"
}
},
"additionalProperties": true
}
#!/usr/bin/env node
/**
* Sentry Monitoring - Main Script
* Sentry error tracking and performance monitoring for real-time visibility into application errors, performance issues, and release health
*
* Usage:
* node main.cjs [options]
*
* Options:
* --help Show this help message
*/
const fs = require('fs');
const path = require('path');
// Find project root
function findProjectRoot() {
let dir = __dirname;
while (dir !== path.parse(dir).root) {
if (fs.existsSync(path.join(dir, '.claude'))) {
return dir;
}
dir = path.dirname(dir);
}
return process.cwd();
}
const PROJECT_ROOT = findProjectRoot();
// Parse command line arguments
const args = process.argv.slice(2);
const options = {};
for (let i = 0; i < args.length; i++) {
if (args[i].startsWith('--')) {
const key = args[i].slice(2);
const value = args[i + 1] && !args[i + 1].startsWith('--') ? args[++i] : true;
options[key] = value;
}
}
/**
* Main execution
*/
function main() {
if (options.help) {
console.log(`
Sentry Monitoring - Main Script
Usage:
node main.cjs [options]
Options:
--help Show this help message
`);
process.exit(0);
}
console.log(
'Sentry Monitoring skill provides in-context guidance; configure Sentry MCP/API for full functionality. Invoke via the agent; no standalone script.'
);
process.exit(0);
}
main();
sentry-monitoring Implementation Template
Goal
- Define target outcome and acceptance criteria.
TDD
1. Red 2. Green 3. Refactor
Verification
- lint
- format
- targeted tests