repo-readiness-audit
Use when a user asks whether an identified repository is ready for further development, release work, a new feature, handoff, or a new contributor, requiring a disciplined read-only audit before an evidence-backed verdict.
Profile →npx skills add asimons81/hermes-field-kit --skill repo-readiness-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Repository Readiness Audit ## Overview Use this skill to answer a broad repository-state question before new work begins. It determines whether the repository is ready for further development, release work, a new feature, a handoff, or a new contributor. This is a **read-only evidence audit**. It does not repair findings. It does not equate a clean working tree, passing tests, or a green local b
What does the repo-readiness-audit skill do?
Use when a user asks whether an identified repository is ready for further development, release work, a new feature, handoff, or a new contributor, requiring a disciplined read-only audit before an evidence-backed verdict.
How do I install it?
Run `npx skills add asimons81/hermes-field-kit --skill repo-readiness-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From asimons81/hermes-field-kit, a repository with 120 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.