BC identification-client
Étape ③ du pipeline comptable. Reconnaît à quel client appartient une pièce déjà analysée, et pour une facture détermine le sens (achat = le client est le destinataire, vente = le client est l'émetteur). À utiliser dès qu'il faut rattacher un document à un dossier client : « à qui appartient cette facture ? », « c'est un de nos clients ? », « c'est un achat ou une vente ? », après l'analyse d'une pièce et avant de la ranger. C'est la seule brique qui tient le registre clients (clients.json) : elle le lit pour reconnaître et n'y ajoute que du certain (un nouveau client vu sur un relevé bancaire). Ne range aucun fichier (c'est classement-document).
Étape ③ du pipeline comptable.
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: 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. Reconnaît à quel client appartient … ^ ); 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. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 689 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 3 example trigger phrases
- +3Description length 654: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 7 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.