Content
61%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, genuinely actionable body built around two complete XML examples and crisp version-specific Do/Don't rules. Its main gaps are redundancy around the attrs deprecation and a complete absence of validation steps for generated XML, plus example coverage that stops at two of the six advertised view types.
Suggestions
Add a validation step to the workflow, e.g., "After writing view XML, upgrade the module (-u module_name) and confirm the view loads without parse errors or attrs deprecation warnings; fix and re-check before delivering."
Merge the duplicated attrs guidance into a single Do/Don't pair and drop the meta "How It Works" activation steps to tighten the token budget.
Add at least one compact example each for a Search view (filters/group-by) and the v14-16 attrs syntax, or move the example set into a references/examples file to cover the advertised view types.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient — the XML examples and Do/Don't rules earn their tokens — but it could be tightened: the attrs deprecation is stated twice ("Use attrs ... only if you are targeting Odoo 14–16 — it is deprecated in v17" and "Don't: Use attrs in Odoo 17 — it is fully deprecated and raises warnings"), the "How It Works" section explains skill activation Claude doesn't need, and the Overview restates the description. Anchor 3, not 4, because these are more than minor trimmable instances. | 3 / 5 |
Actionability | Two complete, copy-paste-ready ir.ui.view XML records (form with header/statusbar/notebook/chatter; kanban with templates and default_group_by) plus exact syntax in the Do/Don'ts (invisible="condition" vs attrs="{'invisible': [...]}" ). Not 5: no example for the Search, Calendar, or Graph views claimed in the description, and no sample of the v14-16 attrs syntax it tells users to use. | 4 / 5 |
Workflow Clarity | "How It Works" provides a rough sequence (Activate → Generate → Review) but no validation checkpoint — nothing like upgrading the module, reloading the view, or checking for XML parse errors. Per the scoring notes, XML manipulation without a feedback loop caps workflow clarity at 3; the sequence is present but checkpoints are absent, matching anchor 3. | 3 / 5 |
Progressive Disclosure | No bundle files exist and the ~4KB body is well-organized with clear sections (Overview, When to Use, How It Works, Examples, Best Practices, Limitations), so inline placement is defensible. Not 5: the body exceeds the ~50-line simple-skill threshold, and the two 25+-line XML examples plus per-version syntax details are natural candidates for a reference file; there are no well-signaled references at all. | 4 / 5 |
Total | 14 / 20 Passed |