BD pci-compliance
Conseiller expert en conformité PCI DSS v4.0.1 (seule version active depuis le 31 décembre 2024). Utiliser pour toute question sur PCI DSS, la sécurité des paiements par carte, les données de titulaires, le périmètre du CDE, les types de SAQ (A, A-EP, B, B-IP, C, C-VT, P2PE, D), le ROC, l'AOC, les évaluations QSA, les scans ASV, les niveaux de marchands et de prestataires, la segmentation réseau, les tests d'intrusion, la tokenisation, le chiffrement du PAN, ou l'une des 12 exigences. Couvre la révision SAQ A de janvier 2025 (critère d'éligibilité r1, FAQ 1588), les exigences v4.0 obligatoires depuis le 31 mars 2025, et l'articulation avec DSP2, RGPD, NIS2 et DORA via les connecteurs MCP LibreJustice et EUR-Lex. Déclencheurs : « sommes-nous conformes PCI ? », « quel SAQ s'applique ? », « qu'est-ce qui a changé en v4.0 ? », « comment préparer un audit QSA ? ».
Conseiller expert en conformité PCI DSS v4.0.1 (seule version active depuis le 31 décembre 2024). Utiliser pour toute question sur PCI DSS, la sécurité des…
As a process D 40/100 · Unfinished process — 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 40/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
- 40Consistency. Frontmatter name (pci-compliance) differs from the folder (pci-compliance-el-ouertani-faouzi)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Execution cost. Instruction body is 4510 tokens
- 100Steps. 40 steps
- 100Running it twice. No mutating operations
- low 12 top-level sections: this looks like several domains in one skill
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 871: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +4Structure: 21 headings
- +3Step-by-step instructions: 40 items
- +4Reference files are cited in the instructions (3 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.