crash-analysis SKILL.md skillA

crash-analysis from dongduong2001/pudo-code-system is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add dongduong2001/pudo-code-system/crash-analysis@git:20260506.478f83b

Pins git:20260506.478f83b in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
dongduong2001/pudo-code-system
Path
skills/debug/crash-analysis/SKILL.md
Versions recorded
1
Latest version
git:20260506.478f83b, committed May 6, 2026
Size
898 bytes
Repository stars
5
License
MIT

Analyzing core dumps, stack traces, and unhandled exceptions.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Crash Analysis Skill

This skill is designed for debugging fatal errors that result in process termination or generic 500 crashes.

## When to use this skill
- When facing segmentation faults, null pointer exceptions, or stack overflows.
- When an application terminates abruptly without graceful error logs.
- When analyzing core dumps or fatal crash reports.

## Guidelines
- **Start at the Source:** Always look at the top/bottom of the stack trace to find the exact line of application code that triggered the failure, ignoring framework-level abstractions if possible.
- **Reproducibility:** Prioritize establishing a reliable reproduction path or writing a fast failing test.
- **State Capture:** Identify what the data state was exactly at the moment of the crash (variables, inputs).

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_exl3gf62m72yduw7/d41dac525c5b420361c8e6fb2c5587bf0b20336aa020aee809855bdb2272ae39.json

Then /plugin install crash-analysis@markdownregistry-exl3gf62m72yduw7 in Claude Code. It installs git:20260506.478f83b, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add dongduong2001/pudo-code-system/crash-analysis@sha256:d41dac525c5b4203

The line at the top of this page pins the label git:20260506.478f83b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_exl3gf62m72yduw7.svg)](https://markdownregistry.com/a/art_exl3gf62m72yduw7)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in dongduong2001/pudo-code-system/crash-analysis since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of crash-analysis from somewhere else? Ask it: where did my crash-analysis come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on May 6, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260506.478f83b latest2026-05-06 478f83b 898 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (898 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

dongduong2001/pudo-code-system · 5 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_exl3gf62m72yduw7
GET https://markdownregistry.com/api/v1/resolve?ref=dongduong2001/pudo-code-system/crash-analysis
GET https://markdownregistry.com/api/v1/blob/d41dac525c5b420361c8e6fb2c5587bf0b20336aa020aee809855bdb2272ae39

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from dongduong2001/pudo-code-system

AGENTS.md AGENTS.md file
dongduong2001/pudo-code-system · AGENTS.md
git:20260625.15b55d6 · audit A · 5 stars
CLAUDE.md CLAUDE.md file
dongduong2001/pudo-code-system · CLAUDE.md
git:20260625.15b55d6 · audit A · 5 stars
CLAUDE.md@claude CLAUDE.md file
dongduong2001/pudo-code-system · claude/CLAUDE.md
git:20260625.15b55d6 · audit A · 5 stars
pudo-handoff SKILL.md skill
dongduong2001/pudo-code-system · claude/plugin/skills/pudo-handoff/SKILL.md · Write the PUDO session handoff (.pudo/session.md) so another session, tool or teammate can continue the work. Use when…
git:20261023.b8e61c3 · audit A · 5 stars
pudo-plan SKILL.md skill
dongduong2001/pudo-code-system · claude/plugin/skills/pudo-plan/SKILL.md · PUDO Plan phase: turn a request into a short plan card (goal, scope, out of scope, success criteria, risks, steps)…
git:20261023.b8e61c3 · audit A · 5 stars
pudo-review SKILL.md skill
dongduong2001/pudo-code-system · claude/plugin/skills/pudo-review/SKILL.md · PUDO Optimize gate: review the current diff against the plan before calling work done: correctness, edge cases, tests…
git:20261023.b8e61c3 · audit A · 5 stars
pudo SKILL.md skill
dongduong2001/pudo-code-system · claude/plugin/skills/pudo/SKILL.md · PUDO workflow: Plan -> Understand -> Develop -> Optimize. Use on any non-trivial coding task (features, bug fixes…
git:20261023.b8e61c3 · audit A · 5 stars
AGENTS.md@codex AGENTS.md file
dongduong2001/pudo-code-system · codex/AGENTS.md
git:20260519.13df8aa · audit A · 5 stars
pudo-core Cursor rule
dongduong2001/pudo-code-system · cursor/.cursor/rules/pudo-core.mdc · Core PUDO workflow rules for all Cursor agent work.
git:20260522.82cda77 · audit A · 5 stars
pudo-develop Cursor rule
dongduong2001/pudo-code-system · cursor/.cursor/rules/pudo-develop.mdc · Use when implementing planned changes.
git:20260522.5ddc561 · audit A · 5 stars
pudo-optimize Cursor rule
dongduong2001/pudo-code-system · cursor/.cursor/rules/pudo-optimize.mdc · Use when reviewing, verifying, or preparing changes for release.
git:20260522.ae06784 · audit A · 5 stars
pudo-plan Cursor rule
dongduong2001/pudo-code-system · cursor/.cursor/rules/pudo-plan.mdc · Use when defining scope, success criteria, risks, and implementation plans.
git:20260522.58c45c8 · audit A · 5 stars

Every file in dongduong2001/pudo-code-system

Browse by kind, by grade A, or by owner.