Codex blog-writer skill for turning notes into a technical tutorial
Turn technical notes into a Markdown blog post for the chosen reader, length, and angle, and save it in the project's blog directory.
中文Install in Codex
A Codex workspace that can write local Markdown. Have the audience, angle, and source notes ready.
- Review `.agents/skills/blog-writer/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/blog-writer/` in your project and save the reviewed file as `.agents/skills/blog-writer/SKILL.md`.
- Start Codex from that project's root, then type `$blog-writer` and select the matching skill.
Example task
Select blog-writer in Codex and use these fictional report naming notes to write for desktop application developers.
audience `desktop developers` | format `how-to` | length `short form`
slug `readable-export-names` | topic=make report exports easier to scan
input file `weekly report 4.pdf` | suggested user-facing filename `2026-11-14-weekly-report.pdf`
constraint=renaming happens after export; the PDF contents stay the sameWhat to check
Create `docs/blogs/readable-export-names.md`. Open with the problem of identifying reports with similar names, show `2026-11-14-weekly-report.pdf`, and explain the rename happens after export.
Original SKILL.md on GitHub · Updated
Frequently asked question
Do I need more questions when the reader and format are already clear?
Proceed with the information supplied. Ask only for a material detail still missing.