Name: skill-management
Author: ZzjNoMercy

Imported from ZzjNoMercy/PuddingClaw (backend/skills/skill-management/SKILL.md). Install upstream with npx skills add ZzjNoMercy/PuddingClaw --skill skill-management. Copyright stays with the author.

Skill Management

Use the typed management tools instead of shell commands or direct writes under /skills. Never download and execute a Skill merely to inspect it.

Inspect

Call inspect_skill for the installed manifest, version metadata, file list and stable hashes. Report missing or invalid manifests without attempting repair.

Install

Call prepare_skill_install with the exact HTTPS source and optional ref/subpath.
Review the returned source, validation result, file diff and immutable plan digest.
When the result contains ui_commit_supported=true, stop after a successful prepare. The frontend renders the immutable plan as a confirmation card and commits it directly after the user clicks 确认并安装.

status=prepared means only that remote files were staged and validated. It does not mean the Skill was installed. Never describe it as installed or download-complete. When ui_commit_supported=true, never ask the user to reply with “确认” and do not call install_skill. If a short handoff is useful, say: “已暂存并校验，尚未安装；请在计划卡片中确认安装。” Legacy clients without structured UI support may call install_skill only after their explicit approval-gated continuation.

Do not overwrite an existing Skill through the install path.

Update

Inspect the installed Skill when its current version or integrity matters.
Call prepare_skill_update; omit the source only when the managed installation already records an authoritative source.
Review the baseline, diff and rollback information.
When ui_commit_supported=true, stop after a successful prepare. The frontend plan card owns confirmation and commit; do not ask for a chat reply and do not call update_skill. Legacy clients may use the explicit approval-gated Tool continuation.

Preparation may use the network but must not modify /skills. Commit operations must remain atomic and approval-gated. Never replace either phase with execute, write_file, or an ad-hoc package installer.

install_skill and update_skill remain compatibility tools for older clients that already implement an explicit one-time approval boundary. They are not the continuation step for the structured frontend plan card.

Install skill-management and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zzjnomercy-puddingclaw-skill-management", "kind": "skill", "name": "skill-management", "description": "Inspect, install, or update locally managed Agent Skills through a staged and approval-gated workflow. Use when the user asks to check a Skill version or integrity, install a Skill from a remote source, or update an installed Skill.", "publisher": "ZzjNoMercy", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Inspect, install, or update locally managed Agent Skills through a staged and approval-gated workflow. Use when the user asks to check a Skill version or integrity, install a Skill from a remote source, or update an installed Skill." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/ZzjNoMercy/PuddingClaw", "path": "backend/skills/skill-management/SKILL.md", "ref": "5c03ad3f68e2789d6d5c7110995b580d00abc832", "url": "https://github.com/ZzjNoMercy/PuddingClaw/blob/5c03ad3f68e2789d6d5c7110995b580d00abc832/backend/skills/skill-management/SKILL.md", "key": "ZzjNoMercy/PuddingClaw/backend/skills/skill-management/SKILL.md" } }, "instructions": "# Skill Management\n\nUse the typed management tools instead of shell commands or direct writes under\n`/skills`. Never download and execute a Skill merely to inspect it.\n\n## Inspect\n\nCall `inspect_skill` for the installed manifest, version metadata, file list and\nstable hashes. Report missing or invalid manifests without attempting repair.\n\n## Install\n\n1. Call `prepare_skill_install` with the exact HTTPS source and optional ref/subpath.\n2. Review the returned source, validation result, file diff and immutable plan digest.\n3. When the result contains `ui_commit_supported=true`, stop after a succe", "cost": { "context_tokens": 557 } }

skill-management

About