App Store Connect crash triage: TestFlight crashes, beta feedback and performance diagnostics
Fetch, analyze and summarize TestFlight crash reports, beta feedback and perf diagnostics via the asc CLI
- What
- Fetch, analyze and summarize TestFlight crash reports, beta feedback and perf diagnostics via the asc CLI
- Cost
- Free
- Needs
- the asc CLI installed and App Store Connect API access (app ID or bundle ID of the app to triage)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @rorkai's triage skill for App Store Connect: fetch, analyze and summarize TestFlight crash reports, beta tester feedback and performance diagnostics (app hangs, disk writes, launch diagnostics) through the `asc` CLI. The workflow resolves the app ID, lists recent crashes (filterable by build, device model, OS version), pulls beta feedback with screenshots, and reads performance diagnostic signatures — then presents a human-readable summary organized by severity and frequency (total count, top crash signatures, affected builds, device & OS breakdown, timeline). Honest caveats: requires the `asc` CLI plus App Store Connect API access; crash data from App Store Connect can lag 24–48 hours. MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: the asc CLI installed and App Store Connect API access (app ID or bundle ID of the app to triage) Install "App Store Connect crash triage: TestFlight crashes, beta feedback and performance diagnostics" for me. It gives my agent @rorkai's triage workflow: resolve the app ID (asc apps list), list recent TestFlight crashes with filters (build, device model, OS version, table/markdown output, pagination), pull beta feedback (optionally with screenshots), read performance diagnostic signatures (hangs, disk writes, launches) and download metrics — then summarize by severity and frequency (counts, top signatures, affected builds, device & OS breakdown, timeline). Note App Store Connect crash data can lag 24-48h. MIT-licensed. Repository: https://github.com/rorkai/app-store-connect-cli-skills/blob/main/skills/asc-crash-triage/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "asc-crash-triage". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the asc CLI and configure App Store Connect API access myself). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.