odoo-user-guidelisted

Use when the user wants END-USER usage documentation / how-to guides for an Odoo flow — "viết hướng dẫn sử dụng", "tạo tài liệu hướng dẫn cho nhân viên", "làm guide thao tác", "document how to <do X> in Odoo", "screenshot/step-by-step guide", "user manual cho luồng <model>". The AGENT drives the real Odoo UI live through an MCP browser tool (claude-in-chrome / Playwright MCP) — observing each page semantically (accessibility tree), clicking by visible label, screenshotting and narrating — grounded by Odoo metadata + RPC so it stays correct, and proven by reading the resulting state at the backend. Then it renders a Markdown guide (guide.md + screenshots/, or self-contained HTML). Deterministic, ground-truth-first, re-runnable — NOT a blind hand-written selector script. Default: dev/UAT (sandbox) db. NOT for QWeb PDF business documents — that is odoo-reports.
tuanle96/odoo-ai-skills · ★ 4 · Web & Frontend · score 62

Install: claude install-skill tuanle96/odoo-ai-skills

# odoo-user-guide — instance-verified end-user guides Generic recorders (Scribe/Tango/Guidde) document **what one person did once**. This skill documents **what this Odoo instance lets this role do now** — and proves it by executing the flow on the running instance. The fast, accurate way to build one is **the agent drives the live UI once** through an MCP browser tool. The bottleneck in doc generation is *guessing the click-path in code before seeing the UI*; don't. The agent observes each page (accessibility tree), clicks by **visible label**, adapts to wizards / locked records / banners like a human, and screenshots as it goes. Odoo metadata + RPC keep it correct; reading the backend state makes it a proof. > Scripts capture FACTS (grounding, test data, proof, cleanup, rendering). The agent > supplies the JUDGEMENT (driving the UI, and writing clear plain-language prose). ## The playbook (primary, agent-driven) ```bash SK=skills/odoo-user-guide/scripts export ODOO_GUIDE_PASSWORD='***' U="--url https://odoo1.example.dev --db DEMO --login tuan.le" ``` 1. **PREP — ground + obtain a record to document** (deterministic): `$SK/odoo-guide-prep "xác nhận đơn bán hàng" $U --sandbox` Reads the real form-view buttons + effective access over RPC and writes `guides/<id>/flow.json` (form URL, the button + its label, expected end state) + an `evidence.json` skeleton + a `screenshots/` dir. **Generic across models:** - `--model <model> --record-id <id>` → document an