agentleFS
tarunyadav1tarunyadav1/ios-app-lifecycle/skills/ios-crash-monitoring-sentry/SKILL.md

ios-crash-monitoring-sentry

Skill1 starsChanged 40 days agoMITView on GitHub

Use when the user asks to triage iOS crashes or production errors in Sentry, or to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 7 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If not already authenticated, ask the user to provide a valid SENTRY_AUTH_TOKEN (read-only scopes such as project:read, event:read) or to …

    line 11
  2. Distinctive:

    Always call the Sentry API (no heuristics, no caching).

    line 15
  3. Distinctive:

    If the token is missing, give the user these steps:

    line 17
  4. Distinctive:

    Create a Sentry auth token: https://sentry.io/settings/account/api/auth-tokens/

    line 18
  5. Very specific:

    Create a token with read-only scopes such as project:read, event:read, and org:read.

    line 19
  6. Distinctive:

    Never ask the user to paste the full token in chat.

    line 22
  7. Very specific:

    Use scripts/sentry_api.py for deterministic API calls.

    line 26
  8. Very specific:

    If CLAUDE_PLUGIN_ROOT is not set, locate skills/ios-crash-monitoring-sentry/scripts/sentry_api.py inside the installed plugin directory.

    line 34
  9. Very specific:

    Use the returned id for issue detail or events.

    line 60
  10. Distinctive:

    Always use these endpoints (GET only):

    line 95
  11. Distinctive:

    If no results, state explicitly.

    line 116
  12. Distinctive:

    Never echo auth tokens.

    line 118

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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 (Read-only Observability)

Quick start

  • If not already authenticated, ask the user to provide a valid SENTRY_AUTH_TOKEN (read-only scopes such as project:read, event:read) or to log in and create one before running commands.
  • Set SENTRY_AUTH_TOKEN as an env var.
  • Optional defaults: SENTRY_ORG, SENTRY_PROJECT, SENTRY_BASE_URL.
  • Defaults: org/project {your-org}/{your-project}, time range 24h, environment prod, limit 20 (max 50).
  • Always call the Sentry API (no heuristics, no caching).

If the token is missing, give the user these steps:

  1. Create a Sentry auth token: https://sentry.io/settings/account/api/auth-tokens/
  2. Create a token with read-only scopes such as project:read, event:read, and org:read.
  3. Set SENTRY_AUTH_TOKEN as an environment variable in their system.
  4. Offer to guide them through setting the environment variable for their OS/shell if needed.
  • Never ask the user to paste the full token in chat. Ask them to set it locally and confirm when ready.

Core tasks (use bundled script)

Use scripts/sentry_api.py for deterministic API calls. It handles pagination and retries once on transient errors.

Bundled script path

export SENTRY_API="${CLAUDE_PLUGIN_ROOT}/skills/ios-crash-monitoring-sentry/scripts/sentry_api.py"

If CLAUDE_PLUGIN_ROOT is not set, locate skills/ios-crash-monitoring-sentry/scripts/sentry_api.py inside the installed plugin directory.

1) List issues (ordered by most recent)

python3 "$SENTRY_API" \
  --org {your-org} \
  --project {your-project} \
  list-issues \
  --environment prod \
  --time-range 24h \
  --limit 20 \
  --query "is:unresolved"

2) Resolve an issue short ID to issue ID

python3 "$SENTRY_API" \
  --org {your-org} \
  --project {your-project} \
  list-issues \
  --query "ABC-123" \
  --limit 1

Use the returned id for issue detail or events.

3) Issue detail

python3 "$SENTRY_API" \
  --org {your-org} \
  issue-detail \
  1234567890

4) Issue events

python3 "$SENTRY_API" \
  --org {your-org} \
  issue-events \
  1234567890 \
  --environment prod \
  --time-range 24h \
  --limit 20

5) Event detail (no stack traces by default)

python3 "$SENTRY_API" \
  --org {your-org} \
  --project {your-project} \
  event-detail \
  abcdef1234567890

API requirements

Always use these endpoints (GET only):

  • List issues: /api/0/projects/{org_slug}/{project_slug}/issues/
  • Issue detail: /api/0/organizations/{org_slug}/issues/{issue_id}/
  • Events for issue: /api/0/organizations/{org_slug}/issues/{issue_id}/events/
  • Event detail: /api/0/projects/{org_slug}/{project_slug}/events/{event_id}/

Inputs and defaults

  • org_slug: default to {your-org} (required for issue detail, issue events, and event detail).
  • project_slug: default to {your-project} (required for list issues and event detail).
  • time_range: default 24h (pass as statsPeriod for list issues and issue events).
  • environment: default prod (used by list issues and issue events).
  • limit: default 20, max 50 (paginate until limit reached).
  • search_query: optional query parameter.
  • issue_short_id: resolve via list-issues query first.

Output formatting rules

  • Issue list: show title, short_id, status, first_seen, last_seen, count, environments, top_tags; order by most recent.
  • Event detail: include culprit, timestamp, environment, release, url.
  • If no results, state explicitly.
  • Redact PII in output (emails, IPs). Do not print raw stack traces.
  • Never echo auth tokens.

Golden test inputs

  • Org: {your-org}
  • Project: {your-project}
  • Issue short ID: {ABC-123}

Example prompt: “List the top 10 open issues for prod in the last 24h.” Expected: ordered list with titles, short IDs, counts, last seen.

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.