implement-guide SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
implement-guide from nexuslabs-ai/nxds is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nexuslabs-ai/nxds/implement-guide@git:20260922.15c901bPins git:20260922.15c901b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nexuslabs-ai/nxds
- Path
.claude/skills/implement-guide/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260922.15c901b, committed Sep 22, 2026
- First version recorded
- Jul 10, 2026
- Size
- 18,218 bytes
- Repository stars
- 4
- License
- MIT
Draft a plan, stress-test it with a parallel review council, then implement in the main session. Only plan review is delegated; drafting and implementation stay single-agent.
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
# Implement Guide
## Purpose
Plan and implement features in the main session. You draft the plan and do all implementation yourself; the one delegated step is a parallel review council that stress-tests the draft plan against the codebase before you finalize it. Implementation is never delegated.
## Rules
The full ruleset lives in `.claude/rules/*.md` — those files are the spec. Don't try to keep all of them in working memory.
The **Reflex Check** in Part 2 → Step 3 names the actions that should evoke a rule mid-write and points at the relevant file. Read the Reflex Check at the start of every phase; open a full rule file only when a reflex actually fires while you're writing.
Operational rules (`docs-mcp.md`, `github.md`, `project-stage.md`) are referenced inline by the step they govern.
## Part 1: Planning
### Step 1: Understand Requirements
1. **If a GitHub issue is referenced:**
```bash
gh issue view {number} --json number,title,body,labels,state,url
```
2. **Extract key information:**
- What problem is being solved?
- What are the acceptance criteria?
- Any constraints or requirements?
- Linked designs or references?
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_sfufixrh5nu2op4u/82a4fd2282f5106cdd7a350d3990c04558fe504cc0b0652d362b038f7f5b34fc.json
Then /plugin install implement-guide@markdownregistry-sfufixrh5nu2op4u in Claude Code. It installs git:20260922.15c901b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add nexuslabs-ai/nxds/implement-guide@sha256:82a4fd2282f5106cThe line at the top of this page pins the label git:20260922.15c901b, 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_sfufixrh5nu2op4u)
2 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 nexuslabs-ai/nxds/implement-guide 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 implement-guide from somewhere else? Ask it: where did my implement-guide 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 5 versions of this file, between Jul 10, 2026 and Sep 22, 2026, about one every 19 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.15c901b latest | 2026-09-22 | 15c901b | 18,218 B | A | view · diff |
| git:20260922.b97f07b | 2026-09-22 | b97f07b | 17,569 B | A | view · diff |
| git:20260922.230cff5 | 2026-09-22 | 230cff5 | 17,496 B | A | view · diff |
| git:20260921.48f0bc6 | 2026-09-21 | 48f0bc6 | 17,367 B | A | view · diff |
| git:20260710.7690c4a | 2026-07-10 | 7690c4a | 17,426 B | A | 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/implement-guide/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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (18218 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
nexuslabs-ai/nxds · 4 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sfufixrh5nu2op4u GET https://markdownregistry.com/api/v1/resolve?ref=nexuslabs-ai/nxds/implement-guide GET https://markdownregistry.com/api/v1/blob/82a4fd2282f5106cdd7a350d3990c04558fe504cc0b0652d362b038f7f5b34fc
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 nexuslabs-ai/nxds
Every file in nexuslabs-ai/nxds