菜单
Use when developing or iterating on installed skill-manager skills and plugins through project-local worktrees and the skill-dev CLI.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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 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__.
| name | skill-dev-skill |
| description | Use when developing or iterating on installed skill-manager skills and plugins through project-local worktrees and the skill-dev CLI. |
| skill-imports | [{"unit":"skill-manager","path":"references/cli.md","reason":"Defines sync --from, force-scripts replay, and managed CLI cleanup for skill-dev worktrees.","section":"runtime"}] |
Use skill-dev when a user wants to edit an installed skill-manager skill
or plugin without directly modifying the installed store copy.
The CLI creates a project-local worktree under skill-dev/<unit>, keeps
that root ignored by the project's git repository, and delegates merge-back
to skill-manager:
skill-dev open <unit>
skill-dev status <unit>
skill-dev git <unit> -- status
skill-dev sync <unit>
skill-dev close <unit> --merge
Prefer skill-dev sync <unit> to apply edits while leaving the worktree
open. Prefer skill-dev close <unit> --merge when finishing a development
session.
If a worktree has a skill-script: CLI installer and you need to replay
it without changing script bytes, run the delegated command directly
with skill-manager sync <unit> --from skill-dev/<unit> --merge --yes --force-scripts. Named sync forces scripts for that unit only; script
stdout/stderr is written under $SKILL_MANAGER_HOME/logs/skill-scripts/.
skill-dev sync <unit> delegates to:
skill-manager sync <unit> --from <project>/skill-dev/<unit> --merge --yes
If the worktree changes files under skill-scripts/, normal sync reruns
the corresponding skill-script: CLI dependency because the fingerprint
changes. To replay an unchanged script from the worktree, call the
underlying command directly with --force-scripts:
skill-manager sync <unit> --from <project>/skill-dev/<unit> --merge --yes --force-scripts
This skill installs the skill-dev binary through a skill-script:
dependency. Uninstalling skill-dev-skill removes that managed binary
and cli-lock.toml row only when no other installed unit claims the
same backend/tool.
These workflow ids are shared with the CLI metadata catalog and the TLA+ program model. Use this table as routing guidance, then run the help command for exact syntax.
| Workflow id | Use when | Help |
|---|---|---|
force-skill-scripts | replaying an unchanged worktree installer for one unit | skill-manager sync --help |
install-local-unit | installing the local worktree as a managed unit | skill-manager install --help |
project-env | syncing project-local envs while developing skills | skill-manager env sync --help |
sync-from-local-source | applying a worktree back to the installed unit | skill-manager sync --help |