Build and review high-quality technical docs as well as agent instruction files in your repository.
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 Documentation
## Purpose
Produce and review technical documentation that is clear, actionable, and maintainable for both humans and agents, including contributor-governance files and agent instruction files.
## When to use
- Creating or overhauling docs in an existing product/codebase (brownfield).
- Building evergreen docs meant to stay accurate and reusable over time.
- Reviewing doc diffs for structure, clarity, and operational correctness.
- Running full-repo documentation audits that must include both governance files and product docs surfaces (`docs/`, `README*`, `.md/.mdx/.mdc`, Fern/Sphinx/Mintlify-style sources).
- Updating or reviewing AGENTS.md and/or CONTRIBUTING.md to keep agent and contributor workflows aligned with current repo practices.
- Improving repository onboarding/docs that include contribution instructions, issue templates, PR flow, and review gates.
…
The line at the top of this page pins the label git:20260617.3a46cdd, 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.
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 (5828 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
openclaw/clawhub · 9,544 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lap4qpgoinafsemv
GET https://markdownregistry.com/api/v1/resolve?ref=openclaw/clawhub/technical-documentation
GET https://markdownregistry.com/api/v1/blob/67a93dc4b2263d23de63d6d3e6fca6447f4f594fe856c1514db79d94b65d3c5a
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.
openclaw/clawhub · .agents/skills/axiom-alerting/SKILL.md · Create and manage Axiom monitors and notifiers via the v2 public API. Use when building alerting, routing…
openclaw/clawhub · .agents/skills/clawhub-content-rights-correspondence/SKILL.md · Use when drafting, sending, or preserving email correspondence for an existing ClawHub content rights case.
openclaw/clawhub · .agents/skills/clawhub-convex/SKILL.md · Apply ClawHub-specific Convex conventions and route to the right managed Convex skill. Use for any change under…
openclaw/clawhub · .agents/skills/clawhub-pr-maintainer/SKILL.md · Use when reviewing, triaging, validating, or discussing ClawHub GitHub issues or pull requests, including author…
openclaw/clawhub · .agents/skills/clawhub-production-release/SKILL.md · Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend…
magnus919/agent-skills · technical-documentation/SKILL.md · Create and review technical documentation, including READMEs, agent-facing instructions, API references, and CLI help…
djarvur/go-ultimate · skills/technical-documentation/SKILL.md · Build and review high-quality technical docs as well as agent instruction files in your repository.
jpeetz/agent-skills · skills/documentation-content/technical-documentation/SKILL.md · Use this skill when creating, maintaining, or auditing technical documentation — READMEs, ADRs, API docs, runbooks…
