跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
部署与云服务

manage-skills

Manage the user's shared agent-skill library via skills-manager-cli — install, update, remove, deploy or undeploy skills per agent or into a project's own agent directories, manage presets, organize tags, search, and adopt existing skills. Use this whenever the user wants Claude Code, Codex, Cursor, or another agent to gain or lose a skill (globally or in one repo), wants to organize the central library, or asks what is installed or deployed. Prefer this over direct agent-folder installs because Skills Manager preserves source metadata, preset membership, updates, and cross-agent deployment state.

xingkongliang · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add xingkongliang/skills-manager --skill manage-skills

技能说明


name: manage-skills description: Manage the user's shared agent-skill library via skills-manager-cli — install, update, remove, deploy or undeploy skills per agent or into a project's own agent directories, manage presets, organize tags, search, and adopt existing skills. Use this whenever the user wants Claude Code, Codex, Cursor, or another agent to gain or lose a skill (globally or in one repo), wants to organize the central library, or asks what is installed or deployed. Prefer this over direct agent-folder installs because Skills Manager preserves source metadata, preset membership, updates, and cross-agent deployment state.

Before doing anything

  1. Resolve the CLI first, then use the path it prints. Run this once (POSIX shell):

    D="$HOME/.skills-manager/bin"
    B="$D/skills-manager-cli"; [ -e "$B" ] || B="$B.exe"   # .exe on Windows
    if [ -s "$D/.version" ] && [ -x "$B" ]; then
      echo "$B"
    elif [ -s "$D/.version" ] || [ -e "$B" ]; then
      echo BRIDGE_BROKEN
    else
      P="$(command -v skills-manager-cli 2>/dev/null || true)"
      [ -x "$P" ] && echo "$P"
    fi
    

    Substitute the printed path into every command below, wherever the examples write $SM. Do not carry $SM as a shell variable: each command you run is a new shell, so an assignment made here is gone by the next one.

    The three outcomes:

    • A path under ~/.skills-manager/bin — the desktop app published this copy, and the .version stamp appears only after it has been verified, so it always matches the app the user is running. Use it.
    • BRIDGE_BROKEN — something the app left behind is here but does not add up: an unstamped binary, or a stamp with no binary beside it. Either is what a copy that failed half-way leaves. Stop. Do not go looking for another CLI: that binary may predate a safety fix, and the machine has a desktop app whose version nothing here can match. Ask the user to open the Skills Manager app once, which republishes it.
    • A path from PATH — nothing was ever published here, so there is no stale copy to worry about: this is a CLI-only machine (a server install, a standalone download, a hand-built binary). Use it, but note it can be older than a desktop app if one is also installed.

    If nothing is printed at all, this skill doesn't apply — fall back to find-skills, or tell the user to install Skills Manager.

  2. Always pass --json when you parse output yourself. Pretty-printed output is for the user; JSON is for you. Errors include ok=false, a stable code, and message on stderr with a non-zero exit code.

"$SM" --json skills list

When a deployment is refused

A deploy that would overwrite something that is not ours is refused outright — nothing at those paths is deleted, and nothing else in the batch is applied. That failure is machine-readable, so report the actual paths rather than the sentence:

{"ok": false, "code": "TARGET_CONFLICT", "kind": "target_conflict",
 "message": "Refusing to deploy: 1 of 2 target(s) …",
 "details": {"conflicts": [{"path": "/Users/me/.claude/skills/db",
                            "reason": "is not a managed deployment"}]}}

Tell the user which path is in the way, that its contents are untouched, and offer the two ways out: adopt it into the library (skills adopt), or move it aside and retry. Never delete it for them.

The project commands refuse the same way, with these reasons:

reasonfromwhat to tell the user
exists and is not this library skillprojects deploythat directory holds something else; it was left alone and nothing in the batch was written
skills "…" (…) and "…" (…) would both be written hereprojects deploytwo library skills have the same directory name and only one can live there; ask the user which one, then deploy just that one
has content not in the library (…)projects undeploythe project copy may have edits, extra files (.gitignore, .git, links) or be a link the user made to somewhere else; projects import it first, or remove it with --force only if they say it can go
library copy differs from the project copyprojects importimporting would overwrite the library version; --force only if they want the project version to win
another copy of this skill also differs from the libraryprojects importseveral agents' copies were edited differently; they must pick one by hand

Never add --force on your own.

Mental model

There's one central library at ~/.skills-manager/skills/ that all agents share. Each skill has source metadata, preset membership, tags, and zero or more real deployments in agent directories. A preset is a reusable group; several presets may be deployed at the same time.

Keep these three states separate:

  • Library: install/remove controls whether Skills Manager owns the skill.
  • Preset membership: presets add-skill/remove-skill organizes the library only.
  • Deployment: skills deploy/undeploy and presets deploy/undeploy control what an agent can actually see.

Project deployments are a separate thing. projects deploy puts a library skill into one project's agent directory (e.g. <repo>/.claude/skills). It is not recorded as a deployment: skills status and deployed_to never show it; read it with projects show. Deploying a preset into a project copies its current members once and makes no lasting link.

Internally, presets are still stored as scenarios for backward-compatible Git Backup. The CLI and UI call them presets.

Install

# From skills.sh marketplace
"$SM" skills install vercel-labs/agent-skills@react-best-practices

# Any git URL (use /tree/branch/subpath form when the skill lives in a sub-directory)
"$SM" skills install https://github.com/anthropics/skills.git
"$SM" skills install https://github
阅读完整来源 ↗