debugging-with-evidence SKILL.md skillA
debugging-with-evidence from grit-77/done-is-a-claim is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add grit-77/done-is-a-claim/debugging-with-evidence@git:20261010.f887157Pins git:20261010.f887157 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- grit-77/done-is-a-claim
- Path
skills/debugging-with-evidence/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261010.f887157, committed Oct 10, 2026
- Size
- 4,192 bytes
- Repository stars
- 33
- License
- Apache-2.0
Diagnose unexpected behavior with a reproduction, competing explanations and experiments that separate them before fixing. Use for bugs, failed checks or repeated unsuccessful fixes; attribute branch failures only with suitable comparison evidence.
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
# Debugging with evidence An observed failure establishes that something happened under particular conditions. Find the mechanism that explains it before changing another thing. Keep the investigation tied to the user's outcome and authorized file scope. ## Capture the failure 1. Record expected and observed behavior, exact command or user action, revision, dirty inputs, environment, relevant order or seed and evidence path. 2. Read the complete error and inspect the affected artifact and relevant diff. Missing paths, absent tools, empty test collection and permission errors may explain an unrunnable check; they do not establish successful behavior. 3. Reproduce with the smallest scope that still preserves the failure. Retain the original run: narrowing can remove order, shared state or boundary effects. 4. Register cleanup before an experiment that creates temporary resources. Use read-only inspection to answer state questions; do not reset or destroy the working tree to learn what was changed. ## Test explanations Write a small set of plausible hypotheses based on the observation. For each, …
Read the whole file at its exact version.
How to install
mdr add grit-77/done-is-a-claim/debugging-with-evidence@sha256:a699860e5a89841bThe line at the top of this page pins the label git:20261010.f887157, 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.
[](https://markdownregistry.com/a/art_hdag7v7y6fygk4vr)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 10, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4192 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
grit-77/done-is-a-claim · 33 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hdag7v7y6fygk4vr GET https://markdownregistry.com/api/v1/resolve?ref=grit-77/done-is-a-claim/debugging-with-evidence GET https://markdownregistry.com/api/v1/blob/a699860e5a89841b01bf92f3b1dcdeb3621359afa485b4aa5d7e768ccd36b963
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.