Table of contents
skillme docs
The missing plugin manager for Claude Code. Detect your stack, install the right plugins, and keep your whole team in sync.
Installation
Install skillme globally via npm. Requires Node.js 18+ and the Claude Code CLI.
Quick Start
Run skillme init inside any project directory. skillme detects your stack, fetches plugin recommendations, and shows an interactive picker.
◆ skillme — Claude Code plugin manager │ ◇ Stack detected │ → React, TypeScript, Tailwind │ ◇ Plugin index ready │ ◆ Select plugins to install (space to toggle, enter to confirm): │ ● commit-commands official │ ● code-review official │ ○ react-patterns community │ ○ tanstack-query community │ ◇ Install scope: │ ● project shared with team via .claude/settings.json │ ○ user only you, across all projects │ ○ local only you, this project, gitignored │ ◆ 2 plugin(s) installed. Run /reload-plugins in Claude Code to activate.
init
Detects your project stack and installs recommended plugins. Runs an interactive multiselect — official plugins are pre-selected, community plugins are opt-in.
Options
-s, --scope <scope>Install scope: user | project | localdefault: project--aiUse Claude to analyze your project for smarter, project-specific recommendationsskillme init --ai for recommendations that reference your actual dependencies and git history. See AI Mode.search
Search for plugins by name or keyword across all marketplaces.
Options
-s, --scope <scope>Scope for installation from the pickerdefault: userinstall
Install a specific plugin by name, optionally pinning the marketplace.
Options
-s, --scope <scope>Install scope: user | project | localdefault: user-m, --marketplace <id>Specify which marketplace to install fromlist
Show all installed plugins across every scope, with descriptions fetched from the live index.
user scope
✓ commit-commands
Adds slash commands for writing conventional commits
project scope
✓ code-review
Adds a /review command that reviews open changesupgrade
Re-installs all currently installed plugins to pick up the latest versions. Prompts for confirmation before proceeding.
doctor
Checks your environment for issues that could prevent plugins from working correctly.
Checks
Node.js versionMust be ≥ 18.0.0Claude CLIInstalled and accessible in PATHPlugin binariesAny required external tools (e.g. language servers)Settings file integrityValid JSON in all .claude/settings*.json filessync
Saves your project plugin setup to a skillme.json lockfile and installs from it. Commit the lockfile so teammates get identical plugins with one command.
First time — create the lockfile
Teammate — install from lockfile
Update lockfile after adding plugins
Options
--saveForce-overwrite skillme.json with current project-scope pluginsuninstall
Remove an installed plugin. Without a name, shows an interactive picker of all installed plugins.
info
Show full details for a plugin — description, marketplace, tags, and install command.
update
Refresh the marketplace plugin index from GitHub. skillme caches the index locally; run this to pick up newly published plugins.
Stack Detection
skillme scans your project directory for known files and infers your tech stack. If no files match, it falls back to scanning your README for keyword patterns.
Detected by file
package.json → node, react, next, vue, angular, svelte,
express, fastify, nestjs, prisma, drizzle…
go.mod → go, gin, echo, fiber, gorm
Cargo.toml → rust, actix, axum, rocket, tokio
pom.xml → java, spring, quarkus
build.gradle → java, kotlin, spring
*.csproj / *.sln → csharp, aspnet, blazor
Gemfile → ruby, rails, sinatra
composer.json → php, laravel, symfony
pubspec.yaml → dart, flutter
requirements.txt → python
pyproject.toml → python, fastapi, django, poetry
Dockerfile → dockerREADME fallback
If no matching files are found, skillme scans README.md for technology keywords. README-sourced detections are shown with a dim (from README) label.
AI Mode
skillme init --ai uses your existing Claude Code subscription — no extra API key required.The --ai flag sends your project context to Claude and gets back plugin recommendations with specific, project-aware reasons.
◇ Analysis complete │ ◆ Select plugins to install: │ ● commit-commands "47 commits with inconsistent messages in git log" │ ● tanstack-query "found @tanstack/react-query in package.json" │ ○ security-guidance ".env file detected alongside SQL queries in src/" │ ● code-review "active PR workflow detected in .github/workflows/"
How it works
skillme builds a context snapshot — root files, directory structure, npm dependencies, recent git log — and sends it alongside the full plugin list to claude -p. Claude returns a ranked list of plugins with one-line reasons tied to your specific project. Falls back to file-based detection if the Claude CLI is unavailable.
Team Sync
skillme.json is a lockfile that captures your project-scope plugin setup. Commit it to git so every teammate gets identical Claude Code plugins automatically.
// skillme.json
{
"version": 1,
"plugins": [
{ "name": "commit-commands", "marketplace": "claude-plugins-official" },
{ "name": "code-review", "marketplace": "claude-plugins-official" }
]
}New team members run skillme sync after cloning. Existing members run it after pulling changes that update the lockfile. Only project-scope plugins are included — user and local plugins stay personal.
skillme sync to your onboarding README or post-checkout git hook to make it automatic.Scopes
skillme installs plugins at one of three scopes. The scope controls where the plugin entry is written and who it applies to.
projectWritten to .claude/settings.json — shared with your team via git. Use this for project-specific plugins everyone should have.userWritten to ~/.claude/settings.json — applies to you across all projects. Use this for personal workflow plugins.localWritten to .claude/settings.local.json — gitignored, only you, this project. Use this for personal overrides.skillme init and skillme install is project and user respectively. Pass --scope <scope> to override.