managing-local-skills
Manages Claude Code skills from plugin marketplaces using the local-skills CLI. Use when the user wants to add, update, remove, list, or inspect skills from a marketplace, or when managing the project's .claude/skills/ directory with version-tracked skills. Triggers on "install a skill", "add skill from marketplace", "update skills", "list available skills", "remove skill", or "local-skills".
What this skill does
# Managing Skills with local-skills CLI `local-skills` is a CLI tool for extracting and managing Claude Code skills from plugin marketplaces. It installs skills into `.claude/skills/` with version tracking, modification detection, and update management. ## Prerequisites The tool must be installed from npm before use: ```bash npm install -g local-skills ``` Or you can install per-project: ```bash npm install --save-dev local-skills ``` Verify installation: ```bash local-skills --help ``` ## Commands ### Add a skill ```bash local-skills add <specifier> ``` The specifier format is `<plugin>@<marketplace>/<skill>[:<version>]`: | Part | Description | | ------------- | ----------------------------------- | | `plugin` | Plugin name in the marketplace | | `marketplace` | GitHub `owner/repo` or full git URL | | `skill` | Skill name (or `*` for all) | | `version` | Optional git ref (tag, branch) | Examples: ```bash # Add a single skill from a GitHub marketplace local-skills add superpowers@anthropics/claude-code/tdd # Pinned to a specific tag local-skills add superpowers@anthropics/claude-code/tdd:v2.0 # All skills from a plugin local-skills add superpowers@anthropics/claude-code/* # From a full git URL local-skills add my-plugin@https://gitlab.com/team/repo.git/my-skill ``` ### List skills ```bash local-skills ls [source] ``` Options: - `--long, -l` — Show descriptions - `--installed` — Only installed skills - `--not-installed` — Only non-installed skills Examples: ```bash # List all installed skills local-skills ls --installed # List skills from a remote marketplace with descriptions local-skills ls anthropics/claude-code --long # List skills not yet installed from a marketplace local-skills ls anthropics/claude-code --not-installed ``` ### Show skill details ```bash local-skills info <skill> ``` Displays source, version, and content information for an installed skill. ### Update a skill ```bash local-skills update <skill-name> ``` Options: - `--force, -f` — Overwrite locally modified files Update behavior: - Skills pinned to a specific commit SHA (40-char hex) are skipped automatically - If skill files were modified locally, update is refused unless `--force` is passed - If the state file is missing, modification check is skipped ### Remove a skill ```bash local-skills remove <skill-name> ``` Removes the skill directory from `.claude/skills/` and cleans up tracking files. ## Tracked Files Both files should be committed to version control: - **`.claude/local-skills.json`** — Manifest declaring what skills are installed and from where (source, ref, SHA) - **`.claude/local-skills-state.json`** — Content hashes for installed skill files, used to detect local modifications ## How It Works 1. Parses the specifier to identify the plugin, marketplace, skill, and optional version 2. Shallow-clones the marketplace git repo 3. Reads `.claude-plugin/marketplace.json` to find the plugin 4. Copies the skill directory to `.claude/skills/<skill-name>/` 5. Records the source, ref, and commit SHA in the manifest 6. Computes a content hash and stores it in the state file ## Workflow Guidance When a user asks to add skills from a marketplace: 1. Check if `local-skills` is installed: `local-skills --help` 2. If not installed, install it: `npm install -g local-skills` 3. If the user knows the marketplace, use `local-skills ls <marketplace> --long` to show available skills 4. Use `local-skills add` with the appropriate specifier 5. Verify installation with `local-skills ls --installed` When a user asks to update skills: 1. Check current state: `local-skills ls --installed` 2. Run `local-skills update <skill-name>` for each skill 3. If update fails due to local modifications, inform the user and suggest `--force` only if they confirm When a user asks about available skills: 1. Use `local-skills ls <marketplace> --long` to browse a marketplace 2. Use `local-skills info <skill>` for details on an installed skill
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.