agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/sentry/SKILL.md

sentry

Skill0 starsChanged 8 months agoMITView on GitHub

Use when the user wants to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data; prefer the current host's Sentry connector when available, otherwise use the bundled read-only API helper with `SENTRY_AUTH_TOKEN`.

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

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for read-only Sentry issue inspection, error summarization, event lookups, and lightweight production-health triage.

    line 9
  2. Very specific:

    Prefer the current host's Sentry connector if it exists.

    line 13
  3. Distinctive:

    Read before summarizing: list issues first, then drill into a specific issue or event only when needed.

    line 14
  4. Distinctive:

    Keep the public version read-only, reproducible, and safe for production support workflows.

    line 23
  5. Very specific:

    Do not request users to paste tokens into chat.

    line 26
  6. Distinctive:

    Do not mutate Sentry state or claim root cause unless the issue or event evidence supports it.

    line 27

“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

Intent

  • Use for read-only Sentry issue inspection, error summarization, event lookups, and lightweight production-health triage.

Default operating pattern

  1. Confirm scope first: organization, project, environment, time range, and whether the user wants issue lists, issue detail, or event detail.
  2. Prefer the current host's Sentry connector if it exists; otherwise use scripts/sentry_api.py with a locally configured SENTRY_AUTH_TOKEN.
  3. Read before summarizing: list issues first, then drill into a specific issue or event only when needed.
  4. Redact sensitive data and avoid dumping raw stack traces unless the user explicitly asks for deeper debugging detail.
  5. Return a clear operational summary: what is happening, how severe it looks, and which issue or event should be investigated next.

Bundled helper

  • scripts/sentry_api.py provides deterministic, read-only Sentry API calls for issues and events.

Pack fit

  • Included in: knowledge-ops
  • Keep the public version read-only, reproducible, and safe for production support workflows.

Boundary

  • Do not request users to paste tokens into chat; ask them to set SENTRY_AUTH_TOKEN locally.
  • Do not mutate Sentry state or claim root cause unless the issue or event evidence supports it.

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