prove SKILL.md skillA

prove from nyelonong/galdr is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add nyelonong/galdr/prove@git:20261115.1faad52

Pins git:20261115.1faad52 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
nyelonong/galdr
Path
skills/prove/SKILL.md
Versions recorded
4
Latest version
git:20261115.1faad52, committed Nov 15, 2026
First version recorded
Nov 14, 2026
Size
5,579 bytes
Repository stars
13
License
MIT

Use before you change production code, before you claim that work is complete, or when you audit a document against code.

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

# prove

Every change gets a proof: a test or a check that can fail. This skill tells you how to
write the proof and when a claim of "done" is true.

## 1. Bugs, regressions and test-first requests

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST.

This rule applies to a bug fix, a regression, and a change that the user asks to be
test-first. If no failing test exists, stop. Write the test first.

1. Write one test for the next small behavior.
2. Run the test and read the failure.
   - The assertion fails for the expected reason: continue.
   - The test does not compile, or it crashes: fix the test.
   - The test passes: it proves nothing. Write it again.
3. Record `EV [<task> RED] <command> → FAIL (<reason>)`.
4. Write the smallest code that makes the test pass. Record
   `EV [<task> GREEN] <command> → PASS`.

If you wrote code for a bug before its test, delete the code. Do not keep it as a
reference. Start again from a failing test.

## 2. New behavior

1. Name the proof before you write code. The `Proof:` line of the task names the tests
   and the boundary that they use.
2. Write the tests from the requirement, not from the code. Write them before the code
…

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_m7o2vv7hnsewo7ef/f550136c8f3b970545d616f27b30fc5de28ced1b86f54a0954c72fbc8a578775.json

Then /plugin install prove@markdownregistry-m7o2vv7hnsewo7ef in Claude Code. It installs git:20261115.1faad52, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add nyelonong/galdr/prove@sha256:f550136c8f3b9705

The line at the top of this page pins the label git:20261115.1faad52, 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_m7o2vv7hnsewo7ef.svg)](https://markdownregistry.com/a/art_m7o2vv7hnsewo7ef)

0 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 nyelonong/galdr/prove 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 prove from somewhere else? Ask it: where did my prove 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 4 versions of this file, between Nov 14, 2026 and Nov 15, 2026, more than one a day.

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

versioncommittedcommitsizeaudit
git:20261115.1faad52 latest2026-11-15 1faad52 5,579 BA view · diff
git:20261114.bf8cc692026-11-14 bf8cc69 5,270 BA view · diff
git:20261114.0740ff12026-11-14 0740ff1 5,302 BA view · diff
git:20261114.fa8b3c32026-11-14 fa8b3c3 5,240 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 (5579 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

nyelonong/galdr · 13 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_m7o2vv7hnsewo7ef
GET https://markdownregistry.com/api/v1/resolve?ref=nyelonong/galdr/prove
GET https://markdownregistry.com/api/v1/blob/f550136c8f3b970545d616f27b30fc5de28ced1b86f54a0954c72fbc8a578775

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 nyelonong/galdr

debug SKILL.md skill
nyelonong/galdr · skills/debug/SKILL.md · Use when you diagnose a bug, a flaky test, unexpected behavior or a production incident, before you propose or write a…
git:20261114.fa8b3c3 · audit A · 13 stars
galdr SKILL.md skill
nyelonong/galdr · skills/galdr/SKILL.md · Use when the user runs /galdr to start or continue a piece of engineering work, or asks which galdr flow fits a request.
git:20261119.142bf5e · audit A · 13 stars
handoff SKILL.md skill
nyelonong/galdr · skills/handoff/SKILL.md · Use when the user runs /galdr:handoff to pass work to a new session, a worker or reviewer session, or the session of…
git:20261114.0740ff1 · audit A · 13 stars
review SKILL.md skill
nyelonong/galdr · skills/review/SKILL.md · Use when the user runs /galdr:review to review a branch, diff or plan document, or asks for browser approval.
git:20261115.1faad52 · audit A · 13 stars
shape SKILL.md skill
nyelonong/galdr · skills/shape/SKILL.md · Use when the user runs /galdr:shape to turn an idea, a position to test, or clear requirements into the goal and…
git:20261114.0740ff1 · audit A · 13 stars

Every file in nyelonong/galdr

Other files named prove

prove SKILL.md skill
wenlan-app/wenlan · .claude/skills/prove/SKILL.md · Per-surface verification loops for wenlan — daemon, cli, mcp, plugin, suite strength (mutation), behavior trace, weekly…
git:20261019.1b4e3ca · audit A · 498 stars
prove SKILL.md skill
7xuanlu/wenlan · .claude/skills/prove/SKILL.md · Per-surface verification loops for wenlan — daemon, cli, mcp, plugin, suite strength (mutation), behavior trace, weekly…
git:20261019.1b4e3ca · audit A · 441 stars
prove SKILL.md skill
dylan/skills · plugins/rigor/skills/prove/SKILL.md · Finds and runs the check that could show a result is wrong. It splits a finished result, claim, fix or answer into…
git:20261109.5ef7913 · audit A · 2 stars

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