菜单
Use when users need to inspect, enable, or disable NocoBase plugins with direct `nb plugin` commands only.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
Step-by-step playbook for developing a NocoBase plugin, covering scaffolding, server-side code (collections, APIs, ACL, migrations), client-side code (blocks, fields, actions, settings pages, routes, components), i18n, and verification. TRIGGER when: user asks to create, build, implement, or develop a NocoBase plugin, mentions 'NocoBase plugin', or describes a feature to be built as a NocoBase plugin. This skill contains NocoBase-specific conventions and templates that general coding cannot replicate — always invoke it instead of planning from scratch.
General-purpose NocoBase reference utilities covering cross-cutting topics such as evaluator engines, expression syntax, UID generation, and more. Use when you need authoritative reference information or reusable snippets that apply across multiple NocoBase features.
Use when users need to configure, inspect, test, or troubleshoot NocoBase notification management, including in-app message channels, email SMTP channels, workflow notification nodes, and notification send logs.
Use when the task hands over a prototype to reproduce in NocoBase — an HTML file, an image, or a link, INCLUDING the published form "Build a NocoBase app — X … Match the layout and signature visuals of this reference prototype: <url>" — or when someone says a built page "doesn't match the prototype / looks monotone / is ugly". A prototype/URL being present is what triggers this skill, EVEN WHEN the same prompt also says "build an app" — the verb "build" does not cancel the prototype. Skip it only when there is NO prototype at all: a bare "build me a CRM/app" → nocobase-app- discipline; a one-field edit / rename → nocobase-ui-builder. It turns "here is the prototype, build it" into a faithful app — analyze prototype, native CRUD, the right native block per region, then a screenshot-vs-prototype visual loop. Native-first; JS only inside a native container; never a full-page JS block. Mechanics live in nocobase-ui-builder, nocobase-data-modeling, nocobase-app-discipline.
| 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 |
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. |