Crash Monitoring
CheckedProactively detects application crashes & anomalies in real-time, alerting teams via fwrite0920's crash-monitoring skill.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
Crash Monitoring, not the name it is listed under, so the command below uses that name.- 1
Run this in your project
terminal$ npx skills add fwrite0920/android-skills --skill "Crash Monitoring" -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
fwrite0920
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned fwrite0920/android-skills at 9a9cf1e4dd.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 9a9cf1e4dd
- Manifest
- crash_monitoring/SKILL.md
- Scanned
- 1 file, 267 lines
About this skill
What it does
This skill enables AI agents to monitor Android application crashes and provide insights into their causes. It collects crash reports, aggregates them, and presents data in a structured format for analysis. The agent can then use this information to identify patterns, prioritize fixes, and improve overall app stability.
When to use it
- Debugging Production Issues: Quickly investigate reported crashes from live Android applications.
- Proactive Stability Improvement: Identify recurring crash patterns before they impact a large number of users.
- New Feature Rollout: Monitor for unexpected crashes when deploying new features or updates.
- Performance Analysis: Correlate crash data with performance metrics to understand the root cause of instability.
Key capabilities
- Crash report collection
- Data aggregation and analysis
- Structured reporting format
- Pattern identification
Example prompts
- "Show me the most frequent crash types in the last 24 hours."
- "What devices are experiencing the highest number of crashes?"
- "Summarize the crash reports related to version 1.2.3 of the app."
- “Give me a list of all crashes with stack traces containing 'NullPointerException'."
Tips & gotchas
This skill requires access to Android application crash reporting data, typically through a third-party service or internal logging infrastructure. Ensure proper configuration and permissions are in place for the AI agent to retrieve this information.