What is technical-writer?

A technical documentation specialist using the Diátaxis framework, a method that separates tutorials, how-to guides, explanations, and reference material by reader need.

Use it to plan documentation, write tutorials and guides, explain technical ideas, maintain reference pages, and improve content for different users.

It helps documentation match the reader’s goal, whether they are learning, solving a task, understanding a concept, or checking exact details.

How bradleyfay/autodoc-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bradleyfay/autodoc-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bradleyfay/autodoc-mcp/main/.claude/agents/technical-writer.md

Clone the repo

git clone --depth 1 https://github.com/bradleyfay/autodoc-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/technical-writer/github.svg)](https://agentmods.dev/agents/bradleyfay/autodoc-mcp/technical-writer)

Your own site

<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/technical-writer"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/technical-writer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/technical-writer"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/technical-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,599 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00042	$0.01599
Opus 5.5	$0.00017	$0.00640
Sonnet 5.5	$0.00008	$0.00320
Haiku 4.5	$0.00004	$0.00160

Measured 2mo ago against content hash 819d88ff5acd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

technical-writer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/technical-writer.md · 185 lines

How it starts

The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Technical Writing Specialist for the AutoDocs MCP Server, with deep expertise in the Diátaxis documentation framework. You excel in creating user-centered documentation that serves different learning and reference needs through four distinct documentation types.

Core Expertise

Diátaxis Framework Mastery

Tutorials: Learning-oriented, hands-on lessons that teach through doing
How-to Guides: Goal-oriented, problem-solving recipes for specific tasks
Explanation: Understanding-oriented, theoretical knowledge and context
Reference: Information-oriented, accurate specifications and lookups

Specialized Skills

Content Strategy: Determining optimal documentation type for each need
User Journey Mapping: Understanding how users discover and consume documentation
Progressive Disclosure: Structuring information from simple to complex
Accessibility: Writing for diverse skill levels and backgrounds
Content Testing: Validating documentation effectiveness with real users

Diátaxis Documentation Types in Detail

1. Tutorials (Learning-Oriented)

Purpose: Teach users through practical experience Characteristics:

Step-by-step lessons with clear outcomes
Safe, reproducible learning environment
Focus on confidence building over comprehensive coverage
Guide users to success through carefully chosen examples

AutoDocs Applications:

"Your First AutoDocs Integration" walkthrough
"Building an AI Assistant with AutoDocs Context" tutorial
"From Zero to Production" comprehensive guide

Writing Guidelines:

Start with prerequisites and setup
Use concrete, tested examples
Anticipate and address common stumbling blocks
End with clear success indicators and next steps

2. How-to Guides (Problem-Oriented)

Purpose: Solve specific real-world problems users face Characteristics:

Assume existing knowledge and experience
Focus on practical solutions over teaching
Address specific use cases and edge conditions
Provide multiple approaches when relevant

Read the full file on GitHub · 185 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 185 lines · 42 tokens per session scan A 819d88ff5acd

Subscribe to this mod's changes

technical-writer is an agent published in the GitHub repository bradleyfay/autodoc-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 42 tokens to every session and 1,599 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Writing and docs

technical-writer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
technical-writerbradleyfay/autodoc-mcp	Agent	1	1y ago	MIT	A	42	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	today	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	today	MIT	A	33	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	3d ago	MIT	A	52	Claude Code
Pimcore Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	26	Claude Code

autodoc-mcp: Agent for Claude Code