CtrlK
BlogDocsLog inGet started
Tessl Logo

odoo-purchase-workflow

Expert guide for Odoo Purchase: RFQ → PO → Receipt → Vendor Bill workflow, purchase agreements, vendor price lists, and 3-way matching.

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-purchase-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 skill body is well-structured, concise, and highly actionable with concrete Odoo menu paths and field values. Its main gap is the lack of explicit validation feedback loops for destructive steps like posting vendor bills and archiving POs.

DimensionReasoningScore

Conciseness

The body is lean and assumes Odoo familiarity, using concrete menu paths and field values with no padding about what Odoo or a PDF is; only minor instances of slight chattiness keep it just below a 5.

4 / 5

Actionability

Provides concrete executable guidance — exact menu paths ('Purchase → Orders → Requests for Quotation → New') and field values ('Minimum Order Amount: $5,000') — covering common cases with only minor gaps, matching the 'mostly executable guidance' anchor; absence of code is acceptable for an instruction-only skill.

4 / 5

Workflow Clarity

The RFQ→PO→Receipt→Bill flow is clearly sequenced as Steps 1-5 with a verification checkpoint ('Verify: PO qty = Received qty = Billed qty'), but destructive/batch-adjacent steps (posting vendor bills, archiving POs) lack explicit validate→fix→retry feedback loops, matching 'clear sequence with most checkpoints; minor validation gaps'.

4 / 5

Progressive Disclosure

No bundle files exist, but the ~95-line body is well-organized into clear sections (Overview, When to Use, How It Works, Examples, Best Practices, Limitations) with easy navigation; the long Examples section could arguably be split but structure is otherwise good, fitting the 'good structure; minor organization gaps' anchor.

4 / 5

Total

16

/

20

Passed

Description

58%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 concrete Odoo Purchase sub-capabilities rather than vague fluff. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when configuring Odoo purchase orders, RFQs, vendor bills, or troubleshooting 3-way matching').

Include common synonyms/variations users might say (e.g., 'purchase order', 'PO', 'vendor invoice', 'reordering') to broaden trigger term coverage.

Optionally add file/record-level triggers (e.g., '.po', vendor bill records) if applicable to strengthen distinctiveness.

DimensionReasoningScore

Specificity

Lists several specific concrete sub-capabilities ('RFQ → PO → Receipt → Vendor Bill workflow, purchase agreements, vendor price lists, and 3-way matching') with only minor coverage gaps, matching the 'several specific actions; minor gaps' anchor.

4 / 5

Completeness

The description gives a clear 'what' but no explicit 'when'/'Use when...' clause; per the rubric's judging guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant domain terms (RFQ, Purchase Order, Vendor Bill, 3-way matching, price lists) but lacks common synonyms and any 'Use when...' phrasing, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Odoo Purchase' with domain-specific triggers (RFQ, vendor bill, 3-way matching) carves a clear niche with only minor overlap risk against other Odoo skills, matching the 'mostly distinct' anchor.

4 / 5

Total

14

/

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.

Validation — 15 / 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.