nocobase-plugin-manage

name	nocobase-plugin-manage
description	Use when users need to inspect, enable, or disable NocoBase plugins with direct `nb plugin` commands only.
argument-hint	[action: inspect|enable|disable] [plugin...] [env?: name]
allowed-tools	Bash, Read, Grep, Write
owner	platform-tools
version	2.0.1
last-reviewed	"2026-04-29T00:00:00.000Z"
risk-level	medium

Goal

Provide a deterministic plugin workflow using only direct nb plugin commands:

• nb plugin list [--env <env>]
• nb plugin enable [--env <env>] <plugin...>
• nb plugin disable [--env <env>] <plugin...>

This skill must not route plugin operations through wrapper scripts or fallback channels.

Scope

• Inspect plugin inventory/state from CLI runtime (nb plugin list [--env <env>]).
• Enable plugins with nb plugin enable [--env <env>] <plugin...>.
• Disable plugins with nb plugin disable [--env <env>] <plugin...>.
• Always perform readback with nb plugin list after writes.

Non-Goals

• Do not use docker compose exec ... yarn nocobase plugin ....
• Do not use API action routes as fallback.
• Do not use legacy ctl commands or wrapper scripts for plugin operations.
• Do not support install/remove in this skill version.

Input Contract

Input	Required	Default	Validation	Clarification Question
action	yes	none	one of inspect/enable/disable	"Which action should I run: inspect, enable, or disable?"
plugins	enable/disable: yes	none	non-empty string array	"Which plugin(s) should be changed?"
runtime_env_name	no	current env	configured CLI env name	"Which env should I target?"
base_dir	no	current working directory	existing path	"Which directory should nb commands run in?"
execution_mode	no	safe	one of safe/fast	"Use safe mode or fast mode?"
verify.timeout_seconds	no	90	integer 10..600	"What verification timeout should I use?"

Rules:

• Keep compact invocation: Use $nocobase-plugin-manage <action> [plugin...].
• safe mode requires pre-state + post-state readback.
• If user says "you decide", use defaults above.

Mandatory Clarification Gate

• Max clarification rounds: 2
• Max questions per round: 3
• Before enable/disable, plugins must be resolved.
• If required inputs are missing, stop mutation and ask.

Workflow

1. Parse request and normalize to inspect/enable/disable.
2. Capture pre-state via nb plugin list when execution_mode=safe.
3. Execute action with direct command:

• inspect: nb plugin list [--env <env>]
• enable: nb plugin enable [--env <env>] <plugin...>
• disable: nb plugin disable [--env <env>] <plugin...>

4. Readback polling via nb plugin list until timeout.
5. Return structured output.

Safety Gate

• High-impact actions:
• disable auth/ACL/system-critical plugins
• batch disable in shared environments
• Secondary confirmation template:
• "Confirm execution: {{action}} for {{plugins}}. Type confirm to continue."
• Rollback guidance:
• failed disable: run nb plugin enable [--env <env>] <plugin...>
• failed enable: run nb plugin disable [--env <env>] <plugin...> (only when user requests rollback)

Verification Checklist

• action and plugins resolved.
• Command path uses direct nb plugin only.
• Pre-state captured in safe mode.
• Post-state readback captured.
• enable => plugin shows enabled=true.
• disable => plugin shows enabled=false.
• Timeout reported as pending_verification.

Minimal Test Scenarios

1. inspect uses nb plugin list.
2. enable uses nb plugin enable then readback by nb plugin list.
3. disable uses nb plugin disable then readback by nb plugin list.
4. Missing plugin input blocks mutation with clarification.

Output Contract

Always return:

• request
• commands
• pre_state
• post_state
• verification (passed|failed|pending_verification)
• assumptions
• next_steps

Reference Loading Map

Reference	Use When
V1 Runtime Contract	Mapping plugin actions to final nb plugin commands.
Test Playbook	Checking inspect/enable/disable behavior and fallback guarantees.

References

• V1 Runtime Contract
• Test Playbook