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`.
In this repository15 other files it gives its agents.
- app-store-listingSkill
- ios-app-intentsSkill
- ios-debugger-agentSkill
- ios-ettrace-performanceSkill
- ios-lifecycleSkill
- ios-memgraph-leaksSkill
- ios-monetizationSkill
- ios-post-launchSkill
- ios-project-setupSkill
- ios-releaseSkill
- ios-testingSkill
- swiftui-liquid-glassSkill
- swiftui-performance-auditSkill
- swiftui-ui-patternsSkill
- swiftui-view-refactorSkill
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
- Very specific: line 11
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 …
- Distinctive: line 15
Always call the Sentry API (no heuristics, no caching).
- Distinctive: line 17
If the token is missing, give the user these steps:
- Distinctive: line 18
Create a Sentry auth token: https://sentry.io/settings/account/api/auth-tokens/
- Very specific: line 19
Create a token with read-only scopes such as project:read, event:read, and org:read.
- Distinctive: line 22
Never ask the user to paste the full token in chat.
- Very specific: line 26
Use scripts/sentry_api.py for deterministic API calls.
- Very specific: line 34
If CLAUDE_PLUGIN_ROOT is not set, locate skills/ios-crash-monitoring-sentry/scripts/sentry_api.py inside the installed plugin directory.
- Very specific: line 60
Use the returned id for issue detail or events.
- Distinctive: line 95
Always use these endpoints (GET only):
- Distinctive: line 116
If no results, state explicitly.
- Distinctive: line 118
Never echo auth tokens.
≈ “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.
Files
Sentry (Read-only Observability)
Quick start
- If not already authenticated, ask the user to provide a valid
SENTRY_AUTH_TOKEN(read-only scopes such asproject:read,event:read) or to log in and create one before running commands. - Set
SENTRY_AUTH_TOKENas an env var. - Optional defaults:
SENTRY_ORG,SENTRY_PROJECT,SENTRY_BASE_URL. - Defaults: org/project
{your-org}/{your-project}, time range24h, environmentprod, limit 20 (max 50). - Always call the Sentry API (no heuristics, no caching).
If the token is missing, give the user these steps:
- Create a Sentry auth token: https://sentry.io/settings/account/api/auth-tokens/
- Create a token with read-only scopes such as
project:read,event:read, andorg:read. - Set
SENTRY_AUTH_TOKENas an environment variable in their system. - 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 1Use the returned id for issue detail or events.
3) Issue detail
python3 "$SENTRY_API" \
--org {your-org} \
issue-detail \
12345678904) Issue events
python3 "$SENTRY_API" \
--org {your-org} \
issue-events \
1234567890 \
--environment prod \
--time-range 24h \
--limit 205) Event detail (no stack traces by default)
python3 "$SENTRY_API" \
--org {your-org} \
--project {your-project} \
event-detail \
abcdef1234567890API 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: default24h(pass asstatsPeriodfor list issues and issue events).environment: defaultprod(used by list issues and issue events).limit: default 20, max 50 (paginate until limit reached).search_query: optionalqueryparameter.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.
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
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.

