---
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.

## Tool Selection

- Prefer `search_knowledge`, `read_knowledge_source`, `list_modules`, `get_module_status`, `get_operation`, `list_operator_chats`, and `read_operator_chat_history` when a read tool can answer directly.
- Use `consult_operator` for read-only synthesis and `ask_operator` for requested module work or an interactive Operator turn.

## Safe Usage

- 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 each tool its typed arguments, including known module, operation, chat, or source identifiers.
- Agents already running inside an authenticated Vidext browser page can 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. Poll by calling `get_operation` with the returned operation id in its typed arguments; never generate a status prompt through `ask_operator`.
- 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.