Project Health
CheckedMonitors project progress, identifies risks & roadblocks, and provides insights to maintain optimal health and deliver on time.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add jezweb/claude-skills --skill project-health -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
jezweb
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned jezweb/claude-skills at 1260fa7439.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1260fa7439
- Scanned
- 6 files, 2,062 lines
About this skill
What it does
The project-health skill evaluates the current state of a project by analyzing its structure, dependencies, and potential issues. It identifies risks such as outdated libraries, missing documentation, or inconsistent code formatting, providing actionable insights to improve maintainability.
When to use it
- Before merging major changes into a codebase to ensure stability
- During onboarding to assess the health of an unfamiliar project
- As part of a CI/CD pipeline to enforce quality standards
- When planning refactoring efforts to prioritize critical areas
Key capabilities
- Analyzes code structure and dependencies
- Detects outdated or vulnerable libraries
- Identifies missing documentation or test coverage
- Highlights formatting inconsistencies across files
Example prompts
- "Evaluate the health of my React project and suggest improvements."
- "Check for outdated packages in this Node.js application."
- "Analyze the codebase for potential maintenance issues."
Tips & gotchas
- Ensure your project has a clear directory structure for accurate analysis.
- This skill may not detect logical bugs or performance issues—use it alongside other tools for comprehensive evaluation.