BC pci-dss-compliance
Implement PCI DSS requirements for payment card data. Configure cardholder data environment and security controls. Use when processing payment cards.
Implement PCI DSS requirements for payment card data.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Risky intent
intent-offensive-securitySKILL.md:157Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)"11.4": "External and internal penetration testing performed"
quoted -
low Risky intent
intent-offensive-securitySKILL.md:302Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Req 11.4 - Penetration testing (annual for external, internal, and segmentation)
-
low Risky intent
intent-offensive-securitySKILL.md:408Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] Internal penetration test annually
-
low Risky intent
intent-offensive-securitySKILL.md:409Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] External penetration test annually
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_repo" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "license_source"
Process rating: all ten parameters 51/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 70Execution cost. Instruction body is 4287 tokens
- 100Tools and files. No external tools needed
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 10 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
- +5Description has no quoted example phrases that should trigger the skill
- +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
- +3Description length 149: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.