agentleFS
Sign inStart free
SentryKnown publishergetsentry/junior/packages/junior-sentry/skills/sentry/SKILL.md

sentry

Skill394 starsChanged 7 months agoApache-2.0View on GitHub

Query live Sentry telemetry, make explicitly requested Sentry configuration changes (projects, teams, alerts, and monitors), and generate Sentry deep links. Use when users ask to investigate Sentry issues, events, logs, traces, organizations, projects, replays, product feature usage, Sentry's own product telemetry, authenticated Sentry API data, to create or configure Sentry projects and teams, to assign teams to projects, or to create alerting. Do not use it for repository/source-code/PR tasks, even when the topic concerns Sentry products.

We split this skill into the rules it gives an agent

26 rules. 0 are common, 11 are distinctive, and 15 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 15

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for live Sentry investigation workflows in the harness.

    line 9
  2. Distinctive:

    Before declaring a Sentry data surface unavailable, verify the current CLI help:

    line 11
  3. Very specific:

    Run sentry --help for top-level command groups.

    line 13
  4. Very specific:

    Run sentry <command> --help or sentry help <command> before using a command shape from memory.

    line 14
  5. Very specific:

    If a remembered plural command fails, check for the current singular command group before blocking.

    line 15
  6. Distinctive:

    If org is missing and needed, ask the user.

    line 24
  7. Very specific:

    Use sentry <command> for structured queries.

    line 29
  8. Distinctive:

    Read references/cli-commands.md when choosing command shapes, target formats, flags, API fallback, or troubleshooting behavior.

    line 32
  9. Distinctive:

    Read references/sandbox-runtime.md before relying on sandbox credentials.

    line 33
  10. Very specific:

    Prefer --json when parsing or summarizing results.

    line 34
  11. Very specific:

    If no high-level CLI command covers the request, use sentry api <endpoint> before claiming the workflow is blocked.

    line 35
  12. Very specific:

    Prefer sentry alert metrics for metric alerts.

    line 37
  13. Very specific:

    If a Sentry API call returns 401, or clearly says the token is invalid, expired, revoked, or unauthorized, rerun the real Sentry command …

    line 38
  14. Very specific:

    If a Sentry API call explicitly says missing scope, missing scopes, or insufficient scope, rerun the real Sentry command once and let the …

    line 39
  15. Very specific:

    If a Sentry API call returns a generic 403, permission denied, or otherwise indicates missing org/project access without naming missing …

    line 40
  16. Very specific:

    Only mention a specific missing scope when the CLI or API error explicitly names that scope.

    line 41
  17. Very specific:

    Read references/cli-commands.md for the write command shapes.

    line 45
  18. Distinctive:

    Read the current state first.

    line 47
  19. Very specific:

    Run the complete command with --dry-run first, then run it once without --dry-run.

    line 49
  20. Distinctive:

    Read the resource again and report what changed (before → after) with the Sentry URL.

    line 50
  21. Distinctive:

    Read references/deep-link-patterns.md for URL templates.

    line 56
  22. Distinctive:

    Write only when the user asks for that change.

    line 65
  23. Very specific:

    Avoid speculative Sentry CLI subcommands.

    line 66
  24. Distinctive:

    Do not print credential values.

    line 67
  25. Distinctive:

    Prefer deep links over raw data dumps when linking to Sentry web UI.

    line 69
  26. Very specific:

    Do not use this skill for repository/source-code/commit/branch/pull-request work, even if the user mentions a Sentry feature or product …

    line 70

“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 Operations

Use this skill for live Sentry investigation workflows in the harness.

Before declaring a Sentry data surface unavailable, verify the current CLI help:

  • Run sentry --help for top-level command groups.
  • Run sentry <command> --help or sentry help <command> before using a command shape from memory.
  • If a remembered plural command fails, check for the current singular command group before blocking. Prefer canonical forms such as sentry issue list, sentry org list, sentry log list, and sentry trace list.

Workflow

  1. Confirm operation and target:
  • Determine operation: issue, event, log, trace, org, project, replay/deep-link, Sentry product feature usage, project/team configuration, alert/monitor creation, or API query.
  • Resolve org from channel config: jr-rpc config get sentry.org
  • Resolve project from channel config: jr-rpc config get sentry.project (optional — many queries span multiple projects).
  • If org is missing and needed, ask the user.
  • If an active repository context exists (cloned repo or configured github.repo), check the repo root for TELEMETRY.md before forming queries. When present, use its query recipes, org/project mappings, and investigation pivots as repo-specific guidance. Explicit user targets, IDs, URLs, and conversation config still win. If absent, continue normally.
  1. Execute via CLI:
  • Use sentry <command> for structured queries.
  • A repo can put its own sentry program first on PATH, for example in a getsentry/sentry checkout. If sentry --help does not show the Sentry CLI, run /vercel/sandbox/.junior/bin/sentry instead.
  • The runtime authenticates Sentry HTTP traffic for this skill. Do not set or print token env vars.
  • Read references/cli-commands.md when choosing command shapes, target formats, flags, API fallback, or troubleshooting behavior.
  • Read references/sandbox-runtime.md before relying on sandbox credentials.
  • Prefer --json when parsing or summarizing results.
  • If no high-level CLI command covers the request, use sentry api <endpoint> before claiming the workflow is blocked.
  • For an explicitly requested write, follow the write workflow below.
  • Prefer sentry alert metrics for metric alerts. Use sentry api only when live CLI help confirms the first-class command cannot express the requested alert behavior, such as dynamic anomaly detection.
  • If a Sentry API call returns 401, or clearly says the token is invalid, expired, revoked, or unauthorized, rerun the real Sentry command once and let the runtime trigger a reconnect flow when needed.
  • If a Sentry API call explicitly says missing scope, missing scopes, or insufficient scope, rerun the real Sentry command once and let the runtime trigger a reconnect flow when needed.
  • If a Sentry API call returns a generic 403, permission denied, or otherwise indicates missing org/project access without naming missing scopes, stop and tell the user the current Sentry connection could not access the requested Sentry data.
  • Only mention a specific missing scope when the CLI or API error explicitly names that scope. Do not guess scope names from a generic 403.
  1. Make requested writes:
  • Read references/cli-commands.md for the write command shapes. Use sentry schema <resource> to confirm the current endpoint and fields before an API write.
  • Resolve the exact org, project, team, and member slugs or IDs. Ask when the target is ambiguous; do not guess.
  • Read the current state first. Stop on a likely duplicate (for example, a project or team with the same slug) and report it.
  • Change only the fields the user asked for. Do not reset or rewrite other settings.
  • Run the complete command with --dry-run first, then run it once without --dry-run.
  • Read the resource again and report what changed (before → after) with the Sentry URL.
  • For a destructive or irreversible change (a delete, removing a team from a project, a slug rename, or a transfer), make sure the user named that exact action in the current request.
  1. Generate deep links:
  • For user-scoped or entity-specific views, generate URLs instead of CLI calls.
  • Read references/deep-link-patterns.md for URL templates.
  1. Report result:
  • Return issue details, replay links, deep links, or CLI output inline.
  • Include Sentry web URLs for easy navigation.

Guardrails

  • Write only when the user asks for that change.
  • Avoid speculative Sentry CLI subcommands. Use bundled references plus live sentry --help output to verify current commands.
  • Do not print credential values.
  • If org is missing and needed, ask the user.
  • Prefer deep links over raw data dumps when linking to Sentry web UI.
  • Do not use this skill for repository/source-code/commit/branch/pull-request work, even if the user mentions a Sentry feature or product area.

Download now (ZIP)

  • Other versions34 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 34

    1. openai/skills★ 27ksame name
    2. anthropics/claude-quickstarts★ 19ksame name
    3. openai/plugins★ 7.4ksame name
    4. Expensify/App★ 5.1ksame name
    5. mitsuhiko/agent-commands★ 3.2ksame name
    6. mitsuhiko/agent-stuff★ 3.2ksame name
    7. chrisdoc/hevy-mcp★ 529same name
    8. wnzzer/rank-analysis★ 439same name
    9. JetBrains/skills★ 386same name
    10. brianlovin/claude-config★ 376same name

    24 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use ghidra, firebase and 7 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

    • 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

    • NVIDIASkill

      github

      Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.

      Also in 8 projects that use this

    • VercelSkill

      slack

      Emulated Slack API for local development and testing. Use when the user needs to interact with Slack API endpoints locally, test Slack integrations, emulate channels/messages/users/views, set up Slack OAuth flows, test incoming webhooks, or work with the Slack Web API without hitting the real Slack API. Triggers include "Slack API", "emulate Slack", "mock Slack", "test Slack OAuth", "Slack bot", "Slack views", "incoming webhook", "local Slack", or any task requiring a local Slack API.

      Also in 3 projects that use this

    • +3 more from mitsuhiko
  • In this repository42 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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