10x-health-check

Audits an existing project's dependencies, tests, CI/CD, and configuration for agent-readiness.

Updated May 20, 2026
One-click install
npx skills add https://github.com/Oskarovsky/Sprinter --skill 10x-health-check-oskarovsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-health-check
Source: https://github.com/Oskarovsky/Sprinter/tree/main/.cursor/skills/10x-health-check
Command: npx skills add https://github.com/Oskarovsky/Sprinter --skill 10x-health-check-oskarovsky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Before letting an AI assistant work on an existing codebase, you need to know whether the project is operationally healthy: are dependencies vulnerable, is there a test runner to verify changes, is CI configured, and are key config files missing. This Skill runs that audit automatically and produces a prioritized report. ## Core Features & Use Cases - Dependency and security audit: Detects the language family from project markers (package.json, Cargo.toml, pyproject.toml, go.mod, and more), checks lockfile presence, runs the ecosystem's audit tool (npm audit, pip-audit, cargo audit, govulncheck, and others), and tiers findings by CVSS severity. - Test runner and CI/CD detection: Identifies the test framework, attempts a dry run, and evaluates CI pipeline coverage across lint, test, build, type-check, and security stages. - Prioritized health report: Writes context/foundation/health-check.md with a healthy / needs-attention / critical-issues verdict, concrete fix commands, effort estimates, and cross-references to stack-assessment findings when available. - Use Case: You inherit a brownfield Node.js project and ask for a health check. The Skill runs npm audit, detects that Vitest is configured but the lockfile is missing, notes there is no CI pipeline, and writes a report ranking the fixes by impact on AI-assisted development. ## Quick Start Ask the assistant to run a health check on the project in the current directory and write the report to context/foundation/health-check.md.

Frequently Asked Questions about 10x-health-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit an existing project before using an AI coding assistant?

Run the health check in the project's root directory. It detects the language family from project markers, audits dependencies for vulnerabilities, verifies the test runner works, evaluates CI/CD coverage, and writes a prioritized report to context/foundation/health-check.md.

What security audit tools does the health check use for each language?

It dispatches per ecosystem: npm audit for JS/TS, pip-audit for Python, cargo audit for Rust, govulncheck for Go, bundle audit for Ruby, composer audit for PHP, and dotnet list package --vulnerable for .NET. Missing tools are skipped with a warning rather than halting.

Does the health check modify or fix my project automatically?

No. The audit is strictly read-only. It never runs npm audit fix, upgrades packages, or edits configuration. Every finding includes a concrete fix command, but executing fixes is left to the user.

What happens if my project has no test runner or CI pipeline?

A missing test runner is flagged as a significant finding because the AI assistant cannot verify its own changes. Missing CI is treated as a lower-priority item to address later and does not by itself lower the health verdict.

Can I run the health check without a prior stack assessment?

Yes. The stack-assessment.md file is optional input. When present, findings are cross-referenced against its quality-gate gaps; when absent, the health check runs standalone and produces a complete report on its own.