Asc Crash Triage
Summarize TestFlight crashes, beta tester feedback, and performance diagnostics using the asc CLI after a build ships to testers.
Overview
asc-crash-triage is an agent skill most often used in Operate (also Ship testing and Grow support) that fetches and summarizes TestFlight crashes and beta feedback via the asc CLI.
Install
npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-crash-triageWhat is this skill?
- Resolve app ID via asc apps list then fetch crashes with sort, build, and device filters
- TestFlight crash list commands with JSON or table output and optional pagination
- Beta feedback listing with screenshot inclusion and build-scoped filters
- Three-step workflow: resolve app → fetch with asc → parse JSON into human summary
- Performance-oriented queries for app hangs, launch diagnostics, and disk writes
- 3-step workflow: resolve app ID, fetch data, parse JSON summary
- Default list limit of 10 crashes or feedback items in examples
Adoption & trust: 639 installs on skills.sh; 845 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a TestFlight build in the wild and need a fast crash and feedback picture without manually exporting everything from App Store Connect.
Who is it for?
Indie iOS developers already using asc who want agent-driven crash and beta-feedback triage after each TestFlight drop.
Skip if: Android-only crash analytics or teams with no App Store Connect / asc CLI access.
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 filtered asc pull and a human-readable triage summary keyed to app, build, device, and OS so you can prioritize fixes or reject a build.
- Human-readable crash and feedback summary
- Command invocations with filters applied
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Operate is the canonical shelf because the workflow starts after builds are in TestFlight and you need ongoing crash and feedback intelligence. Errors subphase fits crash reports, hangs, launch diagnostics, and disk-write issues rather than pre-release coding.
Where it fits
Pull the ten newest TestFlight crashes for a build regression after a point release.
Compare crash counts between two TestFlight builds before promoting to external testers.
Aggregate beta feedback with screenshots to decide whether a UX issue blocks App Store submission.
How it compares
CLI orchestration skill for asc—not a replacement for Xcode Organizer symbolication or full mobile APM products.
Common Questions / FAQ
Who is asc-crash-triage for?
Solo and indie iOS builders who ship TestFlight builds and want scripted crash and feedback summaries through asc.
When should I use asc-crash-triage?
In Operate when crashes or hangs appear in TestFlight; during Ship when validating a beta build; in Grow support when synthesizing tester feedback before a release decision.
Is asc-crash-triage safe to install?
The skill drives asc against your App Store Connect account—review the Security Audits panel on this page and restrict credentials and network use to trusted environments.
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.