agentsclimarketplace
Sign in

Rudrankriyam asc crash triage

Skill JordanCoin/ios-skills-collection/skills/rudrankriyam--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.From its SKILL.md

Install
npx -y skills add JordanCoin/ios-skills-collection --skill rudrankriyam--asc-crash-triage

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

3 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 8 commands, including `asc apps list` and 7 more.

SKILL.md

3.3 KB, 764 tokens by cl100k_base, as published. Nobody here has run it

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.
  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 "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:

  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

  • 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.

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 764 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

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.