CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-einvoice-fr

Implement the French e-invoicing mandate (2026/2027) with Factur-X specs, PDP selection, and e-reporting workflows. Use when: Determine exact mandate dates based on SIREN size and VAT regime; Map Factur-X EN16931 profiles for technical ERP integration; Design automated workflows for the four mandatory invoice statuses.

Quality

64%

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 ./skills/nex-einvoice-fr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

18%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 a marketing product-listing page rather than a skill: it pitches the skill's value ('Why this beats prompting it yourself', purchase FAQ, paid-catalog link) but ships none of the operational content it claims — no date matrix, no Factur-X profile mapping, no lifecycle workflow, no e-reporting rules. As deployed, the skill gives Claude almost nothing actionable beyond one example answer.

Suggestions

Replace the marketing sections ('The problem', 'Why this beats prompting it yourself', the FAQ, and the promo footer) with the actual reference data: the mandate-date matrix by SIREN category (Micro/PME/ETI/GE) and VAT regime, the Factur-X profile-to-EN16931 field mapping, and the e-reporting frequency rules per regime.

Add a concrete, sequenced workflow for the four mandatory invoice lifecycle statuses, including the operational difference between 'rejetée' and 'refusée' and the action required for each status.

Move detailed regulatory tables into bundled reference files (e.g., references/dates.md, references/facturx-profiles.md, references/e-reporting.md) and link them clearly from a lean SKILL.md overview, restoring the progressive-disclosure structure the original package apparently had.

DimensionReasoningScore

Conciseness

Noticeably padded: 'Why this beats prompting it yourself' and the seven-question marketing FAQ ('once purchased, you can instantly deploy it...') plus the promo footer give Claude nothing operational. It avoids score 1 only because 'The problem' and 'Known limitations' carry some signal and it does not explain concepts Claude already knows.

2 / 5

Actionability

The body only describes capabilities ('Generates precise applicability calendars', 'Provides technical mapping') rather than instructing, with the sole concrete element being one demo Q&A (PME, réel normal → Sept 2027 issuance, decade e-reporting within 10 days). That is minimal high-level guidance with every specific step missing — between the 'entirely vague' (1) and 'some concrete guidance' (3) anchors, but closer to minimal.

2 / 5

Workflow Clarity

No sequence of steps exists anywhere in the body; the 'four mandatory invoice statuses' and lifecycle workflows are named but never defined, and the body itself admits 'Scripts, extension source, and templates from the original package are not in this folder.'

1 / 5

Progressive Disclosure

Section headers provide minimal structure, but there are zero file references and no bundle files exist (no references/, scripts/, or assets/ directories) — the payload content (date matrices, profile mappings, decision trees) that clearly belongs in separate reference files is simply absent, which sits between anchors 2 and 3 but closer to 2 since no working references are present at all.

2 / 5

Total

7

/

20

Passed

Description

92%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 strong description: it names the domain precisely, enumerates concrete capabilities, includes an explicit 'Use when:' clause with three trigger scenarios, and uses highly distinctive terminology. The only weakness is missing natural synonyms, particularly the French-language terms a French user would actually type.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Determine exact mandate dates based on SIREN size and VAT regime', 'Map Factur-X EN16931 profiles', 'Design automated workflows for the four mandatory invoice statuses', plus PDP selection and e-reporting — covering the mandate's scope comprehensively; score 4 would require noticeable coverage gaps, and none are apparent.

5 / 5

Completeness

Explicitly answers both 'what' ('Implement the French e-invoicing mandate... with Factur-X specs, PDP selection, and e-reporting workflows') and 'when' via a literal 'Use when:' clause with three concrete trigger scenarios, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('French e-invoicing', 'Factur-X', 'PDP', 'e-reporting', 'SIREN', 'VAT', 'ERP integration'), but a few natural terms users would say are missing — notably French-language phrasing like 'facturation électronique' or 'facture électronique', which is a notable gap for a France-specific skill.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers — Factur-X, PDP, SIREN, EN16931, e-reporting — that virtually no other skill would match, so conflict risk is minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

skills/nex-einvoice-fr/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.