technical-manual SKILL.md skillB
technical-manual from markphelps/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add markphelps/skills/technical-manual@git:20261009.3fd5f7cPins git:20261009.3fd5f7c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- markphelps/skills
- Path
development/skills/technical-manual/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261009.3fd5f7c, committed Oct 9, 2026
- First version recorded
- Oct 9, 2026
- Size
- 23,001 bytes
- Repository stars
- 6
- License
- MIT
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
# Technical manual You are writing a reference book an engineer keeps open while writing a parser, debugging a crash, or deciding how to configure a writer. It runs from the first idea down to the exact bytes or stored rows. The method has one rule: > **Nothing is written from memory. Every claim traces to a pinned source or a > captured artefact, and every figure is drawn from that same data.** What that produces: - **Pinned, ranked evidence.** One subject at one commit. Code outranks the spec; where they disagree, the book says so. - **The real thing on the page.** Real hex, real headers, real stored records, cut from captures and decoded by hand, then checked against the reference implementation. - **Figures as data.** Byte strips, hex walks, sequence diagrams and bar charts generated from captures, about one every two pages, in one colour code that holds for the whole book. - **Plain, exact prose.** Short declarative sentences with numbers and names in them, and a Sources line closing every section. The output is a Letter-size PDF in a fixed house style (cream paper, dark part openers, Manrope / Source Sans 3 / Source Serif 4 italic / JetBrains Mono), …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3hmllh5nieycger7/65f04030649027a6f0b21ca33567ef99a91bf37658179f8003eaa034bf74d942.json
Then /plugin install technical-manual@markdownregistry-3hmllh5nieycger7 in Claude Code. It installs git:20261009.3fd5f7c, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add markphelps/skills/technical-manual@sha256:65f04030649027a6The line at the top of this page pins the label git:20261009.3fd5f7c, 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_3hmllh5nieycger7)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in markphelps/skills/technical-manual 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 technical-manual from somewhere else? Ask it: where did my technical-manual 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 2 versions of this file, all committed on Oct 9, 2026.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261009.3fd5f7c latest | 2026-10-09 | 3fd5f7c | 23,001 B | B | view · diff |
| git:20261009.3f8a7ae | 2026-10-09 | 3f8a7ae | 21,433 B | B | view |
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.
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.
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.
Installed this file, say at .claude/skills/technical-manual/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- fail: Frontmatter declares a description
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Size between 200 bytes and 200 KB (23001 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
markphelps/skills · 6 stars · license MIT · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3hmllh5nieycger7 GET https://markdownregistry.com/api/v1/resolve?ref=markphelps/skills/technical-manual GET https://markdownregistry.com/api/v1/blob/65f04030649027a6f0b21ca33567ef99a91bf37658179f8003eaa034bf74d942
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.