Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →bluelovers/nodejs-readme-updater
Update Node.js module README.md with installation commands and package.json description/keywords.
Passed 13 of 18 test cases with the skill, and 8 of 18 without it.
and 6 more in the full report
7 fixed9 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are updating `package.json` for `@scope/demo-pkg`. The package currently has existing keywords `["utils", "helpers"]`. We generated new keywords `["demo-pkg", "scope", "automation"]`. Show us the final `keywords` array structure for package.json.
| Checked | Without skill | With skill |
|---|---|---|
| Positions newly generated keywords at the start of the array before existing keywords. | Missed | Passed |
| Preserves the existing order of original keywords after the newly added keywords. | Missed | Passed |
The instructions your model reads when the skill loads.
Update Node.js module README.md with complete installation commands and synchronize package.json description and keywords.
When multiple modules are present in a workspace (monorepo or multi-package project), discover targets using file search tools — never read all package.json or README.md files at once:
glob to find all package.json files (e.g. **/package.json)package.json and README.md individually before editingStrictly one-at-a-time: Never pre-read all modules for any reason (including but not limited to finding modules that need updating). Process only one module at a time, proceed to the next only after completing the current one.
| Principle | Description | Why |
|---|---|---|
| No batch reads | After discovery, read only the target package — never pre-read all modules for any reason | Saves context, avoids noise from unrelated info |
| Create todos | Add discovered packages to a todo list and process sequentially | Makes progress trackable, prevents overlooking packages |
| Cross-package reads | Only read additional packages when there's a cross-package need (e.g. shared config, dependency analysis) | Minimizes unnecessary file reads |
When updating multiple packages, process them one at a time using a todo list to track progress:
For each discovered package, create a todo entry:
test cases passed, vs 8 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.