القائمة
Enables or disables a registered plugin in a marketplace's config template. Use when a plugin is registered in marketplace.json but not active, or when toggling a plugin on or off for a setup.
التثبيت باستخدام 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 | enable-plugin |
| description | Enables or disables a registered plugin in a marketplace's config template. Use when a plugin is registered in marketplace.json but not active, or when toggling a plugin on or off for a setup. |
Populates the enabledPlugins map in cli-config.template.json so ZCode
knows which plugins to activate.
ZCode's cli/config.json has:
{
"plugins": {
"enabled": true,
"enabledPlugins": {
"plugin-name@marketplace-name": true
}
}
}
plugins.enabled (bool) — master switch for the plugin system. Must be
true (the default in every marketplace template).plugins.enabledPlugins (object) — per-plugin enable map. The key format is
<plugin-name>@<marketplace-name>. Value true = enabled, false =
explicitly disabled. Absent = not enabled.If enabledPlugins is {} (empty), no plugins are active even if they are
registered in marketplace.json. That is appropriate only for a deliberately
plugin-free profile. A marketplace that advertises bundled plugin capability
must explicitly enable the intended plugin keys; nddev-builder therefore
ships with core@nddev-builder: true.
Worked example: to enable the core plugin in the nddev-builder
marketplace:
{
"plugins": {
"enabled": true,
"enabledPlugins": {
"core@nddev-builder": true
}
}
}
Ask the user for:
Read marketplace.json and confirm the plugin is registered:
python3 -m json.tool \
zcode_tools/marketplaces/<mp>/marketplace.json
If the plugin is not in the list, tell the user to add it first (follow the
add-plugin skill).
Read cli-config.template.json and locate plugins.enabledPlugins.
Set the key <plugin-name>@<marketplace-name>:
true.false (or remove the key entirely).Write the updated JSON (preserve _comment, indent=2, trailing newline).
Validate:
python3 -m json.tool \
zcode_tools/marketplaces/<mp>/cli-config.template.json
cli-tools/scripts/install.sh install --marketplace <mp> --platform macos --plan
plugin-name@marketplace-name (NOT plugin-name alone).plugins.enabled must remain true — do not disable the master switch._comment field and all other keys in the template.