readme-author

Produces READMEs that work as a landing page: a visitor should know what this is, why they should care, and how to try it within the first screen. Default model output fails at this in predictable ways — verbose prose walls, badge spam, marketing hype, invented install commands — and this skill exists to prevent exactly those failures.

When NOT to use

• Repo description, topics, social preview, search visibility → repo-discoverability.
• CONTRIBUTING/SECURITY/SUPPORT and other community files → community-health.
• Personal profile READMEs (github.com/user/user) → out of scope; keep those to a single screen and decline politely.
• Documentation sets and docs sites (tutorials, guides, API reference) → docs-author for the content, docs-site for the GitHub Pages pipeline.

Workflow