sx is your team's private npm for AI assets - skills, MCP configs, commands, and more.
Capture what your best AI users have learned and spread it to everyone automatically.
โญ Star this repo ยท ๐ Website ยท ๐ Changelog ยท ๐ License
Why sx?
Your best developers have figured out how to make AI assistants incredibly productive - custom skills, MCP configs, slash commands, proven patterns. But that knowledge is stuck on their machines.
Current workarounds don't scale:
- Copy into each repo - Duplication nightmare, no central updates, version drift
- Global config - Bloats context for projects/tasks that don't need those skills
- Client plugins - Manually install each one, locked to one AI client, no bundling
sx solves this by:
- Sharing expertise - Turn individual discoveries into team assets
- Instant onboarding - New devs inherit the team's AI playbook on day one
- Central updates - Change once in your vault, everyone gets the update
- Scoped installation - Right assets for each repo, no context bloat
- Works with any AI client - Claude Code, Cursor, and more (coming soon)
Quickstart
Install via Homebrew (macOS/Linux):
brew tap sleuth-io/tap brew install sx
Or via shell script:
curl -fsSL https://raw.githubusercontent.com/sleuth-io/sx/main/install.sh | bashThen
# Initialize sx init # Add an asset from your vault sx add /path/to/my-skill # Install assets to your current project sx install
Multiple vaults? Use profiles to switch between them:
sx profile add work # Add a new profile sx profile use work # Switch to it sx profile list # See all profiles
Already using Claude Code?
If you've built up skills, plugins, or MCP configs in your .claude directory, sx helps you version, sync across machines, and share with teammates.
# Add your existing skills/commands (sx auto-detects the type) sx add ~/.claude/commands/my-command sx add ~/.claude/skills/my-skill sx add code-review@claude-plugins-official
Your prompt files stay exactly as they are - sx just wraps them with metadata for versioning.
What can you build and share?
- Skills - Custom prompts and behaviors for specific tasks
- Rules - Coding standards and guidelines that apply to specific file types or paths
- Agents - Autonomous AI agents with specific goals
- Commands - Slash commands for quick actions
- Hooks - Automation triggers for lifecycle events
- MCP Servers (experimental) - Model Context Protocol (MCP) servers for external integrations
- Plugins - Claude Code plugin bundles with commands, skills, and more
Distribution models
Choose the right distribution model for your team:
Local (Personal)
Perfect for easily sharing personal tools across multiple personal projects
sx init --type path --path my/vault/path
Git vault (Small teams)
Share assets through a shared git vault
sx init --type git --repo git@github.com:yourteam/skills.git
Skills.new (Large teams and enterprise)
Centralized management with a UI for discovery, creation, sharing, and usage analytics
How it works
sx uses a lock file (like package-lock.json) for deterministic installations across your team:
- Create assets with metadata (name, version, dependencies)
- Share to your vault
- Install globally, per project, or even per path (monorepo support!)
- Auto-install on new Claude Code sessions
- Stay synchronized - everyone gets the same tools automatically
Supported Clients
| Client | Status | Notes |
|---|---|---|
| Claude Code | โ Supported | Full support for all asset types |
| Cursor | โ Experimental | Skills, rules, MCP servers, commands, hooks |
| GitHub Copilot | โ Experimental | Skills, rules, commands, agents, MCP servers, local hooks |
| Gemini | Coming soon | |
| Codex | Coming soon |
Roadmap
- โ Local, Git, and Skills.new vaults
- โ Claude Code support
- โ Cursor support (experimental)
- โ GitHub Copilot support (experimental)
- More clients - Gemini, Codex
- Skill discovery - Use Skills.new to discover relevant skills from your code and architecture
- Analytics - Track skill usage and impact
License
See LICENSE file for details.
Development
Click to expand development instructions
Documentation
- Vault Spec - Skills vault structure
- Metadata Spec - Skill metadata format
- Lock Spec - Lock file format
- MCP Spec - MCP server and query tool
- Scoping - Controlling where assets are installed
- Profiles - Multiple configuration profiles
Prerequisites
Go 1.25 or later is required. Install using gvm:
# Install gvm bash < <(curl -s -S -L https://raw.githubusercontent.com/moovweb/gvm/master/binscripts/gvm-installer) # Install Go (use go1.4 as bootstrap if needed) gvm install go1.4 -B gvm use go1.4 export GOROOT_BOOTSTRAP=$GOROOT gvm install go1.25 gvm use go1.25 --default
Building from Source
make init # First time setup (install tools, download deps) make build # Build binary make install # Install to GOPATH/bin
Testing
make test # Run tests with race detection make format # Format code with gofmt make lint # Run golangci-lint make prepush # Run before pushing (format, lint, test, build)
Releases
Tag and push to trigger automated release via GoReleaser:
git tag v0.1.0 git push origin v0.1.0

