CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

odoo-l10n-compliance

Country-specific Odoo localization: tax configuration, e-invoicing (CFDI, FatturaPA, SAF-T), fiscal reporting, and country chart of accounts setup.

Quality

76%

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-l10n-compliance/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured, largely actionable body whose strengths are the country-module table and concrete worked examples with menu paths, field values, and an executable CLI command. Weakest spots are the marketing-flavored 'How It Works' filler, the absence of failure/feedback guidance around e-invoicing submission, and the natural limit of a single file as country coverage grows.

Suggestions

Delete or rewrite the 'How It Works' section as actual instruction — it currently describes what the user will 'receive' instead of telling Claude what to do.

Add a validation/feedback step for e-invoicing workflows (e.g., what to check when CFDI generation or SAT submission fails and how to retry), which would lift workflow clarity.

Move per-country walkthroughs (Mexico CFDI, EU fiscal positions) into references/ files and keep SKILL.md to the overview, country table, and pointers to support growth beyond the 8 listed countries.

DimensionReasoningScore

Conciseness

Mostly efficient — the country table and step-by-step examples are dense with actionable content — but there is real trimming opportunity: the "How It Works" section ("Activate: Mention @odoo-l10n-compliance...", "Install: Get the exact localization module and configuration steps", "Configure: Receive tax code setup...") is meta-copy describing what the user will 'receive' rather than instructing anything, and the Overview/When-to-Use sections partially restate each other. This fits "mostly efficient but includes some unnecessary explanation or could be trimmed". Not 4: the How-It-Works padding is more than a minor instance; not 2: the bulk of the body is tables and concrete steps, not padded explanation.

3 / 5

Actionability

Largely executable guidance: Example 1 walks exact menus ("Apps → Search 'Mexico' → Install 'Mexico - Accounting'", "Settings → Company", "Certificates → New"), Example 2 gives exact field values ("Amount: 0%", "Auto-detect: Country Group = Europe + VAT Required = YES"), and Example 3 gives a copy-paste command ("./odoo-bin -d mydb --stop-after-init -i l10n_mx_edi"). Not 5: a few gaps remain — the fiscal position in Example 2 is "created separately" with no steps, and only 3 of the 8 table countries get worked examples; not 3: the guidance present is concrete and executable, not pseudocode.

4 / 5

Workflow Clarity

Example 1 gives a clearly sequenced workflow (Install → Configure company → Upload SAT certificates → Issue CFDI) with an ordering warning ("Install the localization module before creating any accounting entries") and checkpoints appear elsewhere: Example 3's verify step ("Apps → Installed... Should show as Installed") and the practice of testing in the "SAT/tax authority test environment before going live". Not 5: there are no explicit feedback loops (no validate → fix → retry path, e.g., what to do when SAT certificate upload or CFDI submission fails); not 3: validation checkpoints are present, not absent or only implicit.

4 / 5

Progressive Disclosure

The single-file body (~95 lines) is well organized into clear sections (Overview, When to Use, country table, examples, Best Practices) with no nested or dead references — no bundle files exist to reference, and none are fabricated. Not 5: the skill exceeds the 'under 50 lines with no need for external references' bar and covers 8 countries, so per-country walkthroughs (e.g., the full Mexico CFDI procedure) are the kind of content a references/ file could carry to keep SKILL.md a leaner overview; not 3: structure is good and nothing is buried — the body reads as a coherent overview with a modest amount of detail inlined.

4 / 5

Total

15

/

20

Passed

Description

75%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.

A specific, well-scoped description with concrete named capabilities and strong niche distinctiveness. Its main weakness is the complete absence of a "Use when..." trigger clause, which both caps completeness and slightly limits natural trigger-phrase coverage.

Suggestions

Append an explicit trigger clause, e.g.: "Use when setting up Odoo for a company in a specific country, or when the user mentions CFDI, FatturaPA, SAF-T, VAT returns, or a country chart of accounts."

Add common synonyms users actually say — VAT/GST setup, tax authority integration, e-invoice submission — to broaden natural trigger coverage.

Optionally mention install/configuration verbs ("installs and configures l10n_* modules") to sharpen the what-clause.

DimensionReasoningScore

Specificity

Quotes four concrete action areas — "tax configuration", "e-invoicing (CFDI, FatturaPA, SAF-T)", "fiscal reporting", "chart of accounts setup" — each backed by named country-specific systems (CFDI, FatturaPA, SAF-T), matching the anchor "lists multiple specific concrete actions; comprehensive coverage" of the skill's stated scope. Not 4: the action list has no meaningful coverage gaps relative to what the skill actually does (its body covers exactly taxes, e-invoicing, reporting, and CoA setup).

5 / 5

Completeness

The "what" is clearly and concretely answered (tax configuration, e-invoicing, fiscal reporting, CoA setup), but there is no "Use when..." clause or any equivalent explicit trigger guidance — the "when" is entirely absent. Per the judging guideline, a missing 'Use when' clause caps completeness at 3; not 4 because the "when" is not merely implicit-or-weak, it is missing altogether.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "tax configuration", "e-invoicing", "fiscal reporting", "chart of accounts", "localization", "Odoo" — phrases a user setting up country compliance would actually say. Not 5: common synonyms and variations are missing (e.g., "VAT", "GST", "tax authority", "localization module", country names like Mexico/Italy); not 3: coverage goes well beyond 'some relevant keywords', with the named standards serving as strong natural triggers.

4 / 5

Distinctiveness Conflict Risk

"Country-specific Odoo localization" establishes a clear niche, and named systems (CFDI, FatturaPA, SAF-T) are distinct triggers no other skill would claim — minimal conflict risk. Not 4: the Odoo framing is unambiguous enough that even the broader terms ("tax configuration", "fiscal reporting") stay within this niche rather than overlapping with a generic accounting/tax skill.

5 / 5

Total

17

/

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

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/odoo-l10n-compliance/SKILL.md

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.