Technical Writer

Audit, rewrite, and validate developer, administrator, and operator documentation—including API/OpenAPI references—against live repository evidence. Use when these documents need proof-backed correction, reader-focused review, generated-document ownership, public-access checks, or legacy docs-expert routing; route product end-user documentation to the separate User Documentation skill.

9 stars 4 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jscraik/Agent-Skills --skill technical-writer
Manual install
git clone --depth 1 https://github.com/jscraik/Agent-Skills.git /tmp/Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Agent-Skills/Skills/agent-ops/technical-writer ~/.claude/skills/technical-writer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Technical Writer

## When To Use
- Developer, administrator, or operator READMEs, runbooks, code docs, templates, config docs, API/OpenAPI references, or trust-surface docs need audit or rewrite.
- Skill package evidence or runtime-boundary docs need proof-backed explanation.
- Claims need checks against scripts, commands, workflows, tests, repo structure, support paths, or governance docs.
- Generated, mirrored, registry, or publication docs need canonical ownership and reader-visible validation.
- Talks, articles, DevRel content, service content, visual docs, and short-form
  writing need evidence-backed technical shaping.

## Inputs
Doc target, audience, reader job, writing mode, truth files, validation commands, glossary or ubiquitous-language surfaces, and brand/governance constraints.

## Outputs
For audits and broad rewrites, return findings, claim/evidence map, ownership decisions, validation, unknowns, and handoff needs. For narrow corrections, return the corrected text or patch plus exact evidence. For editorial judgment, return verdict, central risk, revision direction, and a rewrite only when requested. Return `no_justified_edit` when documentation is not the safe owning surface.

## Execution Boundaries
Read the full skill on GitHub

Details

Skill name
technical-writer
Path
Skills/agent-ops/technical-writer/SKILL.md
License
Apache-2.0
Repo updated
16 November 2026

FAQ

What does the Technical Writer skill do?

Audit, rewrite, and validate developer, administrator, and operator documentation—including API/OpenAPI references—against live repository evidence. Use when these documents need proof-backed correction, reader-focused review, generated-document ownership, public-access checks, or legacy docs-expert routing; route product end-user documentation to the separate User Documentation skill.

How do I install the Technical Writer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jscraik/Agent-Skills --skill technical-writer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Technical Writer popular?

It lives in jscraik/Agent-Skills, which has 9 GitHub stars and 4 forks.

Related skills

1password

9

jscraik/Agent-Skills

Plan, diagnose, and validate 1Password CLI workflows. Use when tasks need op CLI sign-in, secret references, op run, op inject, item reads, env injection, or service-account secret access.

Security

Agentation

9

jscraik/Agent-Skills

Audit, validate, and troubleshoot Agentation integrations in frontend apps. Use when annotations, MCP registration, endpoint sync, webhook delivery, or watch mode readiness are failing.

AI, LLMs & Agents

Agents Md

9

jscraik/Agent-Skills

Use when reviewing, creating, shrinking, or refactoring AGENTS.md and directly linked instruction guidance for stale or conflicting rules against current model documentation, scoped routing, deduplication, or progressive disclosure.

AI, LLMs & Agents

User Documentation

9

jscraik/Agent-Skills

Create, review and validate software onboarding, task guides, UI help, FAQs and troubleshooting for non-technical end users. Use when people need to learn how to use a product or dashboard from verified interface evidence; route developer, API and administrator documentation to technical-writer.

Writing & Content

Openai Docs

9

jscraik/Agent-Skills

Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.

Writing & Content

Visual Explainer

9

jscraik/Agent-Skills

Create self-contained HTML visual explainers from technical material. Use this skill when diagrams, matrices, timelines, or browser artifacts beat plain text.

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.