BC pipeline-comptable
Chef d'orchestre du traitement des pièces comptables entrantes. Enchaîne automatiquement les quatre étapes — tri du mail ①, analyse de la pièce ②, identification du client ③, classement ④ — comme une assistante qui traite son courrier du matin. À utiliser dès qu'il faut traiter du courrier entrant ou un lot de pièces de bout en bout : « traite les mails reçus », « range tout ce qui est arrivé », « classe ces factures », « traite cette note de frais », un mail avec pièce jointe comptable arrive, ou un dépôt de documents à traiter. Gère factures, relevés bancaires ET notes de frais. Délègue tout aux petites briques mono-tâche (tri-courrier-entrant, analyse-piece-comptable, identification-client, classement-document) et fait remonter un compte-rendu unique + les questions à poser au comptable.
Chef d'orchestre du traitement des pièces comptables entrantes.
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: Chef d'orchestre du traitement des pièces comptables entrantes. En… ^ ); 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. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 715 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 801: 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 4 example trigger phrases
- +4Structure: 5 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.