Skill

Review

Audit score 70

asc-crash-triage

rudrankriyam/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, launches) using the asc CLI. Use this when investigating app stability issues, reviewing beta feedback, or diagnosing performance problems in TestFlight builds.

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 issues
Group crashes by signature, device, and OS for severity assessment
Resolve app and build IDs from names or bundle identifiers
Export crash and performance data in JSON, table, or markdown formats

How to install asc-crash-triage

npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-crash-triage

Prerequisites

asc CLI installed and configured 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.Resolve the app ID using asc apps list if you don't have it
2.Run the appropriate command: asc testflight crashes list, asc testflight feedback list, or asc performance diagnostics list
3.Parse the JSON output or use --output table/markdown for human-readable results
4.Group results by severity, device, OS, and build as needed
5.Use --paginate for comprehensive analysis across all pages of data

Use cases

Good for

Investigate a spike in crashes for a specific TestFlight build
Review beta tester feedback to identify common complaints or issues
Diagnose app hangs or excessive disk writes reported in performance metrics
Compare crash patterns across different device models and iOS versions
Generate a crash summary report for stakeholders before releasing to production

Who it's for

iOS app developers
QA engineers managing TestFlight testing
Release managers reviewing build stability
Support engineers triaging user-reported issues

asc-crash-triage FAQ

How do I list crashes for a specific build?

Use asc testflight crashes list --app "APP_ID" --build "BUILD_ID" --sort -createdDate --limit 10

Can I filter crashes by device or OS version?

Yes, use --device-model "iPhone16,2" and --os-version "18.0" flags to filter by specific devices and OS versions.

What performance diagnostic types are available?

Three types: HANGS, DISK_WRITES, and LAUNCHES. Filter with --diagnostic-type flag.

How do I include screenshots with beta feedback?

Use asc testflight feedback list with the --include-screenshots flag.

Why is crash data delayed?

App Store Connect crash data typically has a 24-48 hour delay before appearing in reports.

Full instructions (SKILL.md)

Source of truth, from rudrankriyam/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

Resolve the app ID if not provided (use asc apps list).
Fetch data with the appropriate command.
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:

Total count — how many crashes/feedbacks in the result set.
Top crash signatures — group by exception type or crash reason, ranked by count.
Affected builds — which build versions are impacted.
Device & OS breakdown — most affected device models and OS versions.
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.

Related skills

More from rudrankriyam/app-store-connect-cli-skills and the wider catalog.

asc-id-resolver

rudrankriyam/app-store-connect-cli-skills

Resolve App Store Connect IDs from human-friendly names for use in other asc commands.

2.3k installsAudited

asc-localize-metadata

rudrankriyam/app-store-connect-cli-skills

Automatically translate and sync App Store metadata to multiple languages using LLM and asc CLI.

2.0k installs

asc-metadata-sync

rudrankriyam/app-store-connect-cli-skills

Sync, validate, and apply App Store metadata with canonical asc workflow for localizations, keywords, and version fields.

2.4k installsAudited

asc-notarization

rudrankriyam/app-store-connect-cli-skills

Archive, export, and notarize macOS apps with Developer ID signing for distribution outside the App Store.

2.0k installs

asc-ppp-pricing

rudrankriyam/app-store-connect-cli-skills

Set territory-specific pricing for subscriptions and in-app purchases using App Store Connect CLI.

2.2k installsAudited

asc-release-flow

rudrankriyam/app-store-connect-cli-skills

Validate app readiness and drive App Store submission with asc, handling metadata, builds, IAP, subscriptions, and privacy checks.

2.5k installsAudited