audience-check
Installation
SKILL.md
Re-read the README — or whichever front-door doc the user names — as several different readers in turn, not as the author. The author knows what every line means; a first-time reader does not. The job is to surface where a specific audience gets confused, under-served, or bounces, and to propose concrete fixes.
This is an INTERNAL dev skill (not shipped to consumers). It complements the
readme-brevity and docs-quality rules: those govern length/polish; this checks
whether the content actually lands for who it's for.
How to run it
- Read the target doc in full (default:
README.md; honor a path the user gives). Also skim the docs it links to, so "the README promises depth the doc doesn't deliver" is checkable. - For each persona below, do a cold read — adopt that reader's goals, vocabulary, and patience. Ask their questions, not yours.
- Produce the report in the format at the end. Be specific: quote the exact line, name the exact fix. Vague notes ("could be clearer") are useless.