asc-crash-triage

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha c079831542f6 · 24 Oct 2026Report an issue or request a re-scan

• Publisherrudrankriyam GitHub organizationOwner of the repository this skill is read from
• Source folderrudrankriyam/app-store-connect-cli-skills/skills/asc-crash-triageThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdictc079831542f6A new audit runs when the source changes
• Repository statusNot archivedLast push 4 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its 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…

---
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, using `--output json` for responses that will be parsed. For `performance download`, `--output` is the destination file path.
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

- Read-command output defaults to table in a terminal and JSON in pipes or CI. Select the format explicitly when parsing results.
- 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.

Excerpt, first 3,524 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/rudrankriyam/app-store-connect-cli-skills
git -C app-store-connect-cli-skills checkout c079831542f6

Works in

1. 2026-10-24
   ✓SAFE B 89 / 100

   first audit · source c079831542f6

Questions about asc-crash-triage

• github.com/rudrankriyam/app-store-connect-cli-skills/tree/main/s — the audited source at commit c079831542f6 and every finding aboveObserved · 24 Oct 2026

Spotted something wrong? Report a correction · Methodology