agentmods.dev

odoo-support-triage

odoo-support-triage is a skill for Claude Code from Viindoo/odoo-mcp-client. It costs 21 tokens per session (1,829 once invoked), scanned A, original, MIT.

A support-ticket triage guide for Odoo. It classifies a request as a configuration issue, bug, feature request, or training need, then drafts an internal action note and a customer-facing reply.

In plain words
What is it for?
Use it to assess Odoo support tickets, suggest likely causes from reported symptoms, prepare customer responses, and identify issues that need debugging or feature checks.
Why use it?
It helps support teams separate misunderstandings from real defects or missing features before sending the issue to developers. This makes replies more actionable without promising work that has not been approved.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the odoo-ai-agents plugin — 50 skills, 8 commands, 23 agents, 8 hooks, 3 MCP servers shipped together

not rated 9repo changed 17d ago A scan 21 tokens original MIT

Good fit Use it to assess Odoo support tickets, suggest likely causes from reported symptoms, prepare customer responses, and identify issues that need debugging or feature checks.

Compare 6 skills from other repositories ↓
View source ↗ Viindoo/odoo-mcp-client odoo-semantic.viindoo.com
Install

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.

Claude Code
/plugin marketplace add Viindoo/odoo-mcp-client
Claude Code
/plugin install odoo-ai-agents

Made for: Claude Code.

Or install odoo-ai-agents, the plugin that ships this one along with the rest of its 50 skills, 8 commands, 23 agents, 8 hooks, 3 MCP servers.

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

agentmods badge for odoo-support-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-support-triage/github.svg)](https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-support-triage)
Your own site
<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.

agentmods 80×15 button for odoo-support-triage

Your own site · 80×15
<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>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,829 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01829
Opus 5.5 $0.00008 $0.00732
Sonnet 5.5 $0.00004 $0.00366
Haiku 4.5 $0.00002 $0.00183

Measured 17d ago against content hash a2197fef93c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

plugins/odoo-ai-agents/skills/odoo-support-triage/SKILL.md · 151 lines

How it starts

The opening of the file, as written. The whole thing — 151 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-debug via NL-dispatch
  • Verifying whether a feature exists in Odoo -> hand off to odoo-feature-check via 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.yaml is the execution SSOT for the support-triage workflow. When the workflow-chaining fires 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 as odoo-qa-suite.)

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.

Read the full file on GitHub · 151 lines

Files

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.

Changes

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.

  1. 17d ago Changed a2197fef93c8
  2. 24d ago Changed 571ccd8a9a5a
  3. 1mo ago Changed · -13 lines · -217 tokens per session 891fe33a2e31
  4. 1mo ago Changed 80a95a7962a4
  5. 2mo ago First seen · 164 lines · 238 tokens per session scan A 253cc68a8360

Subscribe to this mod's changes

odoo-support-triage is a skill published in the GitHub repository Viindoo/odoo-mcp-client (9 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 1,829 once invoked, about $0.0001 per session on Opus 5.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.

Project management
Related

odoo-support-triage compared with skills from other repositories

odoo-support-triage next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
odoo-support-triageViindoo/odoo-mcp-clientSkill92d agoMITA21Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill100ktodayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k3d agoMITA200Claude Code, Codex
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill315k6d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code