skill-creator
Advanced tools
A powerful composite tool for creating and managing Claude Code skills. It serves as both:
package@version format).claude/skills/) or user directory (~/.claude/skills)npm install -g skill-creator
After installation, verify that the CLI is available:
skill-creator --help
If the help output renders, the local skill workflow is available.
skill-creator does not require Claude Code MCP servers for its core CLI workflow.
It uses:
search and get-inforesolve-context7 and download-context7You only need normal outbound network access when using those commands.
npm install -g skill-creator
# Interactive installation - defaults to current when a local subagent already exists, otherwise user
skill-creator init
# Non-interactive installation with explicit default scope resolution
skill-creator init --scope auto
# Machine-readable installation output for tooling/subagents
skill-creator init-cc --json
# Machine-readable documentation sync output
skill-creator download-context7 --pwd ~/.claude/skills/zustand@5 --package zustand --package-version 5.0.0 --json
# Machine-readable user-note output
skill-creator add-skill --package zustand --title "Best Practices" --content "Your custom notes" --json
# Machine-readable index build output
skill-creator build-index --pwd ~/.claude/skills/zustand@5 --json
Use commands directly for complete control over the skill creation process.
Simply describe what you want, and let the subagent handle everything automatically.
User: Use skill-creator subagent to help me create a vitest skill
User: Tell me about vitest testing patterns
The skill-creator subagent will handle the entire workflow automatically.
# Search for packages
skill-creator search "react query"
# Get package information (Options)
skill-creator get-info @tanstack/react-query
# Create skill with package identity only
skill-creator create-cc-skill --scope user --name "@tanstack/react-query" --description "React Query for data fetching" @tanstack/react-query@5 --json
# Create skill with a custom visible skill name while keeping the source package identity
skill-creator create-cc-skill --scope user --name "@tanstack/react-query" --skill-name "react-query" --description "React Query for data fetching" @tanstack/react-query@5 --json
# Let the CLI choose the default storage scope automatically
skill-creator create-cc-skill --scope auto --name zod --description "Zod validation skill" zod@4 --json
# Create skill with interactive prompts
skill-creator create-cc-skill --scope user --interactive --description "React Query for data fetching" @tanstack/react-query@5
# Resolve the best Context7 project id
skill-creator resolve-context7 @tanstack/react-query
# If no package-path candidate matches reliably, the command exits instead of returning a wrong website mirror
skill-creator resolve-context7 is-odd --package-version 3.0.1
# Download documentation directly from the package name
skill-creator download-context7 --package @tanstack/react-query --package-version 5.0.0
# If the skill was created from a package, the package metadata is stored in SKILL.md
# so the same download can usually be triggered with only the skill path
skill-creator download-context7 --pwd ~/.claude/skills/@tanstack__react-query@5
# Or download with an explicit resolved Context7 id
skill-creator download-context7 --package @tanstack/react-query /tanstack/react-query
# Search your skill knowledge base
skill-creator search-skill --package @tanstack/react-query "useQuery hook"
# Append a structured knowledge update into the closest matching user note
skill-creator add-skill --package @tanstack/react-query --title "Bundle guidance" --content "Prefer React Query cache ownership conventions in bundle-sensitive apps." --force-append
| Command | Description |
|---|---|
init | Install skill-creator as Claude Code subagent (user, current, or auto) |
init-cc | Install skill-creator as subagent in user directory |
| Command | Description |
|---|---|
search <keywords> | Search npm packages |
get-info <package> | Get detailed package information |
resolve-context7 <package> | Resolve the best Context7 library id |
create-cc-skill <name> | Create a new skill directory |
| Command | Description |
|---|---|
download-context7 [project_id] | Download and slice Context7 documentation |
build-index | Build or refresh the local search index |
search-skill <query> | Search in skill knowledge base |
add-skill | Add custom knowledge to skill |
Tip: When using the skill-creator as a subagent, you don't need to remember these commands. Just tell Claude what you want to create, and the subagent will handle the entire workflow automatically.
--scope <user|current|auto>: Storage location for skills (required). auto resolves to current when .claude/agents/skill-creator.md exists, otherwise user--name <name>: Package name for the skill (recommended)--skill-name <name>: Visible skill name written into SKILL.md. When omitted, the visible skill name defaults to --name when present, otherwise skill_dir_name--pwd <path>: Working directory for skill operations--package <name>: Use package name to find skill directory--package-version <version>: Version hint for Context7 library resolution--description <description>: Custom description for the skill--force: Replace the closest matching user knowledge note when adding content--force-append: Append a structured knowledge update into the closest matching user note--skip-indexing: Skip automatic local index building--interactive: Enable interactive prompts--json: Print machine-readable output for init, init-cc, create-cc-skill, download-context7, add-skill, and build-indexWhen --package <name> is used to find an existing skill, the CLI first checks the
<skill-package ...> metadata stored in SKILL.md. Directory-name matching is only a fallback.
Search Package: Find the right package for your skill
skill-creator search "state management"
Get Package Info: Retrieve detailed information
skill-creator get-info zustand
Create Skill: Set up skill directory (requires --scope, recommended to use --name)
# With source package identity only
skill-creator create-cc-skill --scope current --name zustand --description "Zustand state management" zustand@5 --json
# With a separate visible skill name
skill-creator create-cc-skill --scope current --name @tanstack/router --skill-name router-skill --description "Router workflow skill" tanstack-router@1 --json
# With explicit default scope resolution handled by the CLI
skill-creator create-cc-skill --scope auto --name zod --description "Zod validation skill" zod@4 --json
# With interactive prompts
skill-creator create-cc-skill --scope current --interactive zustand
--name records the source package identity for later package-aware workflows. --skill-name only controls the visible skill title written into SKILL.md.
Resolve Context7 Project ID: Pick the strongest Context7 source for the package
skill-creator resolve-context7 zustand --package-version 5.0.0
Download Documentation: Get Context7 docs with automatic indexing
# Simplest path when the skill already stores package metadata
skill-creator download-context7 --pwd ~/.claude/skills/zustand@5
# One-step path: resolve and download from the package name
skill-creator download-context7 --package zustand --package-version 5.0.0
# Two-step path: supply the explicit Context7 project id
skill-creator download-context7 --package zustand /zustand
Add Custom Knowledge: Enhance with your own content
skill-creator add-skill --package zustand --title "Best Practices" --content "Your custom notes"
# Replace the closest existing user note
skill-creator add-skill --package zustand --title "Best Practices" --content "Updated note" --force
# Append a structured update into the closest existing user note
skill-creator add-skill --package zustand --title "Operational update" --content "Additional guidance" --force-append
Search Knowledge Base: Query your skill
skill-creator search-skill --package zustand "typescript patterns"
.claude/skills/
└── package@version/
├── assets/
│ ├── references/
│ ├── context7/ # Auto-sliced Context7 docs
│ └── user/ # Custom knowledge files
│ └── search/ # Local search indexes and state
└── SKILL.md # Skill documentation
# Install dependencies
npm install
# Development mode with watch
npm run dev
# Build TypeScript
npm run build
# Run tests
npm test
# Run tests with coverage
npm run test:coverage
# Type check
pnpm ts
To test the built-in Context7 workflow during development:
skill-creator resolve-context7 vitest --package-version 4.1.7
skill-creator download-context7 --help
When validating the real installed CLI during local development, prefer isolated install roots instead of relying on your machine's global package manager state:
# Source-mode workflow verification
pnpm verify:workflow
# Published-style installed binary verification in an isolated prefix
pnpm verify:installed
# Source-linked binary verification in an isolated prefix
pnpm verify:linked
These workflow gates now also prove the vector-runtime contract:
node:sqlite and sqlite-vec, the verification path builds and queries a real --mode=vector indexIf you still want a linked local binary for ad hoc manual testing, use an isolated prefix:
TMP_PREFIX="$(mktemp -d /tmp/skill-creator-link-XXXXXX)"
npm_config_prefix="$TMP_PREFIX" npm link
PATH="$TMP_PREFIX/bin:$PATH" skill-creator --help
This avoids toolchain managers such as Volta interfering with the linked executable.
If you intentionally skip indexing during documentation download, rebuild it explicitly with:
skill-creator build-index --pwd ~/.claude/skills/zustand@5
build-index supports the same persistent index modes as the runtime:
--mode=auto: build the default lightweight persisted index path--mode=fulltext: build the explicit MiniSearch index--mode=vector: build the explicit SQLite vector index when the runtime supports itFor offline or deterministic local vector verification, pass an explicit embedder:
skill-creator build-index --pwd ~/.claude/skills/zustand@5 --mode vector --vector-embedder deterministic
skill-creator search-skill --pwd ~/.claude/skills/zustand@5 --mode vector --vector-embedder deterministic "query ownership"
--vector-embedder deterministic switches vector mode to the built-in local deterministic embedder instead of the default runtime embedder.
--mode=fuzzy is intentionally rejected because fuzzy search does not use a standalone persisted index.
pnpm pre-release-check is a release gate, not a diagnostic summary. It now fails when:
package.json version is already published to npmThat means a green result is evidence that the repository is both technically verified and version-ready for release.
auto: default path, tries full-text first and falls back to fuzzy when quality is weakfulltext: explicit MiniSearch-backed local indexfuzzy: explicit uFuzzy fallback for path/term-style matchingvector: explicit SQLite vector search path when the local runtime supports itchroma remains accepted only as an undocumented legacy alias for vector.
MIT
For detailed subagent usage, see templates/skill-creator.md
FAQs
A local-first CLI and tray workbench for discovering, creating, validating, and installing agent skills.
The npm package skill-creator receives a total of 242 weekly downloads. As such, skill-creator popularity was classified as not popular.
We found that skill-creator demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Security News
GPT-6 Astra tried to plant malicious code in simulated open source projects using fake GitHub accounts and deceptive PRs during an assigned CTF challenge.
Security News
upm uses Node.js to deliver fast npm installs in about 250 KB, with a JavaScript API and security defaults.
Company News
Socket is joining the OpenJS Security Stewardship Program to fund Node.js vulnerability research, maintainer remediation, and security releases.