This one cuts through the usual README confusion by starting with a simple question: who's going to read this? It walks you through identifying whether you're creating, adding, updating, or reviewing, then matches templates to project type. Open source gets the full contributor treatment, personal projects focus on what you learned, config folders get a "future you will be confused" structure. The step three follow-up asking what you might have missed is smart. Saves you from both the sparse two-liner and the kitchen sink approach where you document everything except what actually matters.
npx skills add https://github.com/softaworks/agent-toolkit --skill crafting-effective-readmes