NV oOS Gateway

View saved version →

---
name: commerce-desk
description: Explore WooCommerce store capabilities exposed by the NV oOS demo site over the fleet gateway — catalog and order lookups through namespaced demo_* tools, when the demo site exposes them.
---

Work against the connected `nvoos_gateway` MCP server. Store tools, when the
public demo site exposes them, appear in `tools/list` with the `demo_`
prefix (for example `demo_get_woo_products`).

Rules:

- Check `tools/list` first — the demo site's operator decides which store
  tools the gateway exposes; do not assume WooCommerce tools exist.
- Prefer read-only lookups (products, orders the demo exposes publicly).
- Never place orders, change prices, refund, or modify store data without
  explicit user confirmation and the exact record IDs.
- Financial figures are demo data — label them as such in every answer.

View saved version →

---
name: content-studio
description: Research and draft content using the NV oOS demo site's capabilities over the fleet gateway — deep research with citations, then drafting grounded in the demo site's public content.
---

Work against the connected `nvoos_gateway` MCP server. Every tool name carries
the `demo_` prefix.

Workflow:

1. **Research** — use `demo_deep_research` for topic discovery with
   citations; prefer `run_mode: "background"` for standard/comprehensive
   depth (the tool is long-running; immediate mode may hit client-side
   timeouts).
2. **Ground in site content** — when the demo site exposes content tools
   (check `tools/list` first), cross-reference findings with the site's
   published posts and pages before drafting.
3. **Draft** — write in the user's requested voice and cite sources with
   links.

Rules:

- Never publish or create content without explicit user confirmation and
  review of the exact draft.
- Only use tools present in `tools/list`; if the demo site does not expose a
  content tool, say so rather than assuming one exists.
- Deep research is open-world: attribute claims to cited sources and do not
  present uncited material as fact.

View saved version →

---
name: gateway-site-operations
description: Explore and inspect the public NV oOS demo site through the fleet MCP gateway — environment status, capabilities, and the namespaced demo_* tool surface. Read-first workflows for anyone evaluating NV oOS.
---

Work against the connected `nvoos_gateway` MCP server. The gateway exposes the
public NV oOS demo site (`demo`) with tool names prefixed `demo_`.

Read-only tools first:

- `demo_get_environment_status` — the demo site's live environment report
  (WordPress version, active plugins, configured AI providers). Ground every
  claim about the demo site in this tool's output.
- `demo_deep_research` — long-running web research with citations. For
  standard/comprehensive depth prefer `run_mode: "background"`; immediate
  mode may exceed client-side tool timeouts.
- Discover anything else available with `tools/list` and read each tool's
  schema before calling it.

Rules:

- The gateway scopes access per site: this plugin only reaches the public
  `demo` site. Never claim access to other sites or clients.
- Never call a destructive or write tool without explicit user confirmation,
  including the exact IDs that will be affected.
- A failing site surfaces as `_meta.gateway.errors` — report degradation
  honestly instead of guessing.
- Quote tool names with their `demo_` prefix; do not invent tools that are
  not in the `tools/list` response.