Content
18%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |