PluginBench
Skill
Review
Audit score 70

asc-crash-triage

rorkai/app-store-connect-cli-skills

Triage TestFlight crashes, beta feedback, and performance diagnostics from App Store Connect.

What is asc-crash-triage?

Fetch and analyze TestFlight crash reports, beta tester feedback, and performance diagnostics (hangs, disk writes, launch issues) using the asc CLI. Use this when investigating app stability issues, reviewing beta feedback, or diagnosing performance problems across builds and devices.

  • List and filter TestFlight crashes by build, device model, or OS version
  • Retrieve beta tester feedback with optional screenshots
  • Analyze performance diagnostics including hangs, disk writes, and launch metrics
  • Group crashes by signature, device, and OS for impact assessment
  • Generate summaries organized by severity, frequency, and timeline
  • Resolve app and build IDs from names or bundle identifiers

How to install asc-crash-triage

npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-crash-triage
Prerequisites
  • asc CLI installed and authenticated with App Store Connect credentials
  • App ID (can be resolved via asc apps list if not known)
  • Build ID for performance diagnostics (can be resolved via asc builds list)
Claude Code
Cursor
Windsurf
Cline

How to use asc-crash-triage

  1. 1.Resolve your app ID using `asc apps list --name "AppName"` if needed
  2. 2.Fetch crashes with `asc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10`
  3. 3.Optionally filter by build ID, device model, or OS version using additional flags
  4. 4.For performance data, get the latest build ID via `asc builds info --app "APP_ID" --latest --platform IOS`
  5. 5.List diagnostics with `asc performance diagnostics list --build-id "BUILD_ID"`
  6. 6.Parse JSON output and organize results by crash signature, device, OS, and timeline

Use cases

Good for
  • Investigate a spike in crashes for a specific TestFlight build
  • Review feedback from beta testers on a particular app version
  • Diagnose app hangs or disk write issues affecting certain device models
  • Compare crash patterns across multiple iOS versions
  • Generate a crash summary report for stakeholders before App Store release
Who it's for
  • iOS app developers
  • QA engineers managing TestFlight beta programs
  • Engineering leads reviewing app stability metrics
  • Release managers preparing for production launches

asc-crash-triage FAQ

How do I get crash data for a specific build?

Use `asc testflight crashes list --app "APP_ID" --build-id "BUILD_ID" --sort -createdDate` to filter crashes by build version.

What performance diagnostic types are available?

Three types: HANGS (app freezes), DISK_WRITES (excessive I/O), and LAUNCHES (slow startup). Filter with `--diagnostic-type` flag.

How current is the crash data from App Store Connect?

Crash data typically has a 24–48 hour delay, so recent crashes may not appear immediately.

Can I include screenshots with beta feedback?

Yes, use the `--include-screenshots` flag with `asc testflight feedback list` to download attached images.

How do I fetch all crashes or feedback, not just the top 10?

Use the `--paginate` flag to retrieve all pages of results in a single command.

Full instructions (SKILL.md)

Source of truth, from rorkai/app-store-connect-cli-skills.


name: asc-crash-triage description: Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.

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-id "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-id "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-id "BUILD_ID"
  • Filter by type: asc performance diagnostics list --build-id "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-id "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.