For AI platform and compliance teams with agent workflows
Shared skills, safe for production.
Agent builders need the same vetted skills, not one-off files nobody's reviewed. Skillsmith shares them across your team, scans them for risk before they ship, and shows you which ones are actually being used.
Free tier available — no credit card required
The shared-skills problem
Once more than one team is sharing agent skills, four questions decide whether that's safe: which team can see it, which version is running, has it been checked for risk, and what happens when nobody's watching it anymore.
Which team is this scoped to?
Every skill is published to a registry scoped to your team.
Which version is installed here?
Versions are immutable once published, so drift across installs is visible instead of silent.
Has it been flagged by the security scan?
Skills pulled from the public index are scored automatically. Flagged or suspicious ones are quarantined pending review.
What happens to the ones nobody maintains?
Skills that go stale can be deprecated instead of quietly rotting in someone's repo.
Without Skillsmith
- ✕ Skills scattered across forks, gists, and shared drives
- ✕ No way to tell which version is installed where
- ✕ No way to catch drift, or deprecate what's gone stale
- ✕ No shared registry — every team starts from scratch
With Skillsmith
- ✓ One registry for your team — publish, version, deprecate
- ✓ Quality scores, integrity-checked publishes, audit logs you can trust
- ✓ MCP, CLI, and VS Code surfaces over the same registry
- ✓ Stack-aware recommendations from hundreds of thousands of indexed skills
Scopes and permissions
Skills are scoped to your team's registry. Team owners and admins control who can publish and manage skills; members install and search.
Start solo
Get Started in Seconds
Pick your MCP client and add this to its config
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"]
}
}
}
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.
After adding this to your settings file and restarting, ask: "Find testing skills for my project"
Semantic Search
Search by intent, not keywords.
Quality Scores
0-100 scores based on docs, tests, maintenance, security.
Stack-Aware
Recommendations tailored to your project's tech stack.
One-Click Install
Install directly. Uninstall just as fast.
Common Questions
What are agent skills?
Is Skillsmith free?
What AI tools does it work with?
How do I install a skill?
npx @skillsmith/cli search testing to find skills, then npx @skillsmith/cli install author/skill-name to install.
Start building for free
Install your first skill in seconds. No credit card required.