CtrlK
BlogDocsLog inGet started
Tessl Logo

odoo-xml-views-builder

Expert at building Odoo XML views: Form, List, Kanban, Search, Calendar, and Graph. Generates correct XML for Odoo 14-17 with proper visibility syntax.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/odoo-xml-views-builder/SKILL.md

The canonical home for this skill is odoo-xml-views-builder in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides solid, actionable XML examples for form and kanban views with version-aware best practices, which is its main strength. However, it over-promises by claiming coverage of Calendar, Graph, and Search views without providing examples or references for them. The introductory sections ('Overview', 'When to Use', 'How It Works') add padding without much value, and there's no validation guidance for verifying generated XML works correctly in Odoo.

Suggestions

Remove or drastically shorten the 'Overview', 'When to Use This Skill', and 'How It Works' sections — they explain things Claude already knows and don't add actionable value.

Add concrete XML examples for Search, Calendar, and Graph views (even brief ones), or remove those claims from the overview to avoid over-promising.

Add a validation step: e.g., 'After adding the XML, upgrade the module with `-u module_name` and check Odoo logs for view parsing errors.'

Show a side-by-side comparison of attrs (v14-16) vs inline expression (v17) syntax for the same visibility condition — this is the key version-specific knowledge Claude needs.

DimensionReasoningScore

Conciseness

The 'Overview' section restates things Claude already knows (what XML views are, what visibility modifiers are). The 'When to Use This Skill' and 'How It Works' sections add little actionable value and pad the content. The examples and best practices sections are reasonably efficient, but overall there's noticeable fat that could be trimmed.

3 / 5

Actionability

The two XML examples are complete, copy-paste ready, and cover common view types (form with tabs, kanban). Best practices give concrete do/don't guidance with version-specific syntax. However, it lacks examples for Search, Calendar, and Graph views despite claiming coverage, and doesn't show the attrs vs inline expression difference side-by-side, which would be highly actionable.

4 / 5

Workflow Clarity

This is essentially a single-purpose skill (generate XML views), so complex multi-step workflows aren't strictly required. The 'How It Works' section provides a simple 3-step flow. However, there's no validation step mentioned — no guidance on how to verify the generated XML is correct (e.g., checking Odoo logs, upgrading the module, testing the view). For XML manipulation, a validation checkpoint would strengthen this.

4 / 5

Progressive Disclosure

The content is reasonably structured with clear sections (Overview, Examples, Best Practices, Limitations). However, with no bundle files, all content is inlined in a single file. The skill mentions '@odoo-qweb-templates' as a cross-reference but doesn't link to any supporting files for the view types it claims to cover (Calendar, Graph, Search views are mentioned but have no examples or references to where those details live).

3 / 5

Total

14

/

20

Passed

Description

70%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies a specific technical domain (Odoo XML views) with good enumeration of view types and version coverage. Its main weakness is the absence of an explicit 'Use when...' clause, which limits Claude's ability to know precisely when to select this skill. The trigger terms are good but could include a few more natural variations.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about Odoo views, XML view definitions, form/list/kanban layouts, or mentions Odoo versions 14-17.'

Include additional trigger terms like 'tree view', 'ir.ui.view', 'attrs', 'domain', or 'record rules' that users commonly mention when working with Odoo views.

DimensionReasoningScore

Specificity

Lists several specific actions (building Form, List, Kanban, Search, Calendar, and Graph views) and mentions XML generation with version-specific syntax. Minor gaps in coverage—doesn't mention things like inheritance, actions, or menus.

4 / 5

Completeness

Has a clear 'what' (building Odoo XML views with correct syntax for versions 14-17) but lacks an explicit 'when' clause. There's no 'Use when...' guidance for Claude to know when to select this skill.

3 / 5

Trigger Term Quality

Includes good natural keywords like 'Odoo', 'XML views', 'Form', 'List', 'Kanban', 'Search', 'Calendar', 'Graph', and version numbers 14-17. Missing some natural user phrases like 'tree view', '.xml', 'ir.ui.view', or 'attrs'/'invisible'.

4 / 5

Distinctiveness Conflict Risk

Very distinct niche—Odoo XML views with specific view types and version range. Unlikely to conflict with other skills given the highly specific domain (Odoo ERP framework views).

5 / 5

Total

16

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.