Sentry Miniapp SDK
lizhiyao/sentry-miniapp
Full Sentry SDK setup for Mini Programs — error monitoring, tracing, offline cache, source maps.
Configure Sentry across development, staging, and production environments with separate DSNs, environment-specific sample rates, per-environment alert rules, and dashboard filtering.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-multi-env-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-multi-env-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/sentry-multi-env-setup .claude/skills/sentry-multi-env-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sentry-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-multi-env-setup into .claude/skills/sentry-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-multi-env-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-multi-env-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-multi-env-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-multi-env-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/sentry-multi-env-setup .agents/skills/sentry-multi-env-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sentry-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-multi-env-setup into .agents/skills/sentry-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-multi-env-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-multi-env-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-multi-env-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/sentry-multi-env-setup .cursor/skills/sentry-multi-env-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sentry-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-multi-env-setup into .cursor/skills/sentry-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-multi-env-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/sentry-multi-env-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-multi-env-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-multi-env-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/sentry-multi-env-setup .gemini/skills/sentry-multi-env-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sentry-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-multi-env-setup into .gemini/skills/sentry-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-multi-env-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-multi-env-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-multi-env-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/sentry-multi-env-setup .github/skills/sentry-multi-env-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sentry-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-multi-env-setup into .github/skills/sentry-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-multi-env-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-multi-env-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-multi-env-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/sentry-multi-env-setup .opencode/skills/sentry-multi-env-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sentry-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-multi-env-setup into .opencode/skills/sentry-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-multi-env-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
sentry-multi-env-setupConfigure Sentry across development, staging, and production environments with separate DSNs, environment-specific sample rates, per-environment alert rules, and dashboard filtering.
Sentry Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Sentry across development, staging, and production environments with separate DSNs, environment-specific sample rates, per-environment alert rules, and dashboard filtering. Use when setting up Sentry for dev/staging/production, managing environment-specific configurations, isolating data between environments, or configuring .env files for per-environment DSNs. Trigger: "sentry environments", "sentry staging setup", "multi-environment sentry", "sentry dev vs prod", "sentry DSN per env".
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/environment-configuration.md`, `references/errors.md` and `references/examples.md`). Compatibility notes: Designed for Claude Code
It sits in DevOps & Cloud, covering Monitoring and alerting. It works with Sentry. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGrepGlobBash(npm:*)Bash(npx:*)Bash(node:*)Bash(sentry-cli:*)From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitnpmpipFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
o0.ingest.sentry.ioAlso links to:
docs.sentry.iosentry.ioFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
SENTRY_AUTH_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Sentry Multi Env Setup loads about 4.1k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 131 tokens; SKILL.md has 687 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
or configuring .env files for per-environment DSNs.- `.env` file management tooling (dotenv, direnv, or platform-native env config)**Set up `.env` files per environment:**# .env.development# .env.staging# .env.production- **Per-environment `.env` files** with isolated DSNs pointing to separate Sentry projectst project; use `dotenv` with `--env-file .env.production` |Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 687 words, ~4,072 tokens.
.claude/skills/sentry-multi-env-setup/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Configure Sentry to run across development, staging, and production with isolated DSNs, tuned sample rates, environment-aware alert routing, and dashboard filtering. Covers @sentry/node v8+ (TypeScript) and sentry-sdk v2+ (Python), targeting sentry.io or self-hosted Sentry 24.1+. The goal is to capture everything in dev, validate in staging, and protect production with tight sampling and PII scrubbing.
@sentry/node v8+ installed (npm install @sentry/node) or sentry-sdk v2+ (pip install sentry-sdk)development, staging, production).env file management tooling (dotenv, direnv, or platform-native env config)Each environment gets its own DSN pointing to a dedicated Sentry project. This prevents dev noise from inflating production quotas and allows independent rate limits per environment.
Set up .env files per environment:
# .env.development
SENTRY_DSN=https://dev-key@o0.ingest.sentry.io/111
SENTRY_ENVIRONMENT=development
SENTRY_RELEASE=local-dev
# .env.staging
SENTRY_DSN=https://staging-key@o0.ingest.sentry.io/222
SENTRY_ENVIRONMENT=staging
# .env.production
SENTRY_DSN=https://prod-key@o0.ingest.sentry.io/333
SENTRY_ENVIRONMENT=productionTypeScript — environment-aware init with typed config:
// config/sentry.ts
import * as Sentry from '@sentry/node';
type Environment = 'development' | 'staging' | 'production';
interface EnvSentryConfig {
tracesSampleRate: number;
sampleRate: number;
debug: boolean;
sendDefaultPii: boolean;
maxBreadcrumbs: number;
enabled: boolean;
}
const ENV_CONFIG: Record<Environment, EnvSentryConfig> = {
development: {
tracesSampleRate: 1.0, // Capture every transaction for local debugging
sampleRate: 1.0, // Every error
debug: true, // Verbose console output for SDK troubleshooting
sendDefaultPii: true, // Include PII for local debugging only
maxBreadcrumbs: 100, // Full breadcrumb trail
enabled: true, // Set to false to fully disable in dev
},
staging: {
tracesSampleRate: 0.5, // 50% of transactions — enough to catch regressions
sampleRate: 1.0, // All errors — staging validates error handling
debug: false,
sendDefaultPii: false, // Staging mirrors prod PII policy
maxBreadcrumbs: 50,
enabled: true,
},
production: {
tracesSampleRate: 0.1, // 10% — balances visibility with quota budget
sampleRate: 1.0, // All errors — never drop production errors
debug: false,
sendDefaultPii: false, // Never send PII in production
maxBreadcrumbs: 50,
enabled: true,
},
};
export function initSentry(env?: Environment): void {
const environment = env
|| (process.env.SENTRY_ENVIRONMENT as Environment)
|| (process.env.NODE_ENV as Environment)
|| 'development';
const config = ENV_CONFIG[environment] || ENV_CONFIG.development;
Sentry.init({
dsn: process.env.SENTRY_DSN,
environment,
release: process.env.SENTRY_RELEASE || `app@${process.env.npm_package_version || 'unknown'}`,
...config,
// Environment-specific event filtering
beforeSend(event) {
// Dev: capture everything for debugging
if (environment === 'development') return event;
// Staging: drop debug-level events to reduce noise
if (environment === 'staging' && event.level === 'debug') return null;
// Production: aggressive filtering
if (environment === 'production') {
// Drop known non-actionable browser errors
if (event.exception?.values?.some(e =>
e.value?.match(/ResizeObserver|Loading chunk|AbortError/)
)) return null;
// Scrub sensitive headers
if (event.request?.headers) {
delete event.request.headers['Authorization'];
delete event.request.headers['Cookie'];
delete event.request.headers['X-API-Key'];
}
}
return event;
},
});
}Python — equivalent multi-environment init:
# config/sentry_config.py
import os
import sentry_sdk
ENV_CONFIG = {
"development": {
"traces_sample_rate": 1.0,
"sample_rate": 1.0,
"debug": True,
"send_default_pii": True,
"max_breadcrumbs": 100,
},
"staging": {
"traces_sample_rate": 0.5,
"sample_rate": 1.0,
"debug": False,
"send_default_pii": False,
"max_breadcrumbs": 50,
},
"production": {
"traces_sample_rate": 0.1,
"sample_rate": 1.0,
"debug": False,
"send_default_pii": False,
"max_breadcrumbs": 50,
},
}
def init_sentry() -> None:
environment = os.environ.get(
"SENTRY_ENVIRONMENT",
os.environ.get("PYTHON_ENV", "development"),
)
config = ENV_CONFIG.get(environment, ENV_CONFIG["development"])
def before_send(event, hint):
if environment == "production":
exc_info = hint.get("exc_info")
if exc_info:
exc_type = exc_info[0]
# Drop expected exceptions in production
if exc_type in (KeyboardInterrupt, SystemExit):
return None
# Scrub PII from headers
request = event.get("request", {})
headers = request.get("headers", {})
for key in ("Authorization", "Cookie", "X-API-Key"):
headers.pop(key, None)
return event
sentry_sdk.init(
dsn=os.environ.get("SENTRY_DSN", ""),
environment=environment,
release=os.environ.get("SENTRY_RELEASE", "unknown"),
before_send=before_send,
**config,
)Alert routing prevents dev noise from waking on-call engineers. Each environment gets alert rules matching its severity tier.
Production alert rules (Sentry dashboard > Alerts > Create Rule):
| Alert Type | Condition | Filter | Action |
|---|---|---|---|
| Issue alert | New issue | environment:production | PagerDuty on-call |
| Metric alert | Error rate > 50/min for 5 min | environment:production | Slack #alerts-critical |
| Metric alert | P95 latency > 2s for 10 min | environment:production | Slack #alerts-performance |
Staging alert rules:
| Alert Type | Condition | Filter | Action |
|---|---|---|---|
| Issue alert | New issue (first seen) | environment:staging | Slack #alerts-staging |
| Metric alert | Error rate > 100/min for 5 min | environment:staging | Slack #alerts-staging |
Development: No alerts configured. Developers check the dashboard manually or use debug: true for console output.
Add environment context tags for richer filtering:
// Add to Sentry.init() for dashboard filtering
Sentry.init({
// ...base config from Step 1
initialScope: {
tags: {
environment: process.env.SENTRY_ENVIRONMENT || process.env.NODE_ENV,
region: process.env.AWS_REGION || process.env.GCP_REGION || 'us-east-1',
service: process.env.SERVICE_NAME || 'app',
deployment: process.env.DEPLOYMENT_ID || 'unknown',
},
},
});
// Dashboard filter queries:
// Issues > environment:production is:unresolved
// Performance > environment:staging service:api-gateway
// Discover > environment:production region:us-east-1Disable Sentry in test and CI environments:
// test/setup.ts — prevent test runs from sending events
const isTestEnv = process.env.NODE_ENV === 'test' || process.env.CI === 'true';
if (!isTestEnv) {
initSentry();
} else {
// Initialize with empty DSN — SDK loads but sends nothing
// All Sentry.captureException() calls become safe no-ops
Sentry.init({ dsn: '' });
}Tag Sentry releases with the deploy target so the Releases dashboard shows which commit is running where. Each sentry-cli releases deploys call records a deployment event on the timeline.
#!/usr/bin/env bash
# scripts/sentry-release.sh — call from CI after deploy
set -euo pipefail
VERSION="${SENTRY_RELEASE:-$(git rev-parse --short HEAD)}"
ENVIRONMENT="${1:?Usage: sentry-release.sh <environment>}"
ORG="${SENTRY_ORG:-my-org}"
PROJECT="${SENTRY_PROJECT:-my-app}"
echo "Creating Sentry release ${VERSION} for ${ENVIRONMENT}..."
# Create release and associate commits
sentry-cli releases --org "$ORG" --project "$PROJECT" new "$VERSION"
sentry-cli releases --org "$ORG" --project "$PROJECT" set-commits "$VERSION" --auto
# Upload source maps (if applicable)
if [ -d "./dist" ]; then
sentry-cli sourcemaps --org "$ORG" --project "$PROJECT" \
upload --release="$VERSION" ./dist
fi
# Finalize and record deployment
sentry-cli releases --org "$ORG" --project "$PROJECT" finalize "$VERSION"
sentry-cli releases --org "$ORG" --project "$PROJECT" \
deploys "$VERSION" new --env "$ENVIRONMENT"
echo "Release ${VERSION} deployed to ${ENVIRONMENT}"
# Usage in CI:
# ./scripts/sentry-release.sh staging # after staging deploy
# ./scripts/sentry-release.sh production # after production deployGitHub Actions integration:
# .github/workflows/deploy.yml (snippet)
- name: Create Sentry release
env:
SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
SENTRY_ORG: my-org
SENTRY_PROJECT: my-app
run: |
npm install -g @sentry/cli
./scripts/sentry-release.sh ${{ github.event.inputs.environment || 'staging' }}After completing all three steps you will have:
.env files with isolated DSNs pointing to separate Sentry projectsconfig/sentry.ts or config/sentry_config.py) that reads SENTRY_ENVIRONMENT and applies the correct sample rates, PII policy, and filteringenvironment, region, service) for scoped queries| Error | Cause | Solution |
|---|---|---|
| Dev events appearing in production dashboard | Wrong DSN loaded at runtime | Verify SENTRY_DSN points to the correct project; use dotenv with --env-file .env.production |
environment: undefined in Sentry events | SENTRY_ENVIRONMENT and NODE_ENV both unset | Set SENTRY_ENVIRONMENT explicitly in deployment config |
| Staging alerts routing to PagerDuty | Alert rule missing environment filter | Add environment:production condition to PagerDuty alert rules |
| Quota exhausted by dev/staging events | All environments share one Sentry project | Use separate projects per environment for independent quotas |
| Source maps not resolving in staging | Release version mismatch | Ensure SENTRY_RELEASE matches between Sentry.init() and sentry-cli upload |
beforeSend dropping wanted events | Filter regex too broad | Test filters in staging first; log dropped events with console.warn during rollout |
Python sentry_sdk.init() silently fails | DSN env var empty string | Check os.environ.get("SENTRY_DSN") is set; empty string disables the SDK |
TypeScript — Express app with multi-environment Sentry:
// app.ts
import express from 'express';
import * as Sentry from '@sentry/node';
import { initSentry } from './config/sentry';
// Initialize before any other imports that need instrumentation
initSentry();
const app = express();
// Sentry request handler — must be first middleware
Sentry.setupExpressErrorHandler(app);
app.get('/health', (_req, res) => res.json({ status: 'ok' }));
app.get('/api/data', async (_req, res) => {
const span = Sentry.startSpan({ name: 'fetch-data', op: 'db.query' }, () => {
// Your database call here
return { items: [] };
});
res.json(span);
});
// Error handler — Sentry captures unhandled errors automatically
app.use((err: Error, _req: express.Request, res: express.Response, _next: express.NextFunction) => {
Sentry.captureException(err);
res.status(500).json({ error: 'Internal server error' });
});
app.listen(3000, () => {
console.log(`Server running in ${process.env.SENTRY_ENVIRONMENT || process.env.NODE_ENV} mode`);
});Python — FastAPI with multi-environment Sentry:
# main.py
import os
from fastapi import FastAPI, Request
from fastapi.responses import JSONResponse
import sentry_sdk
from config.sentry_config import init_sentry
# Initialize before app creation
init_sentry()
app = FastAPI()
@app.get("/health")
async def health():
return {"status": "ok"}
@app.get("/api/data")
async def get_data():
with sentry_sdk.start_span(op="db.query", name="fetch-data"):
# Your database call here
return {"items": []}
@app.exception_handler(Exception)
async def global_exception_handler(request: Request, exc: Exception):
sentry_sdk.capture_exception(exc)
return JSONResponse(status_code=500, content={"error": "Internal server error"})
if __name__ == "__main__":
import uvicorn
env = os.environ.get("SENTRY_ENVIRONMENT", "development")
print(f"Server running in {env} mode")
uvicorn.run(app, host="0.0.0.0", port=8000)beforeSend, ignoreErrors, deny listssentry_sdk.init() options referencetracesSampleRate with tracesSampler for route-level control (see sentry-performance-tuning skill)sentry-cli releases deployssentry-cost-tuning skill)tracePropagationTargets (see sentry-reference-architecture skill)© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in skills/.curated/sentry-multi-env-setup of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit 80f86df
Sentry Multi Env Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sentry Multi Env Setup this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~4.1k | Automated safety check: Notes | MIT | |
| Sentry Miniapp SDKlizhiyao/sentry-miniapp | 687 | — | ~5.1k | Automated safety check: Pass | MIT | |
| Superset Incident Triagesuperset-sh/superset | 15k | — | ~1k | Automated safety check: Pass | Custom licence | |
| Sentry Alert TunerLeoYeAI/openclaw-master-skills | 2.2k | — | ~7.3k | Automated safety check: Pass | MIT | |
| Mz Release SignoffMaterializeInc/materialize | 6.4k | — | ~7.2k | Automated safety check: Pass | Custom licence | |
| Axiom Alerting Managementopenclaw/clawhub | 9.5k | — | ~2.1k | Automated safety check: Pass | MIT |
lizhiyao/sentry-miniapp
Full Sentry SDK setup for Mini Programs — error monitoring, tracing, offline cache, source maps.
superset-sh/superset
Does a read-only first pass on a possible production incident: gathers deploy, Sentry and health-check signals, proposes a severity and status message, then stops for human approval.
LeoYeAI/openclaw-master-skills
Reduce Sentry alert fatigue by surgically tuning issue grouping, fingerprint rules, severity mapping, sample rates, before-send filters, sourcemap pipelines, and release-health gates.
MaterializeInc/materialize
Verify a release candidate on the Grafana dashboards and sign off in release.
openclaw/clawhub
Creates and manages Axiom monitors and notifiers end to end through the v2 API, with scripts for each CRUD operation and a recommended create-validate-tune workflow.
kubesphere/kubesphere
Deploys KubeEye on KubeSphere and writes InspectRule and InspectPlan resources to inspect cluster health, then retrieves the inspection reports.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Works with
Categories
Configure Sentry across development, staging, and production environments with separate DSNs, environment-specific sample rates, per-environment alert rules, and dashboard filtering. Sentry Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Sentry across development, staging, and production environments with separate DSNs, environment-specific sample rates, per-environment alert rules, and dashboard filtering.
Sentry Multi Env Setup fits situations like: setting up Sentry for dev/staging/production; managing environment-specific configurations; isolating data between environments; configuring .env files for per-environment DSNs.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-multi-env-setup -a claude-code`. Or copy the skill folder (skills/.curated/sentry-multi-env-setup in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/sentry-multi-env-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-multi-env-setup -a codex`. Or copy the skill folder (skills/.curated/sentry-multi-env-setup in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/sentry-multi-env-setup in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-multi-env-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry-multi-env-setup, .gemini/skills/sentry-multi-env-setup, .github/skills/sentry-multi-env-setup and .opencode/skills/sentry-multi-env-setup in your project.
Going by SKILL.md and its folder, Sentry Multi Env Setup needs the command-line tools its instructions call (git, npm and pip) and credentials named SENTRY_AUTH_TOKEN. Our summary lists: Python 3; Node.js; A credential in SENTRY_AUTH_TOKEN. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(npm:*), Bash(npx:*), Bash(node:*), Bash(sentry-cli:*). Compatibility (from SKILL.md): Designed for Claude Code.
SKILL.md names 3 domains. In commands or code: o0.ingest.sentry.io; the agent is likely to contact it when it follows the instructions. As links in the text: docs.sentry.io and sentry.io. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Sentry Multi Env Setup is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 677 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Sentry Multi Env Setup: Sentry Miniapp SDK (lizhiyao/sentry-miniapp, 687 stars), Superset Incident Triage (superset-sh/superset, 15k stars), Sentry Alert Tuner (LeoYeAI/openclaw-master-skills, 2.2k stars) and Mz Release Signoff (MaterializeInc/materialize, 6.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.