skills/nocobase-plugin-manage/SKILL.md
Use when users need to inspect, enable, or disable NocoBase plugins with direct `nb plugin` commands only.
npx skillsauth add nocobase/skills nocobase-plugin-manageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
nb plugin list [--env <env>]).nb plugin enable [--env <env>] <plugin...>.nb plugin disable [--env <env>] <plugin...>.nb plugin list after writes.docker compose exec ... yarn nocobase plugin ....install/remove in this skill version.| 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:
Use $nocobase-plugin-manage <action> [plugin...].safe mode requires pre-state + post-state readback.23enable/disable, plugins must be resolved.inspect/enable/disable.nb plugin list when execution_mode=safe.inspect: nb plugin list [--env <env>]enable: nb plugin enable [--env <env>] <plugin...>disable: nb plugin disable [--env <env>] <plugin...>nb plugin list until timeout.{{action}} for {{plugins}}. Type confirm to continue."nb plugin enable [--env <env>] <plugin...>nb plugin disable [--env <env>] <plugin...> (only when user requests rollback)action and plugins resolved.nb plugin only.safe mode.enable => plugin shows enabled=true.disable => plugin shows enabled=false.pending_verification.inspect uses nb plugin list.enable uses nb plugin enable then readback by nb plugin list.disable uses nb plugin disable then readback by nb plugin list.Always return:
requestcommandspre_statepost_stateverification (passed|failed|pending_verification)assumptionsnext_steps| Reference | Use When |
|---|---|
| V1 Runtime Contract | Mapping plugin actions to final nb plugin commands. |
| Test Playbook | Checking inspect/enable/disable behavior and fallback guarantees. |
tools
Use when a NocoBase task requires AI employee lifecycle work such as discovering existing employees, judging fit, creating a dedicated employee, or configuring profile, prompt, model, skills, tools, or knowledge base before another skill binds it to a UI surface.
tools
Use when users need to inspect, create, revise, enable, or diagnose NocoBase workflows through the `nb` CLI, including trigger selection, node-chain changes, version safety checks, and execution troubleshooting.
tools
DEFAULT entry point for NocoBase Modern UI authoring or tweaks: new pages, blocks, menu items, and localized edits to blocks, fields, actions, layouts, or reactions on an already-running app via backend flow-surfaces through nb api. Also handles AI employee / AI assistant action placement on UI surfaces. Hand off employee lifecycle work such as discovering, judging, creating, or configuring profile, prompt, model, skills, tools, or knowledge base to nocobase-ai-employee, then return for the UI write. Only hand off to nocobase-dsl-reconciler when the user explicitly asks for DSL, YAML, git, or cli push workflow. Does not handle ACL, data modeling, workflow orchestration, browser reproduction, page error postmortems, or non-Modern page navigation.
data-ai
Create and manage NocoBase data models through the available data-modeling surface. Use when users want to inspect or change collections, fields, relations, or view-backed schemas in a NocoBase app.