show-your-work SKILL.md skillA
show-your-work from dheerajjha/show-your-work is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dheerajjha/show-your-work/show-your-work@git:20261009.c3a52edPins git:20261009.c3a52ed in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dheerajjha/show-your-work
- Path
skills/show-your-work/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261009.c3a52ed, committed Oct 9, 2026
- Size
- 3,491 bytes
- Repository stars
- 4
- License
- MIT
Use before telling the user that work is done, a bug is fixed, tests pass, the build succeeds or something works. Back each claim with the command you ran after your last edit and the output line that proves it, keep exit statuses honest, and say plainly what you did not check.
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
# Show your work The user cannot see your terminal. When you say "done", your word is all they get, so show the work behind it. **No claim without the check that backs it.** The evidence for a claim is a command you ran **after your last edit**, plus the line of its output that shows the result. | You want to say | Show | |---|---| | "tests pass" | the test command, and its summary line: `Tests: 212 passed, 212 total` | | "it builds", "no type errors" | the build or type-check command, and its last line | | "it works", "fixed" | the command that exercises the change (a test, a request, running the script) and what it printed | | "I ran the tests" | that command, in this session, after your last edit | ## Before you claim anything 1. **Edited since your last run? Run it again.** Output from before your last edit describes code that no longer exists. 2. **Run the project's whole check.** Find it in package.json scripts, the Makefile, the CI workflow or CONTRIBUTING. Do not run one test file and report it as "the tests". If you ran only part, say which part. 3. **Keep the exit status.** `npm test | tail -20` exits 0 even when tests fail, …
Read the whole file at its exact version.
How to install
mdr add dheerajjha/show-your-work/show-your-work@sha256:099142fd2942e3ebThe line at the top of this page pins the label git:20261009.c3a52ed, 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_hssdp37capsykwej)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 9, 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 (3491 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
dheerajjha/show-your-work · 4 stars · license MIT · pushed 2026-10-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hssdp37capsykwej GET https://markdownregistry.com/api/v1/resolve?ref=dheerajjha/show-your-work/show-your-work GET https://markdownregistry.com/api/v1/blob/099142fd2942e3eb19f4ef91e8b2b8db3a6c1cf90d4e61a3a12116b2e899bbcd
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.