nocobase-plugin-manage
Use when users need to inspect, enable, or disable NocoBase plugins with direct `nb plugin` commands only.
What this skill does
# 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](references/v1-runtime-contract.md) | Mapping plugin actions to final `nb plugin` commands. |
| [Test Playbook](references/test-playbook.md) | Checking inspect/enable/disable behavior and fallback guarantees. |
# References
- [V1 Runtime Contract](references/v1-runtime-contract.md)
- [Test Playbook](references/test-playbook.md)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.