A repo visitor decides in about ten seconds whether your project solves their problem — and most READMEs spend those ten seconds on installation instructions instead of answering 'what does this actually do and why should I use it instead of the five alternatives I already know about.' This skill writes the README that converts visitors into users: the lead that explains the problem solved in one sentence, the quick demo that shows the thing working before asking for any setup investment, the honest comparison to alternatives that builds trust instead of hiding competition, the installation that assumes the reader is competent, and the contribution guide that makes it easy for people who want to help to actually help. Give it your project, what it does, who it's for, and the alternatives it competes with; it returns a README that earns stars instead of back-button clicks.