Writing & Docs skills for Codex
Skills for words that do a job: technical writing, READMEs that get people running, API references, docs-as-code sites, Diataxis structure, runbooks, release notes, postmortems, proposals, error messages and CLI help text, plus copy editing and plain-language rewrites.
curl -fsSL codexskills.dev/install.sh | sh -s -- --category writing Installs all 25 into ~/.agents/skills/. Or download the zip.
All 25 Writing & Docs skills
Each opens the full SKILL.md, example prompts and every way to install it.
-
Academic Writing
One clear contribution, every claim backed -
API Documentation
Reference from the spec, guides from real calls -
Engineering Blog Posts
One idea, real evidence, nothing confidential -
Changelog to Announcement
From commit-speak to a launch people care about -
CLI Help Text
A --help screen users can copy from -
Copy Editing
Tighter text that still sounds like the author -
Diataxis Docs
One page, one reader need -
Docs as Code
Docs that ship in the same PR as the code -
Docstrings and Doc Comments
Document the contract, not the signature -
Documentation Audit
Find the wrong docs before the broken links -
Error Messages
What happened, why, and what to do next -
Ghostwriting Voice
Sound like the author, from their own samples -
Grant Writing
Compliant, reviewer-ready proposals you still author -
Localization Workflow
Strings in, translations back, no broken placeholders -
Meeting Notes
Decisions and owners first, no invented commitments -
Plain Language
Understood on the first read by anyone -
Postmortem Writing
Outage write-ups that change something -
Professional Email
The ask in line one, the right tone, nothing sent unseen -
Proposal Writing
Business cases a busy executive can approve -
README Writing
From repo page to first result in five minutes -
Release Notes
Say what changed for the user, breaking first -
Runbooks
Procedures a tired on-call engineer can follow -
Style Guide Creation
A short house style that a linter enforces -
Technical Writing
Lead with the answer, prove every claim -
Tutorial Writing
Tutorials tested from a clean machine, step by step
No Writing & Docs skill matches that.
Where to start
Install the ones that match requests you make every week. Name one with $ghostwriting-voice when you want it for sure; otherwise Codex picks by description.
Start with
- Ghostwriting VoiceSound like the author, from their own samples
- README WritingFrom repo page to first result in five minutes
- Academic WritingOne clear contribution, every claim backed
Install a few by name
curl -fsSL codexskills.dev/install.sh | sh -s -- academic-writing api-documentation 104-line POSIX script. No sudo, no telemetry. Read install.sh
Writing & Docs FAQ
How do I install every Writing & Docs skill at once?
Run curl -fsSL https://codexskills.dev/install.sh | sh -s -- --category writing to put all 25 in ~/.agents/skills/, or add --project to install them into the current repository's .agents/skills/. You can also download the category zip and unpack it yourself.
Does installing 25 skills slow Codex down?
Hardly. At startup Codex sees only each skill's name and description, a few dozen words apiece, and reads a full SKILL.md only when a task needs it. Install the whole category if the work fits; unused skills cost almost nothing.
Which Writing & Docs skill should I start with?
Start with Ghostwriting Voice, README Writing, Academic Writing. They cover the requests that come up most in this category. Mention one with $ghostwriting-voice to try it.