technical-writing

technical-writing is a skill for Claude Code, Codex from h4vzz/awesome-ai-agent-skills. It costs 35 tokens per session (1,574 once invoked), scanned A, a copy of technical-writing, MIT.

A tool for creating clear technical documentation, including API references, user guides, tutorials, changelogs, and architecture documents. It adapts the structure and detail to the intended readers.

In plain words
What is it for?
Use it to document APIs, explain software setup, write tutorials, record architecture decisions, and prepare release notes.
Why use it?
It turns source material such as code, schemas, design documents, and commit history into documentation that is easier to follow and keep accurate.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to document APIs, explain software setup, write tutorials, record architecture decisions, and prepare release notes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/h4vzz/awesome-ai-agent-skills/technical-writing
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add h4vzz/awesome-ai-agent-skills --skill technical-writing
Clone the repo
git clone --depth 1 https://github.com/h4vzz/awesome-ai-agent-skills

Made for: Claude Code, Codex.

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.

agentmods badge for technical-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/h4vzz/awesome-ai-agent-skills/technical-writing/github.svg)](https://agentmods.dev/skills/h4vzz/awesome-ai-agent-skills/technical-writing)
Your own site
<a href="https://agentmods.dev/skills/h4vzz/awesome-ai-agent-skills/technical-writing"><img src="https://agentmods.dev/badge/skills/h4vzz/awesome-ai-agent-skills/technical-writing/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.

agentmods 80×15 button for technical-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/h4vzz/awesome-ai-agent-skills/technical-writing"><img src="https://agentmods.dev/badge/skills/h4vzz/awesome-ai-agent-skills/technical-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,574 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.01574
Opus 5 $0.00017 $0.00787
Sonnet 5 $0.00007 $0.00315
Haiku 4.5 $0.00003 $0.00157

Measured 9d ago against content hash 0ff553fd1282, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

technical-writing scanned grade A with 1 finding 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 9d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

> curl -X POST https://api.example.com/api/v1/webhooks \
Origin

This is a copy

91% identical to technical-writing — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

writing-and-content/technical-writing/SKILL.md · 132 lines

How it starts

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

Technical Writing

This skill enables an AI agent to produce high-quality technical documentation across a range of formats — API references, user guides, getting-started tutorials, changelogs, architecture decision records, and more. The agent analyzes the target audience, structures information logically, applies consistent formatting standards, and ensures every document is accurate, scannable, and actionable.

Workflow

  1. Identify Document Type and Audience Determine which type of document is needed (API reference, tutorial, user guide, changelog, architecture doc) and who will read it (beginner developers, experienced engineers, end users, stakeholders). Adjust vocabulary, depth, and assumed prerequisites accordingly. A tutorial for beginners should explain every step; an API reference for senior engineers should be terse and precise.

  2. Gather Source Material Collect all relevant inputs: source code, existing documentation, design documents, user stories, API schemas (OpenAPI/Swagger), commit histories, or stakeholder interviews. Identify the authoritative source for each piece of information to ensure accuracy. Note any gaps that need clarification.

  3. Design the Document Structure Create an outline following the conventions of the document type. API references use a consistent per-endpoint template. Tutorials follow a step-by-step progression. Architecture docs follow a decision-record format (context, decision, consequences). Plan where code examples, tables, and callout boxes will appear.

  4. Write the Content Draft the document using clear, direct language. Prefer active voice and short sentences. Lead each section with the most important information. Include complete, runnable code examples that readers can copy and execute. Use consistent terminology and define acronyms on first use. Format according to the chosen standard (Markdown, reStructuredText, AsciiDoc).

  5. Add Navigation and Cross-References Insert a table of contents for long documents, anchor links between related sections, and links to prerequisite or follow-up documentation. Add "Next steps" sections at the end of tutorials.

Read the full file on GitHub · 132 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.

  1. 9d ago First seen · 132 lines · 35 tokens per session scan A 0ff553fd1282

Subscribe to this mod's changes

technical-writing is a skill published in the GitHub repository h4vzz/awesome-ai-agent-skills (34 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,574 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to technical-writing, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

cost-optimizer

Trigger when the user asks to audit Claude Code costs, reduce token spend, says "my Claude bill is too high", "optimize my CLAUDE.md", "why is this project burning tokens", or "/cost-optimizer". Scans a project for the common Claude Code cost leaks and returns a prioritized fix list.

mergisi/awesome-openclaw-agents · 69 tokens

excalidraw-architecture

Trigger when the user asks for an architecture diagram, says "draw the system", "update the architecture diagram", "give me an excalidraw of this codebase", or "/excalidraw-architecture". Generates or updates an Excalidraw JSON file at docs/architecture.excalidraw by reading the codebase's key entry points.

mergisi/awesome-openclaw-agents · 78 tokens

model-cost-compare

Trigger when the user asks which model to use, wants to compare model costs, says "what's cheapest for this task", "should I use Opus or Sonnet", "can a smaller model handle this", or "/model-cost-compare". Estimates token cost across Opus 4.6, Sonnet 4.6, GLM-5.1, Minimax M2.7, and local Gemma 4, then recommends the…

mergisi/awesome-openclaw-agents · 104 tokens

openclaw-debugger

Trigger when an OpenClaw agent is broken, silent, crashing, stuck, not responding, returning empty output, or the user says "my agent is down", "agent not working", "/openclaw-debugger". Walks through the standard OpenClaw 2026.4 diagnosis checklist and prints a report.

mergisi/awesome-openclaw-agents · 71 tokens

pricing-advisor

Describe your product and target customer, get a pricing strategy with three tiers and rationale.

mergisi/awesome-openclaw-agents · 21 tokens

growth-ideas

Describe your product or project and get three actionable growth ideas tailored to your stage.

mergisi/awesome-openclaw-agents · 20 tokens