Human Docs Readability
Workflow
Use this skill when editing public Markdown, especially README files, docs pages, finding packets,
PR packets, and evidence pages.
- Put the human story first: what this is, who it helps, why it matters, what to click next.
- Keep the first screen scannable: short paragraphs, callouts, compact tables, and direct links.
- Use GitHub-native components: badges, tables, task lists, blockquotes, and
<details> sections.
- Move long machine material to the bottom under:
<details><summary>LLM / Machine-readable details</summary>.
- Preserve evidence links, commands, hashes, source pins, and reproducibility material.
- Keep public links absolute when the repo's gates require shareable GitHub URLs.
- Never bury the primary share link, demo, or maintainer ask below audit internals.
Page Shape
For a README or landing page:
- H1: project or packet name.
- Badges, if already present.
- One-sentence value proposition.
> [!NOTE] or > [!TIP] callout with the best next action.- Demo or screenshot.
- Compact "Share / Open / Run" table.
- Short "How it works" narrative.
- Collapsible LLM section at the bottom for exhaustive gates, schemas, matrix details, and receipts.
For finding and PR packet pages:
- Share link in the first 10 lines.
- Human summary before the evidence list.
- "What changed", "Why it matters", and "How to verify" before raw artifacts.
- Full bundle links near the top.
- Reproduction commands and machine-readable evidence below the human summary, collapsed if lengthy.
Quality Bar
Reject docs that:
- start with implementation internals before the value proposition
- contain long uncollapsed checker, schema, matrix, or receipt inventories above the fold
- use vague link labels such as "here" for important share targets
- mix founder-facing guidance with LLM audit material in the same section
- drop evidence needed for the adversarially-confirmed to add value bar
Read references/markdown-style.md for the detailed checklist when doing a full rewrite.
1---2name: human-docs-readability3description: Human-first editing standard for README.md files and user-facing Markdown docs. Use when Codex needs to rewrite, review, or gate public docs so humans see the value story first, links are easy to scan, modern GitHub Markdown components are used tastefully, and LLM or machine-readable audit details move into bottom collapsible sections while preserving adversarially-confirmed to add value evidence.4---56# Human Docs Readability78## Workflow910Use this skill when editing public Markdown, especially README files, docs pages, finding packets,11PR packets, and evidence pages.12131. Put the human story first: what this is, who it helps, why it matters, what to click next.142. Keep the first screen scannable: short paragraphs, callouts, compact tables, and direct links.153. Use GitHub-native components: badges, tables, task lists, blockquotes, and `<details>` sections.164. Move long machine material to the bottom under:17 `<details><summary>LLM / Machine-readable details</summary>`.185. Preserve evidence links, commands, hashes, source pins, and reproducibility material.196. Keep public links absolute when the repo's gates require shareable GitHub URLs.207. Never bury the primary share link, demo, or maintainer ask below audit internals.2122## Page Shape2324For a README or landing page:2526- H1: project or packet name.27- Badges, if already present.28- One-sentence value proposition.29- `> [!NOTE]` or `> [!TIP]` callout with the best next action.30- Demo or screenshot.31- Compact "Share / Open / Run" table.32- Short "How it works" narrative.33- Collapsible LLM section at the bottom for exhaustive gates, schemas, matrix details, and receipts.3435For finding and PR packet pages:3637- Share link in the first 10 lines.38- Human summary before the evidence list.39- "What changed", "Why it matters", and "How to verify" before raw artifacts.40- Full bundle links near the top.41- Reproduction commands and machine-readable evidence below the human summary, collapsed if lengthy.4243## Quality Bar4445Reject docs that:4647- start with implementation internals before the value proposition48- contain long uncollapsed checker, schema, matrix, or receipt inventories above the fold49- use vague link labels such as "here" for important share targets50- mix founder-facing guidance with LLM audit material in the same section51- drop evidence needed for the adversarially-confirmed to add value bar5253Read `references/markdown-style.md` for the detailed checklist when doing a full rewrite.
cfregly