메뉴
Adds a reference documentation file — a spec, format reference, or design doc — under a plugin's references/ directory. Use when adding background documentation that plugin skills and commands should cite. Reference docs are plain Markdown, not a loadable component type.
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 | add-reference |
| description | Adds a reference documentation file — a spec, format reference, or design doc — under a plugin's references/ directory. Use when adding background documentation that plugin skills and commands should cite. Reference docs are plain Markdown, not a loadable component type. |
Adds a reference document to a plugin bundle.
plugins/<plugin>/
references/
<doc-name>.md ← a reference document
References are plain Markdown files. They are NOT components (not skills, not
commands, not agents) — they are documentation that skills and commands can
reference by path. The core plugin has references/zcode-native-format.md
as an example.
Ask the user for:
plugins/<plugin>/ is present).api-contract,
design-tokens).Create the directory if it does not exist:
mkdir -p zcode_tools/marketplaces/<mp>/plugins/<plugin>/references
Write the reference file:
zcode_tools/marketplaces/<mp>/plugins/<plugin>/references/<name>.md
Start with a top-level # <name> heading. Write the content as clear,
dense reference documentation (tables, code blocks, field lists). This is
NOT a procedure — it is a spec that other skills cite.
Remind the user that references are NOT declared in plugin.json — they
are discovered by convention (any .md under references/).
Validate the file exists and is non-empty:
test -s zcode_tools/marketplaces/<mp>/plugins/<plugin>/references/<name>.md
Run the installer plan to confirm nothing broke:
cli-tools/scripts/install.sh install --marketplace <mp> --platform macos --plan
plugin.json — convention discovery..md file per reference topic.