Readme badge
Skill NSBen/skillfoundry/src/skillfoundry/data/starter_skills/readme-badge
Use when you want to add accurate, up-to-date status badges (build, version, license, coverage, PyPI) to a README and avoid broken, stale, or misleading shields.From its SKILL.md
npx -y skills add NSBen/skillfoundry --skill readme-badgeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.2 KB, 184 tokens by cl100k_base, as published. Nobody here has run it
README Badge
When to use
Invoke this skill when finalizing a README and you want status badges that stay correct and load reliably.
Steps
- Pick badges that reflect real signals: build, version, license, coverage, downloads.
- Prefer shields.io dynamic endpoints or the project's native badge (GitHub Actions, PyPI).
- Use a flat, compact style and keep the row to 3–6 badges.
- Avoid badges that lie (hardcoded "passing") or services that rate-limit hotlinks.
- Verify each image URL renders, then place the markdown at the top of the README.
Examples
- "Insert a build + license + PyPI version badge row"
- "My coverage badge is stale — point it at the right job"
References
Keep badges honest and few; a clutter of fifteen shields hurts credibility more than it helps.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.