Update to NV oOS Gateway

{
  "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.",
  "included_files": [],
  "name": "gateway-site-operations",
  "skill_md_contents": "---\nname: gateway-site-operations\ndescription: 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.\n---\n\nWork against the connected `nvoos_gateway` MCP server. The gateway exposes the\npublic NV oOS demo site (`demo`) with tool names prefixed `demo_`.\n\nRead-only tools first:\n\n- `demo_get_environment_status` — the demo site's live environment report\n  (WordPress version, active plugins, configured AI providers). Ground every\n  claim about the demo site in this tool's output.\n- `demo_deep_research` — long-running web research with citations. For\n  standard/comprehensive depth prefer `run_mode: \"background\"`; immediate\n  mode may exceed client-side tool timeouts.\n- Discover anything else available with `tools/list` and read each tool's\n  schema before calling it.\n\nRules:\n\n- The gateway scopes access per site: this plugin only reaches the public\n  `demo` site. Never claim access to other sites or clients.\n- Never call a destructive or write tool without explicit user confirmation,\n  including the exact IDs that will be affected.\n- A failing site surfaces as `_meta.gateway.errors` — report degradation\n  honestly instead of guessing.\n- Quote tool names with their `demo_` prefix; do not invent tools that are\n  not in the `tools/list` response.\n"
}