BC analyse-piece-comptable
Analyse UNE pièce comptable (facture, relevé bancaire ou note de frais) et en rend compte au comptable — sans la classer ni la déplacer. À utiliser dès que le comptable veut comprendre une pièce isolée : « regarde cette facture », « qu'est-ce que c'est ce document ? », « lis-moi ce relevé », « c'est quoi cette note de frais ? », « il y a un souci sur cette pièce ? », « combien de TVA sur cette facture ? », ou simplement quand une pièce jointe arrive et que le comptable veut un avis dessus avant tout classement. Extrait le type de pièce, les montants, la TVA, les dates, l'émetteur/destinataire (ou société/salarié pour une note de frais), et signale les incohérences (champ manquant, TVA fausse, total qui ne tombe pas juste, IBAN invalide, date aberrante). Lecture seule : ne range rien (le classement, c'est classement-document) et ne rapproche rien (c'est rapprochement-paiements).
Analyse UNE pièce comptable (facture, relevé bancaire ou note de frais) et en rend compte au comptable — sans la classer ni la déplacer.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Analyse UNE pièce comptable (facture, relevé bancaire ou note de f… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1418 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 890: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -31 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +4Structure: 8 headings
- +3Step-by-step instructions: 9 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.