odoo-woocommerce-bridge
Sync Odoo with WooCommerce: products, inventory, orders, and customers via WooCommerce REST API and Odoo external API.
56
63%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/odoo-woocommerce-bridge/SKILL.mdThe canonical home for this skill is odoo-woocommerce-bridge in administrakt0r/AI-Agents-Safe-Coding-Skills
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The skill's example integration code hardcodes API credentials (consumer_key, consumer_secret) and an Odoo password, which encourages embedding secret values verbatim into generated scripts and outputs.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required runtime workflow for this skill syncs WooCommerce orders/products/customers from the user’s WooCommerce store via the WooCommerce REST API (e.g., `wcapi.get("orders"...).json()`), and outsider-authored free text submitted by store customers/emails is ingested as fields like billing info and line item data.
- Commit
0159794
- Audited
- Security analysis
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.