crash-analytics

When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, actionable crash-analytics skill that leads with concrete thresholds, executable code/commands, and explicit release-feedback loops. The main gaps are minor: a slightly explanatory ASO 'why' section and 1-star workflow lacking a verification step.

Suggestions

Tighten 'Why Crash Rate Is an ASO Signal' to the target metrics and drop the explanatory bullets that restate well-known ranking mechanics, to lift conciseness toward 5.

Add a verification step to the 'Responding to Crash-Driven 1-Star Reviews' workflow (e.g., confirm the crash fix is live and crash rate dropped before replying to reviews) to strengthen workflow_clarity.

Consider extracting the per-platform Crashlytics setup and the full triage priority table into a reference file linked from SKILL.md to improve progressive_disclosure now that the file is over 150 lines.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and dense with domain-specific facts (crash-free targets, triage weights, phased-release percentages) that Claude would not reliably know; the 'Why Crash Rate Is an ASO Signal' section is mildly explanatory and could be trimmed. Not a 5 because of that minor over-explanation; not a 3 because the bulk earns its place.	4 / 5
Actionability	Provides copy-paste-ready elements across the common cases — the upload-symbols bash command, the gradle dependency line, concrete P0–P3 triage thresholds, the crash-rate formula, and the 1%→100% phased-release schedule. Matches the fully-executable anchor.	5 / 5
Workflow Clarity	Multi-step processes (triage, crash-report debugging, 1-star response) are numbered and sequenced, with an explicit feedback loop ('If crash rate increases >0.2%, pause rollout') and a 'write a failing test before fixing' checkpoint. Not a 5 because the 1-star review workflow lacks a validation checkpoint; not a 3 because most checkpoints are present.	4 / 5
Progressive Disclosure	A single well-sectioned SKILL.md (~165 lines) with clear headers and no nested references; cross-skill navigation is clear via 'Related Skills'. Not a 5 because some inline material (detailed per-platform setup, triage tables) could plausibly live in reference files; not a 3 because structure is genuinely good.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: third-person, concrete actions, comprehensive natural trigger terms, and an explicit 'Use when' clause with a boundary pointer to a sibling skill. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking' — with comprehensive coverage; matches the score-5 anchor of multiple specific concrete actions.	5 / 5
Completeness	Clearly states what it does (monitor, triage, reduce crash rate; setup, prioritize, interpret, ASO impact) and explicitly when to use it ('Use when the user mentions...'), with concrete trigger phrases; not the score-4 anchor because 'when' is fully explicit rather than improvable.	5 / 5
Trigger Term Quality	Includes comprehensive natural terms with synonyms and acronyms — 'crash', 'crashlytics', 'ANR', 'app not responding', 'crash-free sessions', 'crash-free users', 'symbolication', 'stability', 'app crashing' — matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Carves a clear crash-analytics/ASO niche with distinct triggers and an explicit boundary pointer ('For overall analytics setup, see app-analytics'), giving minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Eronred/aso-skills
Path: skills/crash-analytics/SKILL.md
Commit: 4df730f

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.