菜单
Composes a complete ZCode plugin from a described intent — a metadata-only manifest plus the right mix of skills, commands, agents, hooks, and MCP config — and registers it in the marketplace. Use when starting a plugin from a goal rather than adding one component at a time.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Authors a ZCode slash command as commands/<name>.md in a marketplace. Use when adding or defining a slash (/) command, including nested colon-separated commands. For a SKILL.md use add-skill; for a subagent use add-agent.
Scaffolds a new self-contained ZCode marketplace — a complete ~/.zcode setup — under zcode_tools/marketplaces/. Use when creating a brand-new setup or profile such as nddev-builder or nddev-designer, or bootstrapping a marketplace directory from scratch.
Scaffolds a new self-contained plugin bundle inside a ZCode marketplace and registers it in marketplace.json. Use when adding a plugin to a marketplace, or grouping skills, commands, and agents into one installable bundle.
Adds a model provider to a marketplace's config template. Use when adding or configuring an LLM provider — OpenAI, Anthropic, or a custom OpenAI-compatible endpoint — or wiring provider models, base URL, or API-key placeholders into a ZCode setup.
Authors a ZCode skill (SKILL.md) inside a plugin bundle or at user scope. Use when adding a skill or teaching the agent a reusable workflow. For a slash command use add-command; for a subagent use add-agent.
Runs an isolated install-and-verify loop for a marketplace using temporary HOME and ZCODE_HOME, proving components flatten and load without touching live ~/.zcode. Use to behaviorally test a plugin during development, after static validation.
| name | scaffold-plugin |
| description | Composes a complete ZCode plugin from a described intent — a metadata-only manifest plus the right mix of skills, commands, agents, hooks, and MCP config — and registers it in the marketplace. Use when starting a plugin from a goal rather than adding one component at a time. |
Turn a described capability into a complete, install-ready ZCode plugin bundle in
one pass, then hand off to validate-components. This orchestrates the focused
add-* skills; it does not replace them.
Use when the input is an intent ("a plugin that reviews Terraform and blocks
unsafe applies") rather than a single component. To add one skill or command to
an existing plugin, use the matching add-* skill directly.
.zcode-plugin/plugin.json plus components under
convention directories. ZCode 3.5.2 executes only commands, skills,
hooks, mcpServers, and user-scope agents; never scaffold the inert
lspServers/outputStyles/channels/settings fields or manifest component
arrays. See nddev-builder-orientation.skills/, commands/, and
agents/ into ~/.zcode/{skills,commands,agents} and fails closed on a
duplicate basename, so every component this skill emits must have a
repo-unique name.add-marketplace if none fits, then
scaffold the empty bundle with add-plugin (manifest + directories + README +
marketplace entry). For a bundle that must also run in Claude Code, use
add-plugin's optional dual .zcode-plugin + .claude-plugin manifest.add-skill, add-command,
add-agent, add-hook, add-mcp-server, add-instructions,
add-reference, add-tool, add-provider. Keep every basename unique across
the whole repository.name@marketplace strings, with
cross-marketplace dependencies listed in allowCrossMarketplaceDependenciesOn.validate-components, then the non-mutating
install.sh install --setup <mp> --plan gate. Run devtest-plugin for a
behavioral pass.add-plugin step 8 (one SemVer across the five
version sources plus CHANGELOG.md) if the bundle ships.validate-components before shipping.