sw-verify SKILL.md skillA
sw-verify from mhmtsrfglu/superwiki is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mhmtsrfglu/superwiki/sw-verify@git:20261031.2a014e1Pins git:20261031.2a014e1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mhmtsrfglu/superwiki
- Path
skills/sw-verify/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261031.2a014e1, committed Oct 31, 2026
- First version recorded
- Oct 8, 2026
- Size
- 17,635 bytes
- Repository stars
- 30
- License
- MIT
Use when a Superwiki task's work is finished and it has to be closed with evidence, when the user asks what a task did, what it changed or how it was verified, or invokes sw-verify with a task id. sw-implement runs it as the gate before `done`.
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
# sw-verify Closes a task with a `## Summary` section in its task file: what was planned, what was built, what changed, and the evidence for each "Done when" item. `status: done` then means verified, and the task file says how. One rule carries the skill: **no verdict without a command run in this session.** Name the command that proves the item, run it now, read its exit code and its output, then write the verdict. An earlier run, the implementer's report, a passing test you remember, or "should pass" is not evidence. A second rule goes with it: **the command must be one that could have come out the other way.** For each item, say how its command would have failed if the item did not hold. A command that passes whatever the code does proves nothing. It runs in the session that invokes it: by hand as `sw-verify <ID>`, or as a step of sw-implement. It is not handed to the implementer; the one who did the work does not also sign it off. Run commands from the project root. ## Steps …
Read the whole file at its exact version.
How to install
mdr add mhmtsrfglu/superwiki/sw-verify@sha256:2c909b1f855f1f80The line at the top of this page pins the label git:20261031.2a014e1, 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_t7ybfmf35elhq5qf)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 8, 2026 and Oct 31, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261031.2a014e1 latest | 2026-10-31 | 2a014e1 | 17,635 B | A | view · diff |
| git:20261015.9415b7c | 2026-10-15 | 9415b7c | 14,653 B | A | view · diff |
| git:20261008.42c6752 | 2026-10-08 | 42c6752 | 14,597 B | A | view |
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 (17635 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
mhmtsrfglu/superwiki · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t7ybfmf35elhq5qf GET https://markdownregistry.com/api/v1/resolve?ref=mhmtsrfglu/superwiki/sw-verify GET https://markdownregistry.com/api/v1/blob/2c909b1f855f1f80a50c956c64ecb7f99f60da5f59ce908b657b1924a15cdd9c
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.