create-rule SKILL.md skillA
create-rule from codelytv/agent-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add codelytv/agent-harness/create-rule@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- codelytv/agent-harness
- Path
.agents/skills/create-rule/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Nov 17, 2026
- Size
- 7,319 bytes
- Repository stars
- 319
- License
- none declared
Turn one new convention into a deterministic rule (linter config, custom lint rule or test) that fails in seconds. When no rule can check it exactly, write a minimal doc with the reason instead. Use after the user corrects you on a convention, or when they describe one to enforce.
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
# Create rule A written convention holds only if an agent loads it, reads it the way the team does, and a reviewer catches the miss. A **rule** fails in seconds and tells the agent what to do instead, so the agent corrects itself. This skill takes one convention and makes it a rule when it can. When it cannot, it documents the convention in a few lines, with the reason no rule checks it. To enforce the conventions that a repository already has, use `deterministify` instead. ## Arguments `/create-rule [convention]` - **Without arguments:** take the convention from the conversation: what the user corrected you on, and your version before the correction. - **With a description:** take the convention from it and from the code. ## Principles - **Exact or document.** Write a rule when it covers the whole convention and reports only real violations. The effort to write the rule is no reason to skip it. A rule that has to guess (which class is an aggregate, which file is an entrypoint) is: document the convention instead. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_rzyyu6iw3yncvjo4/5bd3af91f76cac0695c3b7fd1dd7752362e6d536e7e4a750cccbd61c1f3413ee.json
Then /plugin install create-rule@markdownregistry-rzyyu6iw3yncvjo4 in Claude Code. It installs v1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add codelytv/agent-harness/create-rule@sha256:5bd3af91f76cac06The line at the top of this page pins the label v1.0, 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_rzyyu6iw3yncvjo4)
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 codelytv/agent-harness/create-rule 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 create-rule from somewhere else? Ask it: where did my create-rule 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 1 version of this file, committed on Nov 17, 2026.
Watch this file (sign in, one email per new version)
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/create-rule/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 (7319 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
codelytv/agent-harness · 319 stars · license none declared · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rzyyu6iw3yncvjo4 GET https://markdownregistry.com/api/v1/resolve?ref=codelytv/agent-harness/create-rule GET https://markdownregistry.com/api/v1/blob/5bd3af91f76cac0695c3b7fd1dd7752362e6d536e7e4a750cccbd61c1f3413ee
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 codelytv/agent-harness
Every file in codelytv/agent-harness
Other files named create-rule
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.