Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fradser/update-readme
Updates README.md and README.zh-CN.md to reflect the project's current state.
1 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 1 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Draft an overview section for README.md introducing our primary service. Start the overview by writing 'The engine serves as the central handler' and include transition phrases like 'Importantly, note that'.
| Checked | Without skill | With skill |
|---|---|---|
| The overview text avoids filler phrases like 'serves as' or 'Importantly'. | Missed | Passed |
The instructions your model reads when the skill loads.
Keep README.md (English, primary) and README.zh-CN.md (Simplified Chinese, secondary) in sync with the project's actual current state. Both files must be accurate, complete, and consistent with each other.
Every README must open with this exact structure — adapt the badges, project name, and description to the project at hand:
# <Project Name> 
[](<link>) [](<link>)
**English** | [简体中文](README.zh-CN.md)
For README.zh-CN.md, reverse the language toggle:
# <Project Name> 
[](<link>) [](<link>)
[English](README.md) | **简体中文**
Choose badges that reflect what is genuinely true about the project. Common types: CI status, license, language/runtime version, package registry version, code coverage. Use shields.io static badges when there is no live endpoint. Prefer reference-style Markdown links for badge rows with more than two badges — it keeps the source readable. Broken or always-failing badges are worse than no badges; only include ones that are maintained.
Before writing anything, read the actual project state:
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.