
asc-crash-triage
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.
- Installs
- 6.4K
- Last 24h
- +36
- Trending rank
- #4097
- Security
- Warn
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-crash-triage- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads asc-crash-triage automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
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, using
--output jsonfor responses that will be parsed. Forperformance download,--outputis the destination file path. - 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
- Types:
- 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"orasc 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
- Read-command output defaults to table in a terminal and JSON in pipes or CI. Select the format explicitly when parsing results.
- Use
--paginateto fetch all pages when doing a full analysis. - Use
--prettywith JSON for debugging command output. - Crash data from App Store Connect may have 24-48h delay.
FAQ
What does the asc-crash-triage skill do?
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.
How do I install asc-crash-triage?
Run npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-crash-triage in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/asc-crash-triage/ (personal) or .claude/skills/asc-crash-triage/ (project).
Which AI agents can use asc-crash-triage?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is asc-crash-triage safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk flagged items to review. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains asc-crash-triage?
It is published by rorkai in rorkai/app-store-connect-cli-skills. It has 6,417 recorded installs.
More from rorkai/app-store-connect-cli-skills
asc-cli-usage
rorkai/app-store-connect-cli-skills
Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
asc-release-flow
rorkai/app-store-connect-cli-skills
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and retry decisions to asc-submission-health.
asc-submission-health
rorkai/app-store-connect-cli-skills
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.
asc-metadata-sync
rorkai/app-store-connect-cli-skills
Sync, validate, and apply App Store metadata and store assets with asc. Use when updating localizations, keywords, App Clip or preview assets, Asset Library media and placements, or migrating legacy fastlane metadata.
asc-xcode-build
rorkai/app-store-connect-cli-skills
Build, archive, export, and manage Xcode version/build numbers with asc, including portable iOS compilation and packaging. Use when creating an IPA or PKG for App Store Connect, TestFlight, or registered-device release testing.
asc-id-resolver
rorkai/app-store-connect-cli-skills
Resolve App Store Connect IDs (apps, builds, app and digital-goods versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.