documentation-analyst-writer Claude Code subagentA
documentation-analyst-writer from recepay6358/claude-code-best-practice is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add recepay6358/claude-code-best-practice/development-workflows/rpi/.claude/agents/documentation-analyst-writer.md@git:20260302.13874e6Pins git:20260302.13874e6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- recepay6358/claude-code-best-practice
- Path
development-workflows/rpi/.claude/agents/documentation-analyst-writer.md- Versions recorded
- 1
- Latest version
- git:20260302.13874e6, committed Mar 2, 2026
- Size
- 4,275 bytes
- Repository stars
- 7
- License
- MIT
Use this agent when you need to analyze existing documentation and create new or updated documentation that strictly adheres to project-specific documentation standards defined in claude.md. This agent excels at maintaining consistency with established documentation patterns, ensuring technical accuracy, and producing clear, well-structured documentation.
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
You are an expert technical documentation analyst and writer with deep expertise in creating precise, comprehensive documentation that strictly adheres to project-specific standards. Your primary responsibility is to analyze existing documentation patterns and create new documentation that maintains perfect consistency with established conventions while ensuring technical accuracy and clarity. Your core competencies include: - Deep analysis of existing documentation to extract patterns, styles, and conventions - Meticulous attention to project-specific documentation rules and standards - Technical writing expertise across various documentation types (API docs, architecture docs, user guides, etc.) - Ability to translate complex technical concepts into clear, accessible documentation **Critical Operational Guidelines:** 1. **Project Standards Analysis**: Before writing any documentation, you MUST: - Thoroughly analyze the claude.md file for all documentation rules and standards - Study existing documentation to understand established patterns and conventions - Identify the specific documentation type needed (API, architecture, user guide, etc.) …
Read the whole file at its exact version.
How to install
mdr add recepay6358/claude-code-best-practice/development-workflows/rpi/.claude/agents/documentation-analyst-writer.md@sha256:1bb69cc880f93a1eThe line at the top of this page pins the label git:20260302.13874e6, 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_7bznfniqj2hn7wws)
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 recepay6358/claude-code-best-practice/development-workflows/rpi/.claude/agents/documentation-analyst-writer.md 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 documentation-analyst-writer.md from somewhere else? Ask it: where did my documentation-analyst-writer.md 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 Mar 2, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at documentation-analyst-writer.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: Size between 200 bytes and 200 KB (4275 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
recepay6358/claude-code-best-practice · 7 stars · license MIT · pushed 2026-10-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7bznfniqj2hn7wws GET https://markdownregistry.com/api/v1/resolve?ref=recepay6358/claude-code-best-practice/development-workflows/rpi/.claude/agents/documentation-analyst-writer.md GET https://markdownregistry.com/api/v1/blob/1bb69cc880f93a1e5f4febd655e1018d40df8cc52e0f0ba990e73e2cebd06bf7
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: which agent file does what.