code-story SKILL.md skillA

code-story from will-ness-ai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add will-ness-ai/skills/code-story@git:20260820.de181a7

Pins git:20260820.de181a7 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
will-ness-ai/skills
Path
skills/code-story/SKILL.md
Versions recorded
3
Latest version
git:20260820.de181a7, committed Aug 20, 2026
First version recorded
Aug 18, 2026
Size
3,331 bytes
Repository stars
170
License
MIT

Build a wizard-style HTML page that teaches how and why a change works.

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

`/code-story <request>` — a **change** (a PR, a diff, a branch, one commit) — plus whatever the human says they do not understand.

A **code story** re-cuts a change into the **stack of PRs** it could have been. One big diff lands whole; a stack arrives one reviewable step at a time, each standing on the last. Each **chapter** is one step in that stack: it answers one question, its title *is* that question, and it pulls out a **slice** of the change (hunks) from whichever files help answer it.

The stack is the narrative. Each chapter answers its question and hands the reader the next one, so order the chapters the way the understanding has to build.

A code story explains **why** the code changed the way it did. Write it for a day-one contributor — someone who knows nothing yet about this domain, this codebase, or its architecture.

Tell it around code: each chapter is built from the lines it is about — changed, unchanged, or from a dependency — with a note pinning each claim to a line. Everything else is there to make those lines mean something.
…

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_4owtaszuykp2zuw6/ee44800a971043ff67a6e46cbcb9d9f16ab51d354b90c4f27b513b1954bdc11f.json

Then /plugin install code-story@markdownregistry-4owtaszuykp2zuw6 in Claude Code. It installs git:20260820.de181a7, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add will-ness-ai/skills/code-story@sha256:ee44800a971043ff

The line at the top of this page pins the label git:20260820.de181a7, 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_4owtaszuykp2zuw6.svg)](https://markdownregistry.com/a/art_4owtaszuykp2zuw6)

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 will-ness-ai/skills/code-story 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 code-story from somewhere else? Ask it: where did my code-story 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 3 versions of this file, between Aug 18, 2026 and Aug 20, 2026, more than one a day.

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

versioncommittedcommitsizeaudit
git:20260820.de181a7 latest2026-08-20 de181a7 3,331 BA view · diff
git:20260819.75b2f192026-08-19 75b2f19 2,504 BA view · diff
git:20260818.e84c8b82026-08-18 e84c8b8 1,737 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 (3331 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

will-ness-ai/skills · 170 stars · license MIT · pushed 2026-11-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_4owtaszuykp2zuw6
GET https://markdownregistry.com/api/v1/resolve?ref=will-ness-ai/skills/code-story
GET https://markdownregistry.com/api/v1/blob/ee44800a971043ff67a6e46cbcb9d9f16ab51d354b90c4f27b513b1954bdc11f

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 will-ness-ai/skills

AGENTS.md AGENTS.md file
will-ness-ai/skills · AGENTS.md
git:20260713.697d4ce · audit B · 170 stars
CLAUDE.md CLAUDE.md file
will-ness-ai/skills · CLAUDE.md
git:20260813.511a5eb · audit A · 170 stars
agent-tools SKILL.md skill
will-ness-ai/skills · skills/agent-tools/SKILL.md · Build commands for agents in AXI style. Use when writing or changing a script or CLI whose reader is an agent, or when…
git:20261018.d5f6219 · audit A · 170 stars
cmux SKILL.md skill
will-ness-ai/skills · skills/cmux/SKILL.md · Drive the local cmux app — workspaces, panes, surfaces, terminal input, agent sessions, and browser surfaces.
git:20260811.446635a · audit A · 170 stars
development-workflow SKILL.md skill
will-ness-ai/skills · skills/development-workflow/SKILL.md · Take a task from idea to merged PR through my development workflow — research, alignment, proof, spec, tickets…
git:20261115.cba339b · audit A · 170 stars
grilling-frontend-prototyping SKILL.md skill
will-ness-ai/skills · skills/engineering/grilling-frontend-prototyping/SKILL.md
git:20260811.cf8c130 · audit C · 170 stars
find-standards SKILL.md skill
will-ness-ai/skills · skills/find-standards/SKILL.md · Find how this problem is already solved: standards we could adopt, and the industry's best practices.
git:20260817.d31b391 · audit A · 170 stars
flashlight SKILL.md skill
will-ness-ai/skills · skills/flashlight/SKILL.md · Shine a light into a wayfinder map's fog — work one direction now, out of frontier order, or redraw the map itself.
git:20260811.b42be37 · audit A · 170 stars
grill-design SKILL.md skill
will-ness-ai/skills · skills/grill-design/SKILL.md · Converge on a frontend look through rounds of prototypes and grilling verdicts. Use when the user wants to iterate on…
git:20260811.b42be37 · audit A · 170 stars
sandcastle SKILL.md skill
will-ness-ai/skills · skills/sandcastle/SKILL.md · Run a Sandcastle lane — a sandboxed implement→review loop over a fixed batch of work in its own worktree, ended by an…
git:20260811.e2d5215 · audit A · 170 stars
test-a-skill SKILL.md skill
will-ness-ai/skills · skills/test-a-skill/SKILL.md · Field-test a skill by running it cold in parallel agent sessions, then turn what they hit into edits.
git:20260819.f70e64b · audit A · 170 stars

Every file in will-ness-ai/skills

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