skill-manager

Author and maintain installable skill-manager units: skills, plugins, doc-repos, and harnesses. Read this before editing any file inside a unit — SKILL.md, its frontmatter or description, skill-manager.toml, plugin.json, harness.toml, or a references/ page — not only when creating one from scratch. Use when making a directory installable by skill-manager, choosing a unit kind, scaffolding a unit, writing or reviewing unit manifests/TOML, adding CLI or MCP dependencies, wiring references, validating install/bind/instantiate round-trips, preparing optional registry metadata, or shipping an edit to an already-installed unit so it reaches $SKILL_MANAGER_HOME (commit, push, then `skill-manager sync`). Detailed schemas live in references for skills, plugins, doc-repos, harnesses, scaffolding, coordinates/distribution, dependencies, bindings/sync, and skill-script.

Search, install, bind, sync, and remove skill-manager-managed units: skills, plugins, doc-repos, and harnesses; manage skill projects, project child homes, CLI tools, and MCP tools. Use when the user asks to find, add, remove, inspect, bind, unbind, instantiate, sync, upgrade, or resolve one of those surfaces. CLI syntax is authoritative in `skill-manager --help`; project workflows live in `references/projects.md`; gateway operations are authoritative in `references/virtual-mcp-gateway.md`; agent workflow routing lives in `references/workflows.md`.

Use when developing or iterating on installed skill-manager skills and plugins through project-local worktrees and the skill-dev CLI.

Use when demonstrating a contained skill inside an example plugin.

Use when demonstrating the minimum shape of a skill-manager skill.

Work with the test-graph validation system -- scaffold a test_graph project into a user repo, add JBang/uv nodes, compose graphs in build.gradle.kts, discover/plan them, run one graph or all graphs, and aggregate reports. Use whenever the user asks to set up validation nodes, compose a validation graph, run test_graph, or extend an existing test_graph project.

test_graph fixture — exercises a stdio MCP dependency at scope __SCOPE__.

test_graph fixture — exercises an MCP dependency at scope __SCOPE__.

Integration-test skill about code formatting, style, and linting — used as the target of a sponsored campaign keyed on "format" and the "style" category.

Test fixture exercising the npm / uv / docker MCP load types end-to-end through skill-manager's install pipeline. Not for agent use.

Partner skill claiming an MCP server name shared with the umbrella plugin. Used by test_graph.sources.smoke.plugin.PluginUninstalledMixedOrphans to verify non-orphan deps survive plugin uninstall.

Integration-test skill about code review, pull requests, and diff analysis — used as the target of a sponsored campaign keyed on "review" and "code-review".

Integration-test fixture that declares a skill-script CLI dependency. The bundled install script touches a sentinel file under $SKILL_MANAGER_BIN_DIR so the smoke graph can assert the backend ran end-to-end.

Inner sub-skill of skill-script-umbrella-skill. Declares a skill-script CLI dep so the smoke graph can assert the backend runs transitively when only the umbrella is installed.

Integration-test fixture that references a nested skill-script-inner sub-skill via file:. Used by the smoke graph to prove that the skill-script CLI backend fires for transitively installed sub-skills, not just the top-level install target.

Contained skill of umbrella-plugin fixture — carries its own CLI + MCP deps that the plugin's install pipeline walks and registers.

Integration-test sub-skill that declares an npm CLI dependency.

Integration-test sub-skill that declares a pip CLI dependency.

Integration-test umbrella skill that transitively depends on two sub-skills via file references, each carrying a different CLI backend.

Contained skill of hello-plugin — demonstrates a plugin's nested skill layout.

Example skill demonstrating skill-manager — CLI deps, skill refs, MCP via gateway.