package-health
Check a package's health before you depend on it — npm and PyPI registry APIs via keyless curl: downloads, release recency, maintenance signals, and the dependency-decision read. Use when asked is this npm package maintained, check this PyPI library before we adopt it, compare these two packages, or is this dependency abandoned. Produces the health read with the signals interpreted (not just listed), the numbers with their commands, and the adopt/avoid/vendor recommendation framing.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill package-health --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.
# Package Health Skill Adding a dependency is hiring code you'll never interview — and the registries publish the résumé keylessly: last release date, download trajectory, version cadence, maintainer count. This skill pulls the signals for npm and PyPI over plain curl and does the part the raw numbers don't: interpretation. A package with no release in three years is *abandoned or finished* — and which one it is depends on what the package does. The output is a read, not a dashboard. ## What This Skill Produces - **The health read** — maintained / stable-and-done / drifting / abandoned — with the reasoning - **The signals table** — latest version + date, download scale, release cadence, deprecation flags - **The comparison** — for adoption decisions between candidates, same signals side by side - **The commands** — every number's curl, rerunnable ## Required Inputs Ask for these if not provided: - **The package(s) and ecosystem** — npm or PyPI; exact names (typosquats are a real hazard — the exact-name check is part of the job, and a near-miss name is a 🔴 finding, not a typo to auto-correct) - **The role it would play** — a core dependency, a dev tool, a one-function utility: the
- What This Skill Produces
- Required Inputs
- Framework: The Signals and the Reads
- Output Format
- Quality Checks
- Anti-Patterns
What does the package-health skill do?
Check a package's health before you depend on it — npm and PyPI registry APIs via keyless curl: downloads, release recency, maintenance signals, and the dependency-decision read. Use when asked is this npm package maintained, check this PyPI library before we adopt it, compare these two packages, or is this dependency abandoned. Produces the health read with the signals interpreted (not just listed), the numbers with their commands, and the adopt/avoid/vendor recommendation framing.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill package-health --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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.