top-crashers
Get top crashers from Brave's Backtrace crash reporting. Shows crash signatures, stacks, platforms, versions, channel breakdown, code origin, and regression detection. Triggers on: top crashers, crash report, what's crashing, top crashes, crash analysis, regression crashers, new crashes.
Profile →npx skills add majiayu000/claude-skill-registry --skill top-crashers --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Top Crashers Query Brave's Backtrace crash reporting instance for top crashers. Returns developer-actionable data including crash signatures, stack traces, platform/version breakdowns, channel mapping, code origin classification, and triage URLs. **PII-safe**: Only aggregate data is output. Use the triage URLs for full crash details. --- ## When to Use - **Investigating stability regressions** after a release - **Prioritizing crash fixes** — which crashes affect the most users - **Detecting new crashers** introduced by recent changes - **Filing crash bugs** — the output includes suggested issue titles and labels - **During development** — checking if your area of code has top crashers --- ## Environment Requirements The `BACKTRACE_API_KEY` environment variable must be set with a token that has `query:post` capability. The `BACKTRACE_PROJECT` environment variable should also be set (or pass `--project` as an argument). If not set, inform the user: ``` BACKTRACE_API_KEY must be set. Create a token with query:post capability in Backtrace project settings. BACKTRACE_PROJECT should be set to the Backtrace project name (or pass --project). ``` --- ## The Job When invoked, run the top-c
- When to Use
- Environment Requirements
- The Job
- Step 1: Parse Arguments
- Step 2: Run the Script
- Step 3: Present Results
- GitHub Formatting Rules
- Step 4: Offer Follow-Up Actions
- Usage Examples
- Script Details
- Output Fields Per Crash Group
- Version Format
- Limitations
python3 ./scripts/top-crashers.py --project "$BACKTRACE_PROJECT" --format json [parsed flags] python3 ./scripts/top-crashers.py --project "$BACKTRACE_PROJECT" Top 10, JSON output for parsing python3 ./scripts/top-crashers.py --project "$BACKTRACE_PROJECT" --format json --limit 10 Real crashes only (exclude DumpWithoutCrashing) python3 ./scripts/top-crashers.py --project "$BACKTRACE_PROJECT" --crashes-only Crashes affecting current Nightly python3 ./scripts/top-crashers.py --project "$BACKTRACE_PROJECT" --channels nightly Crashes on Nightly and Beta python3 ./scripts/top-crashers.py --project "$BACKTRACE_PROJECT" --channels nightly,beta
What does the top-crashers skill do?
Get top crashers from Brave's Backtrace crash reporting. Shows crash signatures, stacks, platforms, versions, channel breakdown, code origin, and regression detection. Triggers on: top crashers, crash report, what's crashing, top crashes, crash analysis, regression crashers, new crashes.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill top-crashers --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.