---
name: vidext-operator
description: Use Vidext Operator MCP to research connected sources, create and revise training modules, inspect module workflow status, and continue module workflows.
---

# Vidext Operator

Use this skill when a user wants to create, inspect, continue, or edit Vidext learning operations through the remote operator MCP server.

## Capabilities

- Ask the organization operator to research connected sources, organization wiki context, and module workflow status.
- Start or continue module outlining, module builds, and existing-module edits through the operator agent; requests to create a course are fulfilled as modules.
- Inspect recent modules and long-running outline/build status.
- Continue an existing operator conversation with a chat id or focus a turn on an active module id.

## Run Envelope

A single operator agent handles every turn and selects its own tools. Every successful `ask_vidext_operator` response includes a `run` envelope with `modelId`, `mutationLevel` (`read` when only read tools ran, `write` when any write tool ran), `availableToolNames`, `requestId`, `traceId`, normalized module/planner/builder/course ids, and `nextAction` when polling is useful.

## Safe Usage

- Send the user's request as a single prompt; the operator decides which tools to run.
- The operator only creates, builds, revises, rebuilds, or edits module work when the user's request clearly asks for it, and asks for explicit confirmation before destructive changes.
- Pass `activeModuleId` when the target module is already known.
- Remote MCP callers use `ask_vidext_operator`. Agents already running inside an authenticated Vidext browser page can instead use the browser-local `vidext.ask_operator` WebMCP tool, which passes the current workspace and module context automatically.

## Polling

- Builds and outline generation can be asynchronous. When the response `run.nextAction` is `poll_outline_status` or `poll_build_status`, call `ask_vidext_operator` again with the same `chatId`, the returned `activeModuleId` or module id, and a short status prompt.
- Stop polling when the operator reports the outline/build work is ready, completed, failed, or waiting on user approval.

## Entry Points

- Read product context from /llms.txt and /developers.
- Discover MCP metadata at /.well-known/mcp.
- Connect to the operator MCP transport at /api/mcp/operator after OAuth authorization.
- On authenticated app pages, use browser WebMCP tools from `document.modelContext` for page navigation, module lookup, and context-aware `vidext.ask_operator` turns.