CtrlK
BlogDocsLog inGet started
Tessl Logo

odoo-upgrade-advisor

Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation.

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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/odoo-upgrade-advisor/SKILL.md

The canonical home for this skill is odoo-upgrade-advisor 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.

This is a solid instructional skill with actionable checklists and concrete commands for the OpenUpgrade path. Its main weaknesses are unnecessary introductory/explanatory sections that Claude doesn't need, a monolithic structure that could benefit from splitting detailed checklists into separate files, and some gaps in rollback procedures and explicit failure-recovery loops. The Enterprise upgrade path mentioned in the description is notably absent from the content.

Suggestions

Remove or drastically shorten the 'Overview', 'When to Use This Skill', and 'How It Works' sections — Claude doesn't need to be told what an upgrade is or when to use the skill.

Add an explicit rollback procedure with concrete commands (e.g., database restore from backup) and a feedback loop for post-upgrade validation failures.

Include the Enterprise upgrade path (Odoo Upgrade Service) with concrete steps, since the skill description promises 'community vs enterprise upgrade path' guidance.

Consider splitting the pre-upgrade checklist and post-upgrade validation checklist into separate referenced files to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The overview and 'When to Use This Skill' sections explain things Claude already knows (what an Odoo upgrade is, when to use the skill). The 'How It Works' section with activation instructions adds little value. However, the checklists and command examples themselves are reasonably efficient.

3 / 5

Actionability

The skill provides concrete, executable bash commands for OpenUpgrade, detailed checklists with specific validation items, and links to real tools. Minor gaps include lacking specific commands for backup/restore and the Enterprise upgrade path being absent despite being mentioned in the description.

4 / 5

Workflow Clarity

The pre-upgrade checklist provides a clear 10-step sequence with staging-before-production validation. The OpenUpgrade example includes a log review step. However, the go/no-go decision criteria are vague, and there's no explicit rollback procedure or feedback loop for the post-upgrade validation (what to do if validation fails beyond 'fix and re-test').

4 / 5

Progressive Disclosure

All content is inlined in a single file with no bundle files for supporting material. The post-upgrade validation checklists per module area and the detailed pre-upgrade checklist could be split into separate reference files. External links to OCA and Odoo Upgrade Service are provided, but the skill itself is a monolithic document that would benefit from better structural separation.

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 does a good job identifying a clear niche (Odoo version upgrades) and listing specific aspects of the upgrade process. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding trigger phrases and a few synonym terms like 'migration' would strengthen it further.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Use when the user asks about Odoo version upgrades, migrations, or updating Odoo from one version to another.'

Include common synonyms and variations such as 'migration', 'version migration', 'Odoo update', and example version references like 'Odoo 14 to 16' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists several specific actions/areas: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation. These are concrete aspects of the upgrade process, though it could be more granular about what each step entails.

4 / 5

Completeness

The 'what' is clearly stated (step-by-step upgrade advising with specific areas covered), but there is no explicit 'when' clause. There's no 'Use when...' guidance telling Claude when to select this skill, which caps this dimension at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes strong natural keywords like 'Odoo', 'upgrade', 'OCA module', 'community vs enterprise', 'pre-upgrade', 'post-upgrade'. Missing some natural variations users might say like 'migration', 'version migration', specific version numbers (e.g., 'Odoo 16 to 17'), or 'update'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Odoo version upgrades specifically. The combination of Odoo, OCA modules, community vs enterprise, and upgrade-specific terminology makes it very unlikely to conflict with other skills.

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.