Name: odoo-woocommerce-bridge
Rating: 61.6 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

odoo-woocommerce-bridge

Sync Odoo with WooCommerce: products, inventory, orders, and customers via WooCommerce REST API and Odoo external API.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/odoo-woocommerce-bridge/SKILL.md

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

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 body delivers strong, executable code examples and a useful field-mapping table in a concise, well-structured layout. Its main weakness is workflow clarity: the batch sync operations lack validation checkpoints and error-recovery loops.

Suggestions

Add explicit validation/verification steps to the sync workflows (e.g. verify the sale.order was created, check the WooCommerce PUT response, retry on failure) so batch operations have feedback loops.

Insert a numbered end-to-end workflow with checkpoints (authenticate → fetch → validate payload → upsert → verify → flag) rather than relying on the code comments alone to convey sequence.

Move the full field-mapping table into a one-level-deep reference file and keep only key mappings inline, to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding explaining what Odoo or WooCommerce are — though the Overview and 'How It Works' sections lightly restate the description and could be trimmed.	4 / 5
Actionability	Two complete, executable Python examples (order import and inventory push) with real WooCommerce REST and Odoo xmlrpc calls, plus a concrete field-mapping table, cover the common cases in copy-paste-ready form.	5 / 5
Workflow Clarity	A sequence is present in the code (find/create partner → build order lines → create sale order → mark on-hold), but batch sync operations lack validation/verification checkpoints and error-recovery loops, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Overview, When to Use, How It Works, Field Mapping, Examples, Best Practices) with no nested references; minor gaps only, since some reference material (e.g. full field mapping) could live in a separate file.	4 / 5
	Total	16 / 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 clearly conveys a specific integration niche and lists concrete sync targets, but it omits any explicit 'Use when' trigger guidance, which limits its completeness. Trigger-term coverage is solid but lacks synonyms.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases (e.g. 'Use when syncing a WooCommerce store with Odoo, importing WooCommerce orders into Odoo, or pushing Odoo stock to WooCommerce').

Include synonyms and store-context terms (e.g. 'WordPress store', 'ERP', 'WooCommerce REST API') to broaden trigger-term coverage.

Reframe the entity list as concrete actions (e.g. 'sync products, import orders, update inventory, manage customers') rather than bare nouns.

Dimension	Reasoning	Score
Specificity	Names the sync action across four concrete entity targets ("products, inventory, orders, and customers") and both APIs ("WooCommerce REST API and Odoo external API"), giving several specific sync targets with only minor coverage gaps.	4 / 5
Completeness	The 'what' is clear (sync Odoo with WooCommerce across four domains), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms users would say ("Odoo", "WooCommerce", "products, inventory, orders, customers") with good coverage, though synonyms like "WordPress store" or "ERP" are absent.	4 / 5
Distinctiveness Conflict Risk	The Odoo↔WooCommerce pairing is a clear, narrow niche with distinct triggers and minimal risk of overlapping with unrelated skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/odoo-woocommerce-bridge/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.