How I built a practical agent skill that turns rough READMEs into polished project docs

If you're new to agent skills, start with my beginner guide first: What Are Agent Skills? Beginners Guide That post covers what skills are, how they get loaded, and how to build a tiny one from scratch. This post picks up where that one stops. Instead of another tiny example, I want to show you what a practical skill looks like when it solves a real problem. We are going to take the idea of a skill and use it to turn rough project READMEs into polished docs that are consistent, accurate, and reusable across repos. I picked README generation because the output is easy to judge, it comes up again and again, and once you get it right for one project you want the same quality bar everywhere. The problem with one-off README prompts You can absolutely ask an agent to improve your README and get something decent back. Sometimes it will even be very good. But if you do that across multiple projects, the cracks show up quickly: badge styles are inconsistent section order changes from repo to re