BC tri-courrier-entrant
Étape ① du pipeline comptable. Trie un mail entrant comme le ferait une assistante qui ouvre son courrier : décide s'il concerne la comptabilité, en sort les pièces à traiter et les informations d'en-tête (expéditeur, domaine, objet) utiles pour reconnaître le client ensuite. À utiliser dès qu'un mail arrive et qu'il faut décider quoi en faire : « ce mail me concerne ? », « y a-t-il une facture là-dedans ? », tri d'un courrier reçu, première étape avant d'analyser une pièce. Ne lit pas le contenu des pièces (c'est analyse-piece-comptable) et ne range rien (c'est classement-document). Décision + normalisation, rien d'autre.
Étape ① du pipeline comptable.
As a process C 50/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: 3. 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: Étape ① du pipeline comptable. Trie un mail entrant comme le ferai… ^ ); 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 50/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
- 75Steps. 3 steps
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 520 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 630: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (2 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.