CtrlK
BlogDocsLog inGet started
Tessl Logo

odoo-shopify-integration

Connect Odoo with Shopify: sync products, inventory, orders, and customers using the Shopify API and Odoo's external API or connector modules.

53

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/odoo-shopify-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 provides useful, mostly executable code examples for Shopify-Odoo order sync, but suffers from unnecessary introductory padding and lacks critical workflow validation steps for what is a multi-system integration involving data creation. The data flow diagram promises coverage of inventory, fulfillment, and product sync, but only order creation is actually implemented, leaving significant gaps.

Suggestions

Add explicit validation/error-handling steps: verify the created Odoo order exists after creation, handle cases where SKU lookup returns False, and add try/except blocks around API calls with retry logic.

Remove or drastically shorten the 'Overview', 'When to Use This Skill', and 'How It Works' sections — Claude doesn't need to be told what Shopify sync is or how to 'activate' a skill.

Add the HMAC signature validation code that's recommended in Best Practices but never shown — this is a security-critical gap.

Either provide implementation examples for the other data flows shown in the architecture diagram (inventory sync, fulfillment push-back) or split them into referenced files to set proper expectations.

DimensionReasoningScore

Conciseness

The 'Overview' and 'When to Use This Skill' sections explain things Claude already knows (what syncing means, what Shopify/Odoo are). The 'How It Works' section with 'Activate/Design/Build' is meta-fluff. The data flow diagram and code examples are useful, but there's noticeable padding that could be trimmed.

3 / 5

Actionability

The Python code examples are concrete and mostly executable — the XMLRPC order creation and Flask webhook receiver are copy-paste ready. Minor gaps include the missing HMAC validation code (mentioned in best practices but not shown), missing error handling, and the `get_odoo_product_id` returning False without handling that case in the order creation.

4 / 5

Workflow Clarity

There is no clear multi-step workflow with validation checkpoints. The skill involves creating orders and syncing data (operations that should have validation/error recovery), but there's no verification that the created order is correct, no error handling for failed API calls, no retry logic, and no feedback loop. The data flow diagram shows architecture but not operational steps. This is a multi-system integration involving destructive operations (creating orders, modifying inventory) without validation, which should cap this at 3, and the lack of any sequenced steps pushes it to 2.

2 / 5

Progressive Disclosure

The content is reasonably structured with clear sections and headers, but there are no references to external files for advanced topics (e.g., inventory sync code, fulfillment push-back, Shopify connector module setup, HMAC validation). Everything is inlined, and topics mentioned in the data flow diagram (inventory sync, fulfillment push) lack corresponding implementation details or file references.

3 / 5

Total

12

/

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 clearly identifies a specific integration domain (Odoo-Shopify) with concrete sync targets and technologies, making it highly distinctive. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Trigger term coverage is good but could benefit from synonyms like 'e-commerce integration' or 'ERP sync'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about connecting Odoo to Shopify, syncing e-commerce data, or setting up an Odoo-Shopify integration.'

Include additional trigger synonyms such as 'e-commerce integration', 'ERP sync', 'stock synchronization', or 'Shopify connector' to improve discoverability.

DimensionReasoningScore

Specificity

Lists several specific actions (sync products, inventory, orders, customers) and names concrete technologies (Shopify API, Odoo's external API, connector modules). Minor gaps—could mention specific operations like creating webhooks, handling fulfillments, or mapping fields.

4 / 5

Completeness

The 'what' is clearly stated (connect Odoo with Shopify, sync various entities using specific APIs). However, there is no explicit 'when' clause or trigger guidance telling Claude when to select this skill, which caps this dimension at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes strong natural keywords: 'Odoo', 'Shopify', 'sync products', 'inventory', 'orders', 'customers', 'Shopify API', 'connector modules'. Missing some variations like 'e-commerce integration', 'Shopify connector', 'stock sync', or 'ERP integration'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive—the combination of Odoo and Shopify integration is a very specific niche. It's unlikely to conflict with other skills unless there are multiple Odoo-Shopify integration skills, which is improbable.

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.