5-Minute Setup
Get Skillsmith running in 5 minutes. Choose your preferred workflow below.
Note: The bare skillsmith package on npm is not this project. Use @skillsmith/cli for the CLI or @skillsmith/mcp-server for MCP. Alternatively, npm install -g skillsmith-cli also works.
Before You Begin
Make sure you have:
- Node.js >=22.22 installed (
node --versionto check) - npm or another package manager
Choose Your Workflow
MCP Client Setup
Use natural language to discover and install skills. Just ask your assistant!
- "Find skills for this React project"
- "Install the commit helper skill"
- "What testing skills do you recommend?"
Direct CLI
Use traditional command-line tools in any terminal.
skillsmith search testingskillsmith install jest-helperskillsmith list
Using an MCP Client
What is MCP?
MCP (Model Context Protocol) lets AI coding agents — Claude Code, Cursor, GitHub Copilot, Windsurf, Codex CLI, and others — connect to external tool servers. An "MCP client" is just your agent's name for this capability. Skillsmith provides an MCP server that gives your agent the ability to search and install skills for you.
Step 1: Open Your Project, Then Open Your AI Agent
Skillsmith reads your project's package.json and file structure to
recommend relevant skills, so open your AI agent from inside the project you
want skills for.
cd /path/to/your/project "MCP client" just means your AI coding agent — Claude Code, Cursor, GitHub Copilot, Windsurf, and Codex CLI all work the same way here. Already have one open in this project? Skip to Step 2.
Don't have an agent yet? Claude Code is a fast-to-install default — any agent above works the same way.
Installing Claude Code (skip this if you already have an agent open):
# Install via npm (recommended)
npm install -g @anthropic-ai/claude-code
# Or via Homebrew
brew install claude-code Step 2: Add the Skillsmith MCP Server
Using Claude Code? Start with Option A. Using any other agent? Skip to Option B.
Option A — Claude Code's built-in command (fastest)
claude mcp add skillsmith -- npx -y @skillsmith/mcp-server
The -- separates Claude Code's own flags from the command it should
run. This adds the server at the default --scope local (this
project only); pass --scope user to make it available in every
project instead, or --scope project to share it via a checked-in
config. Verify with claude mcp list; remove it with
claude mcp remove skillsmith.
Note: skillsmith here is just a local name you're choosing for
this install — it doesn't need to match the @skillsmith/mcp-server
package name used in Option B/C's config files.
Option B — Ask your agent in chat (works with any agent)
This is a normal file-edit request, not a special "auto-config" feature — your agent will edit a config file for you, and you should expect the usual permission prompt the first time it writes to a new file. Paste this into your agent's chat:
Please add the Skillsmith MCP server to my MCP client configuration.
Create the config file if it doesn't exist yet, and show me the diff
before you save. Use this entry:
{
"mcpServers": {
"@skillsmith/mcp-server": {
"command": "npx",
"args": ["-y", "@skillsmith/mcp-server"]
}
}
}
If you are NOT Claude Code, also add an "env" block to that entry with
SKILLSMITH_CLIENT set to your own client name (e.g. "windsurf" for Windsurf,
"copilot" for GitHub Copilot) so skills install to your own skills directory
instead of Claude Code's default. If you're not sure of the right value,
ask me before saving.
Tell me which file you changed when you're done. Not using Claude Code? Skills install to your agent's own
directory by default (e.g. ~/.claude/skills/ for Claude Code). The
prompt above already asks your agent to set SKILLSMITH_CLIENT for
itself when it isn't Claude Code — see the client-specific snippets in Option C
below for exact examples if you'd rather edit the file yourself.
Using Cursor? Skip the prompt above and use Option C's Cursor
snippet instead — Cursor's bundled Node cannot resolve packages via
npx (a real ENOENT), so the "command": "npx"
entry above will not connect. Option C's Cursor section gives you the
resolved-path form that's confirmed to work.
Option C — Edit the config file yourself
Pick the snippet for your MCP client and add it to the matching config file. Every snippet uses the same shape — only the config-file path (and, for Codex/Hermes, the format) differs.
Claude Code — ~/.claude/settings.json
{
"mcpServers": {
"@skillsmith/mcp-server": {
"command": "npx",
"args": ["-y", "@skillsmith/mcp-server"]
}
}
} Cursor — ~/.cursor/mcp.json
{
"mcpServers": {
"@skillsmith/mcp-server": {
"command": "<paste output of: which skillsmith-mcp (macOS/Linux) or where skillsmith-mcp (Windows)>",
"env": {
"SKILLSMITH_CLIENT": "cursor"
}
}
}
} Cursor 2.4+ required, Node >=22.22 (Cursor's own bundled Node meets this). Setup: run npm install -g @skillsmith/mcp-server, then run which skillsmith-mcp (macOS/Linux) or where skillsmith-mcp (Windows) and paste that path into command above — Cursor's bundled Node cannot resolve packages via npx (a real ENOENT on a missing Resources/app/resources/lib directory), so pointing directly at the installed binary is the only form confirmed to work inside Cursor. SKILLSMITH_CLIENT routes installs to ~/.cursor/skills instead of the default ~/.claude/skills. Prefer to try npx first anyway? Replace command with "npx" and add "args": ["-y", "@skillsmith/mcp-server"] — simpler, but may hit the same ENOENT, plus EBADENGINE or ENOTEMPTY on repeated installs. After saving: enable the server in Cursor's Settings → MCP panel and start a new chat — a correctly-configured entry still shows disconnected until toggled on there — then reload the window.
GitHub Copilot (VS Code) — .vscode/mcp.json (workspace)
{
"mcpServers": {
"@skillsmith/mcp-server": {
"command": "npx",
"args": ["-y", "@skillsmith/mcp-server"]
}
}
} VS Code 1.108+ required. Workspace-scoped (commit to repo if team-shared, or use user settings.json instead).
Windsurf — ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"@skillsmith/mcp-server": {
"command": "npx",
"args": ["-y", "@skillsmith/mcp-server"]
}
}
} Supports ${env:VAR} interpolation for secrets in this config.
Codex CLI — ~/.codex/config.toml (TOML)
[mcp_servers.@skillsmith/mcp-server]
command = "npx"
args = ["-y", "@skillsmith/mcp-server"] Codex reads ~/.agents/skills. When installing via Skillsmith CLI, pass --client agents.
Cross-agent (open standard) — ~/.agents/mcp.json
{
"mcpServers": {
"@skillsmith/mcp-server": {
"command": "npx",
"args": ["-y", "@skillsmith/mcp-server"]
}
}
} OpenCode — ~/.config/opencode/opencode.json
{
"mcp": {
"@skillsmith/mcp-server": {
"type": "local",
"command": ["npx", "-y", "@skillsmith/mcp-server"],
"enabled": true
}
}
} OpenCode also reads .claude/skills and .agents/skills for skill discovery. Note the OpenCode-specific entry shape: command is an array and the env-var field is named environment, not env.
Hermes (Nous Research) — ~/.hermes/config.yaml (YAML)
mcp_servers:
@skillsmith/mcp-server:
command: "npx"
args: ["-y", "@skillsmith/mcp-server"] Hermes config is YAML. Hermes has no SessionStart hook equivalent — nudge/attribution is unsupported on this harness.
Grok Build (xAI) — ~/.grok/config.toml (TOML)
[mcp_servers.@skillsmith/mcp-server]
command = "npx"
args = ["-y", "@skillsmith/mcp-server"] Grok Build uses TOML under a [mcp_servers.NAME] table, the same convention as Codex CLI above.
Google Antigravity — ~/.gemini/config/mcp_config.json
{
"mcpServers": {
"@skillsmith/mcp-server": {
"command": "npx",
"args": ["-y", "@skillsmith/mcp-server"],
"env": {
"SKILLSMITH_CLIENT": "antigravity"
}
}
}
} One config file is shared across the Antigravity CLI, IDE, and 2.0. A workspace-scoped alternative also exists at .agents/mcp_config.json (project root) if you prefer not to register the server globally. SKILLSMITH_CLIENT routes installs to ~/.gemini/config/skills instead of the default ~/.claude/skills.
After any of the three options above, restart your agent to load Skillsmith.
Step 3: Discover Skills for Your Project
You're already in your project with your agent open from Step 1 — just ask:
You're all set!
Skills install to your MCP client's own directory — ~/.claude/skills/ for
Claude Code, ~/.cursor/skills/ for Cursor, or the equivalent path for
your agent (see the client-specific snippet above) — and are automatically available
in all your sessions.
Built-in security scanning — Every skill is automatically scanned for security issues before installation. Skills with critical findings are blocked; high-severity findings require your confirmation. Learn more about security →
Using the CLI Directly
When to use this
Use the CLI if you prefer traditional command-line tools, want to script skill management, or are not using an MCP client.
Step 1: Install the Skillsmith CLI
# Install globally
npm install -g @skillsmith/cli
# Verify installation
skillsmith --version After this, skillsmith command is available everywhere.
Step 2: Navigate to Your Project
Open your terminal and navigate to your project directory:
Why navigate here? Skillsmith can analyze your project's package.json, dependencies, and file structure to recommend relevant skills.
Step 3: Search for Skills
# Search by keyword
skillsmith search testing
# Search with filters
skillsmith search react --category development
skillsmith search git --tier verified
# Get recommendations for current project
skillsmith recommend
The recommend command analyzes your project and suggests relevant skills.
Step 4: Install Skills
# Install by skill name
skillsmith install jest-helper
# Install by full ID
skillsmith install community/react-patterns
# Install multiple skills
skillsmith install jest-helper commit react-patterns Step 5: Verify Installation
# List installed skills
skillsmith list
# Show skill details
skillsmith info jest-helper Skills Installed!
By default the CLI installs to ~/.claude/skills/. Pass --client cursor
(or another client name) to target a different MCP client's directory instead —
they'll be automatically available when you use that client.
Next Steps
Browse Skills
Explore available skills by category and trust tier.
Configuration Guide
Set up API keys, verify installation, and troubleshoot issues.
CLI Reference
Complete documentation for all CLI commands.
MCP Server
Advanced configuration for the MCP integration.
Ready to configure API keys?
Continue to the Configuration Guide for API key setup, verification, and advanced options.