Sentry onboarding
Skill addxai/enterprise-harness-engineering/skills/sentry-onboarding
Enterprise-grade AI Agent Skills for software development, DevOps, SRE, security, and product teams. Compatible with Claude Code, Cursor, Windsurf, Gemini CLI, GitHub Copilot, and 30+ AI coding agents.
npx -y skills add addxai/enterprise-harness-engineering --skill sentry-onboardingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Create and configure Sentry projects across staging/production environments via REST API. Use when user needs to onboard a new service to Sentry, create Sentry projects, or set up error monitoring for a new application.
SKILL.md
2.3 KB, as published. Nobody here has run it
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
- Java →
- 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-bootnotjava) - Project slug is auto-generated from name