➜
Setup
init
Bootstrap skills-check for your project. Scans a directory for SKILL.md files, prompts for npm package mappings, and generates the skills-check.json registry that all other commands depend on.
Why it matters
The skills-check.json registry is the foundation — it maps product names to npm packages and tracks which skill files belong to which product. Without it, check, report, and refresh can't function. Init sets everything up in seconds.
What it does
- Recursively scans a directory for files matching *SKILL.md or *skill.md
- Extracts product names and version references from frontmatter
- In interactive mode, prompts you to confirm or correct npm package mappings
- In non-interactive mode (-y), auto-detects mappings from frontmatter
- Generates a skills-check.json with $schema reference for editor validation
Usage
npx skills-check init [dir] [options]Options
| Flag | Description |
|---|---|
-y, --yes | Non-interactive mode (auto-detect mappings) |
-o, --output <path> | Output path (default: skills-check.json) |
Examples
Interactive setup
npx skills-check init ./skillsAuto-detect
npx skills-check init ./skills -yCustom output path
npx skills-check init ./skills -o config/registry.jsonWhen to use this
- When starting a new project with agent skills
- To set up skills-check in an existing repo
Related commands
- check — Set up registry, then start checking
CI tip
Run init once locally, then commit skills-check.json to your repo. Other commands will find it automatically.