This one actually asks good questions before generating boilerplate. It figures out whether you're writing for open source contributors, teammates, or future-you digging through config files, then adjusts the template accordingly. The four-step flow (identify task, ask context questions, draft, then check what's missing) is solid. Includes specific templates for OSS, personal projects, internal docs, and XDG configs. The "always ask who will read this" framing is obvious in retrospect but easy to forget when you're just trying to document something quickly. Works for creating new READMEs or updating stale ones.
npx skills add https://github.com/pedronauck/skills --skill crafting-effective-readmes