Skill

sentry-onboarding

Creates and configures Sentry projects across staging/production environments via REST API. Extracts DSNs and generates SDK snippets for onboarding services to error monitoring.

Sentry

monitoring

npx claudepluginhub addxai/enterprise-harness-engineering --plugin enterprise-harness-engineering

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Create and configure Sentry projects across multiple environments via REST API.

SKILL.md

Similar Skills

sentry-multi-env-setup

1.9k

Configures Sentry for dev, staging, and prod with separate DSNs, env-specific sample rates, per-env alerts, and dashboard filtering. For @sentry/node (TS) and sentry-sdk (Python).

4 files9 tools

sentry-pack

sentry-python-sdk

Sets up full Sentry SDK for Python apps including error monitoring, tracing, profiling, logging, metrics, crons, and AI monitoring. Supports Django, Flask, FastAPI, Celery, Starlette, AIOHTTP, Tornado.

7 files

getsentry-sentry-agent-skills-1

configure-sentry

Checks and configures Sentry error tracking SDKs for frontend, Next.js, Node.js, and Python projects including DSN env vars, source maps, and CI/CD release tracking.

1 file10 tools

configure-plugin

Stats

Stars18

Forks5

Last CommitApr 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Sentry Onboarding

Create and configure Sentry projects across multiple environments via REST API.

Setup

Before using this skill, configure your Sentry instances:

# Add your Sentry instances here
SENTRY_INSTANCES:
  - name: staging
    url: https://sentry-staging.example.com
    token_env: SENTRY_STAGING_TOKEN
    org: your-org
  - name: prod
    url: https://sentry.example.com
    token_env: SENTRY_PROD_TOKEN
    org: your-org

Workflow

Step 1: Collect Information

Ask the user for:

Service name (e.g., payment-service)
Platform — must be framework-level, not language-level:
- Java → java-spring-boot
- Python → python-django / python-fastapi
- JavaScript → javascript-nextjs / javascript-react
- Go → go
- Android → android
- iOS → apple-ios
Team — which team should own this project
Environments — which instances to create in (staging, prod, or both)

Step 2: Verify Token

curl -s -H "Authorization: Bearer $TOKEN" "$SENTRY_URL/api/0/organizations/$ORG/teams/" | jq '.[].slug'

If 401 → token expired, guide user to regenerate.

Step 3: List Available Teams

curl -s -H "Authorization: Bearer $TOKEN" "$SENTRY_URL/api/0/organizations/$ORG/teams/" | jq '.[] | {slug, name}'

Step 4: Create Project

curl -s -X POST \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "<service-name>", "platform": "<platform>"}' \
  "$SENTRY_URL/api/0/teams/$ORG/<team-slug>/projects/"

Step 5: Extract DSN

curl -s -H "Authorization: Bearer $TOKEN" \
  "$SENTRY_URL/api/0/projects/$ORG/<project-slug>/keys/" | jq '.[0].dsn.public'

Step 6: Generate SDK Snippet

Based on platform, generate the SDK initialization code with the DSN.

Rules

Production operations require explicit user confirmation
Create staging first, verify, then create prod
Platform must be framework-level (e.g., java-spring-boot not java)
Project slug is auto-generated from name