CtrlK
BlogDocsLog inGet started
Tessl Logo

odoo-edi-connector

Guide for implementing EDI (Electronic Data Interchange) with Odoo: X12, EDIFACT document mapping, partner onboarding, and automated order processing.

59

Quality

69%

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-edi-connector/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 lean, actionable, and well-structured with concrete code and a mapping table, but its workflow lacks the validation/verification checkpoints expected for batch EDI processing.

Suggestions

Add explicit validation steps to the workflow: verify required EDI segments exist before parsing, validate the created Odoo record, and include a validate→fix→retry loop for rejected/malformed transactions.

Fix Example 2 so `today` is either passed in or generated, and align the pyx12 API usage (transaction/segment access) with the library's real interface so the code is genuinely copy-paste ready.

Consider moving the two full code examples into a references/ file (e.g. examples.md) and keeping SKILL.md as an overview, to push progressive disclosure toward a 5.

DimensionReasoningScore

Conciseness

The body is mostly efficient with tight section headers and useful segment-field comments; the one-line "EDI is the standard for automated B2B document exchange..." definition is mild over-explanation Claude does not need, keeping it at 4 rather than 5.

4 / 5

Actionability

Provides concrete, near-executable Python (pyx12 + xmlrpc) and a concrete EDI↔Odoo mapping table; not a 5 because Example 2 references an undefined `today` and the pyx12 dict/segment-access API is simplified rather than accurate.

4 / 5

Workflow Clarity

A rough Activate→Map→Automate sequence exists, but there are no validation checkpoints or validate→fix→retry feedback loops for what is a batch, record-creating operation, so the batch-operations cap holds at 3.

3 / 5

Progressive Disclosure

Single self-contained file with clear, well-labeled sections (Overview, When to Use, How It Works, Examples, Best Practices) and no nested references; not a 5 because the file exceeds 50 lines and the two long code examples could plausibly live in separate reference files.

4 / 5

Total

15

/

20

Passed

Description

70%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 highly distinct, with strong domain trigger terms, but it omits any explicit 'when to use' guidance, which caps its completeness.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when integrating Odoo with a trading partner requiring X12/EDIFACT, onboarding a new EDI partner, or automating 850/856/810 document flows.'

Include the common transaction-set numbers (850, 856, 810, 997) as trigger terms so users searching by document type can find the skill.

DimensionReasoningScore

Specificity

Lists several concrete actions — "X12, EDIFACT document mapping, partner onboarding, and automated order processing" — matching anchor 4 (several specific actions, minor gaps); not a 5 because "automated order processing" is generic and invoice/acknowledgment flows are unmentioned.

4 / 5

Completeness

Clearly states what ("implementing EDI with Odoo: ... mapping, partner onboarding, ... order processing") but has no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Names natural domain keywords a user would say ("EDI", "Electronic Data Interchange", "Odoo", "X12", "EDIFACT") — good coverage; not a 5 because common variations like "trading partner", "purchase order", and transaction-set numbers (850/810) are absent.

4 / 5

Distinctiveness Conflict Risk

The EDI-plus-Odoo niche is highly specific with distinct triggers (X12/EDIFACT/Odoo), giving minimal overlap with other skills and matching the anchor-5 clear-niche example.

5 / 5

Total

16

/

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.