Sentry onboarding

Skill addxai/enterprise-harness-engineering/skills/sentry-onboarding

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.From its SKILL.md

Install

npx -y skills add addxai/enterprise-harness-engineering --skill sentry-onboarding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

reads credentialsReads from 2 credential sources: `SENTRY_STAGING_TOKEN` and 1 more.
runs commandsInstructs the agent to run 4 commands, including `curl -s -H "Authorization: Bearer $TOKEN" "$SENTRY_URL/api/0/organizations/$ORG/teams/" | jq '.[].slug'` and 3 more.
fetches URLsInstructs the agent to fetch 3 URLs, including $SENTRY_URL/api/0/organizations/$ORG/teams/ and 2 more.

SKILL.md

2.3 KB, 572 tokens by cl100k_base, 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
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

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 572 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

collect service name, platform, team, and environments
verify the token before proceeding
list available teams before creating the project
create the project in each requested environment
extract the public DSN after creation
generate an SDK snippet containing the DSN

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.