CtrlK
BlogDocsLog inGet started
Tessl Logo

odoo-l10n-compliance

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

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

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

61%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 is actionable and well-structured with concrete commands, menu paths, and per-country examples, but its workflows lack consistent validation/feedback loops and some sections carry mild verbosity.

Suggestions

Add explicit validation checkpoints to the CFDI and tax-setup workflows (e.g., verify certificate upload, confirm test-environment submission succeeded before going live).

Tighten the Overview to drop general Odoo background Claude already knows.

Consider moving per-country deep-dive details into reference files if the skill grows, to keep the overview lean.

DimensionReasoningScore

Conciseness

Mostly efficient with clear sections, but the Overview restates general facts about Odoo localizations and the worked menu-path examples carry some padding that could be tightened.

3 / 5

Actionability

Provides concrete executable guidance — exact CLI commands (./odoo-bin -d mydb --stop-after-init -i l10n_mx_edi), menu paths, and specific tax/fiscal-position fields — with only minor gaps.

4 / 5

Workflow Clarity

Sequences multi-step examples (Step 1-4) and includes one verify step in Example 3, but the main CFDI workflow and tax setup lack explicit validation checkpoints/feedback loops, which caps the score at 3.

3 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers (Overview, When to Use, modules table, Examples, Best Practices) and no nested or buried references; minor gaps only.

4 / 5

Total

14

/

20

Passed

Description

58%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 distinct, naming concrete capabilities and niche acronyms, but it lacks an explicit 'when to use' trigger clause, which caps its completeness and leaves natural trigger phrases under-covered.

Suggestions

Add an explicit 'Use when ...' clause naming natural trigger phrases (e.g., setting up Odoo for a country, configuring e-invoicing, country tax/VAT setup).

Include more conversational synonyms users would say (e.g., 'tax setup', 'country chart of accounts', 'electronic invoicing') alongside the technical acronyms.

Confirm both 'what' and 'when' are answered concretely to lift completeness above 3.

DimensionReasoningScore

Specificity

Lists several concrete actions — "tax configuration, e-invoicing (CFDI, FatturaPA, SAF-T), fiscal reporting, and country chart of accounts setup" — with minor gaps in coverage rather than full comprehensiveness.

4 / 5

Completeness

Gives a clear 'what' but has no explicit 'when'/'Use when...' trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant domain keywords (e-invoicing, CFDI, FatturaPA, fiscal reporting) but misses common natural variations/synonyms and the conversational phrases a user would actually say when needing this skill.

3 / 5

Distinctiveness Conflict Risk

"Country-specific Odoo localization" is a clear, distinct niche with mostly minimal overlap risk against other skills.

4 / 5

Total

14

/

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.