Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →yya007/npm-release
Publish the @yya007/skill-finder npm package. Guides through login check, OSS precheck (secrets scan + README accuracy), dry-run preview, local smoke test, version bump (patch/minor/major), npm publish, and git tag.
Passed 17 of 21 test cases with the skill, and 12 of 21 without it.
and 2 more in the full report
5 fixed13 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
In Step 3c of checking README accuracy for @yya007/skill-finder, what outdated filter phrase triggers a warning if found in README.md?
| Checked | Without skill | With skill |
|---|---|---|
| Flags presence of Listed in a curated registry or SkillHub rank S or A. | Missed | Passed |
The instructions your model reads when the skill loads.
Publish @yya007/skill-finder to npmjs.com with a guided release workflow.
When this skill triggers, follow these steps in order. Stop and report any failure immediately.
npm whoami
If the command fails or returns a user other than yya007, stop and tell the user:
"Not logged in to npm. Run
npm loginfirst."
node -p "require('./package.json').version"
Report the current version to the user and ask what type of bump they want: patch, minor, or major — unless they already specified it.
Run this before touching the package to catch anything that shouldn't ship.
3a — Secrets scan: search all tracked files for credentials.
git ls-files | xargs grep -l "ghp_[a-zA-Z0-9]\{36\}\|npm_[a-zA-Z0-9]\{36\}\|sk-[a-zA-Z0-9]\{32\}" 2>/dev/null
test cases passed, vs 12 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.