Use this skill to fetch, analyze, and summarize TestFlight crash reports, beta feedback, and performance diagnostics.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionasc-crash-triageExecute the skills CLI command in your project's root directory to begin installation:
Fetches asc-crash-triage from rudrankriyam/asc-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate asc-crash-triage. Access via /asc-crash-triage in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
710
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
710
stars
Use this skill to fetch, analyze, and summarize TestFlight crash reports, beta feedback, and performance diagnostics.
asc apps list).List recent crashes (newest first):
asc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10asc testflight crashes list --app "APP_ID" --build "BUILD_ID" --sort -createdDate --limit 10asc testflight crashes list --app "APP_ID" --device-model "iPhone16,2" --os-version "18.0"asc testflight crashes list --app "APP_ID" --paginateasc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10 --output tableList recent feedback (newest first):
asc testflight feedback list --app "APP_ID" --sort -createdDate --limit 10asc testflight feedback list --app "APP_ID" --sort -createdDate --limit 10 --include-screenshotsasc testflight feedback list --app "APP_ID" --build "BUILD_ID" --sort -createdDateasc testflight feedback list --app "APP_ID" --paginateRequires 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.
asc performance diagnostics list --build "BUILD_ID"asc performance diagnostics list --build "BUILD_ID" --diagnostic-type "HANGS"
HANGS, DISK_WRITES, LAUNCHESasc performance diagnostics view --id "SIGNATURE_ID"asc performance download --build "BUILD_ID" --output ./metrics.jsonasc apps list --name "AppName" or asc apps list --bundle-id "com.example.app"asc builds info --app "APP_ID" --latest --platform IOSasc builds list --app "APP_ID" --sort -uploadedDate --limit 5export ASC_APP_ID="APP_ID"When presenting results, organize by severity and frequency:
For performance diagnostics, highlight the highest-weight signatures first.
--output table or --output markdown for quick human review.--paginate to fetch all pages when doing a full analysis.--pretty with JSON for debugging command output.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend asc-crash-triage for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
asc-crash-triage reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in asc-crash-triage — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
asc-crash-triage fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added asc-crash-triage from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: asc-crash-triage is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for asc-crash-triage matched our evaluation — installs cleanly and behaves as described in the markdown.
asc-crash-triage has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added asc-crash-triage from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
asc-crash-triage reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 42