Menu

Individual skill

readme-benefit-writer

0upvotes

Use when asked to rewrite a README so strangers understand why they should care, turn a feature list into benefits, make a side project's README convincing, or explain what users get rather than what the code does. Rewrites an existing README so every feature is stated as a user benefit in plain sentences, and produces a one-line pitch, a Why section, a benefit-led feature list, a quick start, a Your data section and a contribution pointer. For a README written from scratch with badges, usage and install sections, use readme-writer.

plugins/pm-oss-launch/skills/readme-benefit-writer/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,542
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# README Benefit Writer

Most side-project READMEs describe the code ("built with React, uses SQLite, supports webhooks") when a stranger wants to know what changes for them ("your notes stay on your laptop and sync when you are back online"). This skill rewrites an existing README so each feature is stated as a benefit to a named user, in plain sentences, without losing the facts a developer needs.

## Required Inputs

Ask for these if not provided:
- **The current README** (or the repo's description and feature list)
- **Who it is for**: the one kind of person most likely to install it
- **What they do today instead**: the tool, spreadsheet or habit this replaces
- **Where data goes**: what is stored, where, and whether anything leaves the user's machine
- **How to contribute**: CONTRIBUTING file, issue labels, or "not accepting PRs yet"

## Working from a brief
Back to top