agentleFS
Sign inStart free
addxaiaddxai/enterprise-harness-engineering/skills/sentry/SKILL.md

sentry

Skill44 starsChanged 7 months agoApache-2.0View on GitHub

Query Sentry errors, triage issues, and check release health via REST API. Use when debugging exceptions, investigating crash reports, triaging error issues, checking release stability, or any error monitoring and issue tracking task. Also triggers on mentions of Sentry, errors, exceptions, crashes, stack traces, or error rates.

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ghidra, datadog and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mitsuhikoSkill

    ghidra

    Reverse engineer binaries using Ghidra's headless analyzer. Decompile executables, extract functions, strings, symbols, and analyze call graphs without GUI.

    Also in 3 projects that use this

  • SentrySkill

    datadog

    Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.

    Also in 4 projects that use this

  • xfstudioSkill

    firebase

    Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. I

    Also in 3 projects that use this

  • mitsuhikoSkill

    openscad

    Create and render OpenSCAD 3D models. Generate preview images from multiple angles, extract customizable parameters, validate syntax, and export STL files for 3D printing platforms like MakerWorld.

    Also in 3 projects that use this

  • digitalocean-labsSkill

    postgres

    Configure DigitalOcean Managed Postgres with bindable variables or schema isolation. Use when setting up databases, creating users, managing permissions, configuring multi-tenant schemas, or troubleshooting database connectivity on App Platform.

    Also in 3 projects that use this

  • SentrySkill

    vercel

    Deploy and inspect Vercel apps, assign aliases, delete deployments, investigate logs, and monitor deployment outcomes. Use for Vercel deployment and log requests, not GitHub code changes or other cloud providers.

    Also in 3 projects that use this

  • +2 more from mitsuhiko

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look before you act: Write operations (resolve / ignore / assign) must be preceded by reviewing the stack trace and impact scope

    line 67

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

sentry

Query errors, investigate exceptions, track issues, and monitor release health via the Sentry REST API. API usage is referenced through Context7 MCP; only company-specific rules are documented here.

Description

Applicable scenarios: production error investigation, issue triage, release health checks, crash analysis.

  • Internal URL: https://sentry-us.example.com (self-hosted Sentry, API base path /api/0/)
  • Organization slug: sentry
VariableDescriptionRequired
SENTRY_AUTH_TOKENOrganization Token (Settings -> Organization Tokens -> Create)Yes

Authentication: -H "Authorization: Bearer $SENTRY_AUTH_TOKEN"

The current Organization Token only has Release-related permissions by default. To query Issues/Events, create an Internal Integration in Developer Settings and enable Issue & Event: Read, Project: Read, Organization: Read.

Rules

Project Structure (7 projects)

Project slugProductPlatformDescription
app-androidMain AppAndroidPrimary consumer app (most frequent releases)
app-iosMain AppiOSPrimary consumer app
backend-serviceBackendJavaBackend service (shares releases with consumer-service)
consumer-serviceBackendJavaBackend consumer service
app2-androidSub-brand AppAndroidSub-brand app
app2-iosSub-brand AppiOSSub-brand app
app3-iosSecurity AppiOSSecurity app

Release Version Naming Convention

Three formats, distinguished by platform:

PlatformFormatExample
Android{major}.{minor}.{patch}({commit_hash})2.85.0(b4f16c)
iOS{bundle_id}@{version}+{build_number}com.example.app@3.91.0+30713
Backend{YYYYMMDD}@{COMMIT_HASH}20260212@3A5AE26

iOS Bundle ID Reference:

Bundle IDProduct
com.example.appMain App
com.example.guardGuard App
com.example.app2Sub-brand App
com.example.app3Security App

Release Frequency

  • app-android: Multiple builds per day (CI auto-reports)
  • app-ios: Several times per week
  • backend-service / consumer-service: Approximately daily deployments, version numbers include date (YYYYMMDD@HASH), both projects share the same release
  • app2-*: Lower frequency

Hard Rules

  1. Look before you act: Write operations (resolve / ignore / assign) must be preceded by reviewing the stack trace and impact scope
  2. PII protection: Error context may contain user data; never share raw stack traces externally or expose user information

Common Workflows

  1. Investigate production errors: Query unresolved issues for a project -> sort by time -> view latest event stack trace -> locate code line -> provide fix suggestions
  2. Post-deployment health check: Query latest release -> check for new issues -> confirm Crash Free Rate -> continue monitoring for 30min
  3. Batch triage: Filter by project + environment -> review stack traces one by one -> resolve / ignore / assign
  4. Release tracking: /api/0/organizations/sentry/releases/?per_page=20&sort=date -> check latest releases

Examples

Bad

# Resolving without investigation
User: Help me handle the errors on Sentry
AI: I've resolved all unresolved issues for you.  <- Did not review stack traces and impact scope

# PII leakage
AI: The stack trace shows user email user@example.com triggered the exception...  <- Should not expose user information

Good

# Post-deployment check
User: Backend just released a new version, check if there are new errors on Sentry
AI: Querying latest Release...
  1. Found 20260303@A1B2C3D, linked to backend-service and consumer-service
  2. Checking issues associated with this Release...
  3. No new issues found, recommend continuing to monitor for 30min

# Client crash investigation
User: app-android latest version 2.85.0 has user reports of crashes
AI: Querying app-android project Release 2.85.0 related issues...
  1. Found latest build 2.85.0(b4f16c)
  2. Viewing unresolved issues, sorted by affected user count
  3. Viewing top issue stack trace -> locating code

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free