Asc Crash Triage
Summarize TestFlight crashes, beta feedback, hangs, and performance diagnostics for an iOS build using the asc CLI.
Overview
asc crash triage is an agent skill most often used in Operate (also Ship testing) that fetches and summarizes TestFlight crashes, beta feedback, and performance diagnostics via the asc CLI.
Install
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-crash-triageWhat is this skill?
- Resolves app ID via asc apps list when the user omits it
- Lists TestFlight crashes with sort, build, device, and OS filters plus paginate and table output
- Pulls beta feedback with optional screenshots and build filters
- Covers performance diagnostics: app hangs, disk writes, launch issues per skill trigger list
- Human-readable JSON summaries after structured asc commands
- Default crash and feedback list commands use --limit 10 with -createdDate sort
Adoption & trust: 1.6k installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have TestFlight signal scattered across asc JSON output and no quick human summary for which build or device class is failing.
Who is it for?
Solo iOS builders already using asc with App Store Connect API access who triage beta crashes and tester notes daily.
Skip if: Android Play Console workflows, teams without asc installed, or deep native debugging without App Store Connect identifiers.
When should I use this skill?
User asks about TestFlight crashes, beta feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.
What do I get? / Deliverables
You get a sorted, filtered crash and feedback summary tied to app and build IDs so you can prioritize fixes before the next TestFlight upload.
- Resolved app ID when missing
- Filtered asc crash/feedback/diagnostics fetch
- Human-readable triage summary
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Crash triage is canonical in Operate/errors because it responds to live beta and production-adjacent signals after ship. Errors subphase fits parsing crash lists, diagnostics, and tester feedback into actionable summaries.
Where it fits
Compare crash counts between two TestFlight builds before promoting a release candidate.
Summarize newest crashes and hang diagnostics after a spike in tester reports.
Pull paginated crash lists to watch device/OS clusters during a long beta.
How it compares
CLI triage skill for App Store Connect lists—not a substitute for in-Xcode Instruments sessions on a repro device.
Common Questions / FAQ
Who is asc-crash-triage for?
Indie and solo iOS developers shipping with TestFlight who want their agent to run asc and summarize crashes and beta feedback.
When should I use asc-crash-triage?
Use it in Operate/errors when monitoring beta health, and in Ship/testing when comparing crash rates across TestFlight builds before wider release.
Is asc-crash-triage safe to install?
It implies App Store Connect API credentials via asc; review the Security Audits panel on this page and rotate keys if the skill runs in shared CI agents.
SKILL.md
READMESKILL.md - Asc Crash Triage
# asc crash triage Use this skill to fetch, analyze, and summarize TestFlight crash reports, beta feedback, and performance diagnostics. ## Workflow 1. Resolve the app ID if not provided (use `asc apps list`). 2. Fetch data with the appropriate command. 3. Parse JSON output and present a human-readable summary. ## TestFlight crash reports List recent crashes (newest first): - `asc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10` - Filter by build: `asc testflight crashes list --app "APP_ID" --build "BUILD_ID" --sort -createdDate --limit 10` - Filter by device/OS: `asc testflight crashes list --app "APP_ID" --device-model "iPhone16,2" --os-version "18.0"` - All crashes: `asc testflight crashes list --app "APP_ID" --paginate` - Table view: `asc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10 --output table` ## TestFlight beta feedback List recent feedback (newest first): - `asc testflight feedback list --app "APP_ID" --sort -createdDate --limit 10` - With screenshots: `asc testflight feedback list --app "APP_ID" --sort -createdDate --limit 10 --include-screenshots` - Filter by build: `asc testflight feedback list --app "APP_ID" --build "BUILD_ID" --sort -createdDate` - All feedback: `asc testflight feedback list --app "APP_ID" --paginate` ## Performance diagnostics (hangs, disk writes, launches) Requires a build ID. Resolve via `asc builds info --app "APP_ID" --latest --platform IOS` or `asc builds list --app "APP_ID" --sort -uploadedDate --limit 5`. - List diagnostic signatures: `asc performance diagnostics list --build "BUILD_ID"` - Filter by type: `asc performance diagnostics list --build "BUILD_ID" --diagnostic-type "HANGS"` - Types: `HANGS`, `DISK_WRITES`, `LAUNCHES` - View logs for a signature: `asc performance diagnostics view --id "SIGNATURE_ID"` - Download all metrics: `asc performance download --build "BUILD_ID" --output ./metrics.json` ## Resolving IDs - App ID from name: `asc apps list --name "AppName"` or `asc apps list --bundle-id "com.example.app"` - Latest build ID: `asc builds info --app "APP_ID" --latest --platform IOS` - Recent builds: `asc builds list --app "APP_ID" --sort -uploadedDate --limit 5` - Set default: `export ASC_APP_ID="APP_ID"` ## Summary format When presenting results, organize by severity and frequency: 1. **Total count** — how many crashes/feedbacks in the result set. 2. **Top crash signatures** — group by exception type or crash reason, ranked by count. 3. **Affected builds** — which build versions are impacted. 4. **Device & OS breakdown** — most affected device models and OS versions. 5. **Timeline** — when crashes started or spiked. For performance diagnostics, highlight the highest-weight signatures first. ## Notes - Default output is JSON; use `--output table` or `--output markdown` for quick human review. - Use `--paginate` to fetch all pages when doing a full analysis. - Use `--pretty` with JSON for debugging command output. - Crash data from App Store Connect may have 24-48h delay.