⚕
Diagnostics & Maintenance
doctor
A diagnostic command that checks your environment for everything skills-check needs: Node version, package manager, registry reachability, isolation runtimes, LLM provider configuration, and project setup.
Why it matters
Missing prerequisites cause confusing errors deep in a workflow. Doctor surfaces setup problems upfront — wrong Node version, missing pnpm, unreachable registry, no isolation runtime, missing API keys — before they block your work.
What it does
- Checks Node.js version against the >=22 requirement
- Detects pnpm availability and lockfile consistency
- Tests npm registry reachability with a 5-second timeout
- Probes available isolation runtimes (Docker, Podman, OrbStack, Apple Containers, Vercel Sandbox)
- Checks for LLM provider API keys (Anthropic, OpenAI, Google)
- Verifies skills-check.json registry file exists in the current directory
Usage
npx skills-check doctor [options]Options
| Flag | Description |
|---|---|
--format <type> | Output format: terminal or json |
--ci | CI mode — exit non-zero on errors |
Examples
Check environment
npx skills-check doctorJSON output
npx skills-check doctor --format jsonCI gate
npx skills-check doctor --ciWhen to use this
- When setting up skills-check for the first time
- When commands fail with unexpected errors
- In CI to validate runner prerequisites
Related commands
- init — Validate environment, then initialize registry
CI tip
Run doctor --ci as the first step in your pipeline to catch environment issues before any other commands run.