CtrlK
BlogDocsLog inGet started
Tessl Logo

odoo-inventory-optimizer

Expert guide for Odoo Inventory: stock valuation (FIFO/AVCO), reordering rules, putaway strategies, routes, and multi-warehouse configuration.

63

Quality

75%

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-inventory-optimizer/SKILL.md

The canonical home for this skill is odoo-inventory-optimizer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%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 content is highly actionable, with concrete menu paths and field values across four realistic Odoo Inventory scenarios, and is reasonably concise. Its main gap is the absence of validation/verification checkpoints in recipes that touch destructive operations like valuation changes and stock adjustments.

Suggestions

Add explicit verification steps after each recipe, e.g. after enabling FIFO: 'Verify via Inventory → Reporting → Inventory Valuation that the costing method shows FIFO and a stock journal entry posted.'

Include a feedback loop for the reordering recipe (e.g. confirm the Purchase/Manufacturing Order was generated and check the scheduled date).

Consider moving the four detailed config examples into a references/ file and keeping SKILL.md as a concise overview to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is efficient and mostly assumes Claude's competence; parenthetical notes like 'trigger reorder when stock falls below this' add Odoo-specific value rather than padding, though a few inline explanations could be trimmed.

4 / 5

Actionability

Each example gives exact menu paths, field values, and account mappings (e.g. 'Inventory → Configuration → Product Categories → Edit' with Costing Method and account fields), providing copy-paste-ready configuration guidance.

5 / 5

Workflow Clarity

Recipes list sequenced menu steps but lack validation/verification checkpoints, and the skill touches destructive operations (valuation changes, stock adjustments), so per the guidelines workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

A single self-contained file with clear section headers (Overview, When to Use, Examples, Best Practices, Limitations) and no bundle files to navigate; well-organized, though slightly above the 50-line simple-skill threshold.

4 / 5

Total

16

/

20

Passed

Description

75%Weight 40%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 is specific and distinct, naming five concrete Odoo Inventory capabilities, but it omits any explicit 'when to use' trigger guidance, which caps completeness. Adding a 'Use when...' clause with natural trigger phrases would raise the score.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when configuring Odoo Inventory, setting up stock valuation, reordering rules, putaway, or multi-step warehouse routes.'

Include natural synonyms a user might say, such as 'inventory management', 'stock control', or 'warehouse setup', to broaden trigger coverage.

Keep the capability list but consider framing it as actions ('Configure stock valuation...', 'Set up reordering rules...') to align with the third-person action voice the rubric rewards.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'stock valuation (FIFO/AVCO), reordering rules, putaway strategies, routes, and multi-warehouse configuration' — giving comprehensive coverage of the skill's scope.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural Odoo-domain terms ('Odoo Inventory', 'FIFO/AVCO', 'reordering rules', 'putaway strategies', 'multi-warehouse') are present, but common synonyms users might say ('inventory management', 'stock control', 'warehouse setup') are missing, so it is not a 5.

4 / 5

Distinctiveness Conflict Risk

'Expert guide for Odoo Inventory' carves a clear niche with distinct Odoo-specific triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.