agentsclimarketplace

Appstore crash insights

Skill Xopoko/build-swift-apps/skills/appstore-crash-insights

Triage TestFlight crashes, beta feedback, hangs, disk writes, launches, and performance diagnostics with `asc` crash/feedback/diagnostics commands.From its SKILL.md

Install
npx -y skills add Xopoko/build-swift-apps --skill appstore-crash-insights

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • runs commandsInstructs the agent to run 8 commands, including `asc apps list` and 7 more.

SKILL.md

2.1 KB, 492 tokens by cl100k_base, as published. Nobody here has run it

App Store Crash Insights

Fetch, analyze, and summarize TestFlight crash reports, beta feedback, and performance diagnostics.

Workflow

  1. Resolve app ID with asc apps list if missing.
  2. Resolve build ID when diagnostics need one.
  3. Fetch JSON with the narrowest useful command.
  4. Group by severity/frequency and summarize in human terms.

Commands

Crashes:

asc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10
asc testflight crashes list --app "APP_ID" --build "BUILD_ID" --sort -createdDate --limit 10
asc testflight crashes list --app "APP_ID" --device-model "iPhone16,2" --os-version "18.0"
asc testflight crashes list --app "APP_ID" --paginate

Feedback:

asc testflight feedback list --app "APP_ID" --sort -createdDate --limit 10
asc testflight feedback list --app "APP_ID" --sort -createdDate --limit 10 --include-screenshots
asc testflight feedback list --app "APP_ID" --build "BUILD_ID" --sort -createdDate
asc testflight feedback list --app "APP_ID" --paginate

Performance diagnostics:

asc builds info --app "APP_ID" --latest --platform IOS
asc builds list --app "APP_ID" --sort -uploadedDate --limit 5
asc performance diagnostics list --build "BUILD_ID"
asc performance diagnostics list --build "BUILD_ID" --diagnostic-type "HANGS"
asc performance diagnostics view --id "SIGNATURE_ID"
asc performance download --build "BUILD_ID" --output ./metrics.json

Diagnostic types: HANGS, DISK_WRITES, LAUNCHES.

Resolve IDs with asc apps list --name "AppName", asc apps list --bundle-id "com.example.app", or export ASC_APP_ID="APP_ID".

Summary

Report total count, top crash signatures, affected builds, device/OS breakdown, timeline/spikes, and highest-weight performance signatures. Default output is JSON; use table/markdown for quick human review, --paginate for full analysis, and --pretty for JSON debugging. ASC crash data can lag 24-48h.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most error diagnosis skills give in 492 tokens

Counted across 135 of the 162 authors here whose files we hold, read 2026-09-06

  • Handle, re-throw, or log in every catch blockin 12 of 135, across 7 files
  • Use typed error classes over string messagesin 11 of 135, across 6 files
  • Log full error context server-sidein 10 of 135, across 5 files
  • Document every error code clients may receivein 9 of 135, across 4 files
  • Surface errors at the boundary where they occurin 9 of 135, across 4 files
  • Wrap React components in an ErrorBoundaryin 9 of 135, across 4 files
  • Wrap errors with context, never lose the originalin 9 of 135, across 4 files
  • Use the standard error envelope for API responsesin 9 of 135, across 4 files
  • Retry only retriable errors, never 4xx client errorsin 8 of 135, across 3 files
  • Retry transient failures with exponential backoff and jitterin 8 of 135
  • Show users friendly messages without technical detailsin 7 of 135, across 3 files
  • Use the Result pattern for expected failuresin 7 of 135, across 5 files

Said here and by no other author read

  • Resolve the app ID with asc apps list if missing
  • Fetch JSON with the narrowest useful command
  • Group crashes by severity and frequency
  • Summarize findings in human terms
  • Report totals, top signatures, builds, devices, timeline
  • Pass --output json explicitly for automation

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.