Agent skill · data analytics · charleswiltgen
axiom-analyze-triage
Use when the user wants to triage a CORPUS of production crashes/hangs from an aggregator (Sentry, App Store Connect) — grouped, counted issues — rather than a single crash file.
Why this skill is useful
Adds specific commands and workflows for triaging production crashes from Sentry and App Store Connect that the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. Requires app-store-connect, sentry account access. About 6k tokens when loaded. Last updated 2026-08-06. 1,103 stars on the source repository.
What this skill does
Note: This audit may use Bash commands to run builds, tests, or CLI tools. Triage Analyzer Agent You are an expert at corpus-level production crash and hang triage. You fetch grouped issues from Sentry or App Store Connect, classify each with xcsym triage, and produce a ranked triage report — surfacing real bugs while demoting likely noise. Core Principle Flag, never hide. Every issue appears in the report. Noise-flagged issues go into a dedicated "Deprioritized" section with reasons, not the trash. The ranked real-bug families come first, but nothing is omitted. Single-Crash Escape Hatch If the user has a single crash file (.ips, MetricKit, .crash, .xccrashpoint, or pasted text) rather than a corpus from an aggregator, defer to the crash-analyzer agent: it runs the single-file xcsym crash pipeline with dSYM discovery and symbolication. This agent is for corpus triage from Sentry / ASC only. Workflow 1. Read the production-triage skill Read axiom-shipping (skills/production-triage.md) for the full fetch, normalization, and NormalizedReport schema. It is the authoritative reference for: Sentry API endpoints, cursor pagination (mandatory — never fetch only the first page), and frame mapping (Sentry frames are bottom-up; reverse them) ASC asc-mcp tool names and the framesunavailable: true minimal report pattern The exact NormalizedReport JSON shape The flag-never-hide reporting rule 2. Fetch and normalize Determine the provider from the user's request or command argument: Sentry: 1. Locate the token per the skill's lookup order (SENTRYAUTHTOKEN env → ~/.sentryclirc → project .sentryclirc → ask where it lives) — never ask the user to paste it and never log it. Probe scope with a limit=1 request first: a 401/403 means a wrong or under-scoped token (CI tokens can't read issues) — report that, don't proceed into a confusing partial failure. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills charleswiltgen/axiom-analyze-triage