- Home
- Skills
- Mobile Development
- Android Logcat Crash Decoder
More screenshots
Works with the AI Agents you already use
Android Logcat Crash Decoder
Turn a raw logcat crash dump into a named cause, a responsible code location, and one specific next step.
$5
Android Logcat Crash Decoder
Example session with this skill installed
Decode this excerpt: a fatal section with java.lang.NullPointerException: detail id was null and a first app frame in com.example.app.Detail.bind.
- Read your context and instructions
- Compiled the android logcat crash
Running the bundled script on that excerpt produces:
FATAL-LINE: java.lang.NullPointerException: detail id was null
FRAMES-FOUND: 2
FIRST-APP-FRAME: com.example.app.Detail.bind
EXCEPTION-TYPE: java.lang.NullPointerException
The skill's worked example completes the decode: the crash happens only when a deep link carries no identifier, so the fix validates the identifier at screen entry and shows an error state, rather than merely guarding the binding line. Verification is repeating the exact deep-link action.
Connects securely to your tools. The creator never sees your data.
About this skill
A stack trace is only useful if it is read in the right order. This skill enforces a top-down decode: isolate the fatal section, read the exception line verbatim, walk frames to the first frame belonging to application code, handle obfuscation only with the mapping file for that exact build, form a trigger hypothesis with a disproof condition, and choose one executable next step.
It covers Java and native crashes, with a decision table spanning null dereferences, index errors, lifecycle misuse, cast errors, missing resources, parcel problems, out-of-memory errors, and native signals. It also names the traps: truncated tester excerpts labeled provisional, intermittent crashes that need stress captures, release-only crashes caused by shrinking, and the habit of guarding only the crash line while the producer of the bad value keeps running. A runnable decoder extracts the fatal line, exception type, and first app frame from a log file.
- Needs a trace; a symptom description with no log cannot be decoded.
- Obfuscated traces without the matching mapping file can only be classified by exception type.
- Freezes where the app stays alive (ANRs) need a different capture, not a crash trace.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 23 days ago