Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Viindoo/odoo-mcp-client/plugin install odoo-ai-agentsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-support-triage)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-support-triage"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-support-triage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-support-triage"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-support-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00238 | $0.02072 |
| Opus 5 | $0.00119 | $0.01036 |
| Sonnet 5 | $0.00048 | $0.00414 |
| Haiku 4.5 | $0.00024 | $0.00207 |
Grade A, and why
odoo-support-triage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Odoo support triage for a partner or implementation team - distinguishes config misunderstandings, genuine bugs, feature gaps, and training issues. Dual audience: the internal team (root cause + action) and the end customer (respectful, actionable reply). Produces both in one pass; the customer reply never promises fixes the team cannot deliver.
Out of Scope
- Deep code debugging across multiple modules -> hand off to
odoo-debugvia NL-dispatch - Verifying whether a feature exists in Odoo -> hand off to
odoo-feature-checkvia NL-dispatch - Responding to sales objections ("can Odoo even do X?") -> use
odoo-objection-handling - Gap analysis for a new project or scope estimation -> use
odoo-gap-analysis - Full upgrade risk assessment -> use
odoo-risk-overview - Writing marketing content or product announcements -> use
odoo-content-draft
Standalone-first fallback
Operates standalone by default. All classification and root-cause hinting run on the ticket text. OSM/MCP NOT called automatically.
On feature-request with grounding needed → NL-dispatch to odoo-feature-check. On bug with runtime symptoms → NL-dispatch to odoo-debug. Email tone mirrors odoo-deal-followup B2B style.
If OSM unreachable: all phases complete via training knowledge; append caveat that feature/module claims are unverified.
Execution SSOT
The
workflows/support-triage.workflow.yamlis the execution SSOT for the support-triage workflow. When theworkflow-chainingfires this skill it follows the phase sequencing declared in that YAML. The phase descriptions below document the inline behavior of this skill as invoked by the runner - they do not duplicate the orchestration logic. (Same pattern asodoo-qa-suite/SKILL.md.)
Phase 0 - Collect ticket input
Resolve series, profile, and module scope per
${CLAUDE_PLUGIN_ROOT}/snippets/project-facts-resolution.md before asking for any project fact.
Ask only for still-missing fields:
Required: ticket description or customer message (accepted as structured text already in request, OR a file path - Read it; never ask to re-paste); Odoo series - resolved per ${CLAUDE_PLUGIN_ROOT}/snippets/project-facts-resolution.md, asked for only when every rung missed. An unresolved series is NEEDS_CONTEXT, never the literal "unknown": version-relative triage (is this a bug or a known behavior of that series?) cannot be graded without it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 164 lines · 238 tokens per session scan A 253cc68a8360
odoo-support-triage is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 5d ago), licensed MIT. It adds 238 tokens to every session and 2,072 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.