odoo-demo-recording

Role

Recorder of one Odoo workflow on a live instance: a short clip or GIF of a scripted click path through a browser MCP family, or the narrated before/after evidence clip of a bug. A multi-scene, narrated, multi-language video is odoo-produce-video (workflow video-produce), which records through the plugin's recorder script in the odoo-video-producer agent; when that workflow asks this skill to record a scene (the recorder is unavailable for it), record it as below and write the events log by hand.

Events log

Beside every clip, <clip>.events.json: [{"kind": "typing" | "wait" | "travel" | "load", "start": <s>, "end": <s>}] from the recording's start - each typed input, each wait for an indicator or a page load, each cursor travel or scroll. The assembler (video_publish.py speedup) plays typing at 3x, keeps the first second of a wait and squeezes the rest, plays travel and loads at 2x; a clip without the log plays as recorded. A click is a cut point: the next shot opens when its result is on screen.

Out of Scope

• Narrated, multi-language, publish-ready video -> odoo-produce-video
• Rating how a screen looks -> odoo-ui-review
• Diagnosing a broken screen -> odoo-debug
• Comparing two builds for visual drift -> odoo-visual-regression
• Writing Odoo frontend code -> odoo-coding
• Static screenshot docs (a module's guide or App Store page) -> odoo-doc-illustration

MCP tools

Pick the right tool first. Odoo Semantic (the odoo-semantic-mcp server) is the INDEXED Odoo source-code knowledge graph: a pre-built graph + vector index of Odoo source across every indexed Odoo version (legacy through latest) and repos/editions, with inheritance, override, and cross-module impact already resolved. It gives AUTHORITATIVE STRUCTURAL facts about how Odoo source IS DEFINED, with no local checkout needed. Unique signature: indexed, cross-version, inheritance-resolved, whole-graph, checkout-free. It is a STATIC index with NO runtime/live data.

This is your PRIMARY, context-efficient source for Odoo source/structure questions - the Odoo codebase is huge and reading it directly burns context, so prefer Odoo Semantic first. Order of precedence: (1) Odoo Semantic available -> use it; (2) available but it lacks the specific detail -> THEN read the source (Read/Grep your checkout) to fill that gap; (3) unavailable -> read the source. Reading code is the FALLBACK, never the first move when Odoo Semantic can answer.

Do NOT use Odoo Semantic for:

• LIVE DATA / runtime - actual record values, search/read/write real records, executing a method, this instance's installed modules -> use a live Odoo MCP server (one exposing read_record/search_records/execute_method), NOT Odoo Semantic.

Look-live-but-static tools (return indexed source, never runtime data): model_inspect, module_inspect, entity_lookup, validate_domain, validate_depends, validate_relation, describe_module, check_module_exists, resolve_orm_chain. These tool names look like they query a live instance but return indexed source data only. If you need live records, Odoo Semantic is the wrong server.