SKILLEMALL.ai
GitHub ↗ RU Sign in

BC pci-compliance

Expert PCI DSS compliance advisor covering PCI DSS v4.0.1 (current) and v4.0. Use this skill whenever a user asks about PCI DSS, payment card security, cardholder data protection, CDE scoping, SAQ types (A, A-EP, B, B-IP, C, C-VT, P2PE, D), ROC, AOC, QSA assessments, ASV scans, merchant levels, service provider levels, network segmentation, penetration testing, tokenisation, encryption of PAN data, or any of the 12 PCI DSS requirements. Also trigger for questions like "are we PCI compliant?", "how do I scope my CDE?", "which SAQ applies to us?", "what changed in PCI DSS v4.0?", "how do I prepare for a QSA audit?", or any request involving payment data security, cardholder data environment, or PCI certification readiness.

lawve-ai/awesome-legal-skills Agent Skills author: lawve-ai 6 files body ≈ 3 260 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Expert PCI DSS compliance advisor covering PCI DSS v4.0.1 (current) and v4.0. Use this skill whenever a user asks about PCI DSS, payment card security…

As a process C 55/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency

AnalyzerSecuritytype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
91
Quality 40%
93
Run on models
none yet
Process rating
C
55/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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 · 9

    ✓ No critical or high findings

    Medium and low: 9
    • low Risky intent intent-offensive-security references/pci-dss-requirements.md:123
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Anti-malware controls protect against viruses, ransomware, spyware, and other threats.
    • low Risky intent intent-offensive-security references/pci-dss-requirements.md:311
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | 11.4 | External and internal penetration testing is performed | Penetration test reports |
    • low Risky intent intent-offensive-security references/pci-dss-requirements.md:312
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | 11.4.1 | Penetration testing methodology defined | Pen test scope document |
    • low Risky intent intent-offensive-security references/pci-dss-requirements.md:313
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | 11.4.2 | Internal penetration testing at least annually and after changes | Annual pen test report |
    • low Risky intent intent-offensive-security references/pci-dss-requirements.md:314
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | 11.4.3 | External penetration testing at least annually and after changes | External pen test report |
    • low Risky intent intent-offensive-security references/pci-dss-v4-changes.md:72
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
      - **11.4.7**: Multi-tenant service providers support customers' requests for penetration testing
      quoted
    • low Risky intent intent-offensive-security SKILL.md:3
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      description: "Expert PCI DSS compliance advisor covering PCI DSS v4.0.1 (current) and v4.0. Use this skill whenever a user asks about PCI DSS, payment card security, cardholder data protection, CDE sc
      detector
    • low Risky intent intent-offensive-security SKILL.md:178
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | Penetration Testing and ASV Scan Policy | Req 11 |
    • low Risky intent intent-offensive-security SKILL.md:194
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | **Penetration testing** | Req 11.3 | Enhanced scope: internal + external + CDE segmentation validation |

    Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 55/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 1 mutating operations with no state check
    • 40Consistency. Frontmatter name (pci-compliance) differs from the folder (pci-compliance-tanaji-hemant-naik)
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 50 steps
    • 100Execution cost. Instruction body is 3260 tokens
    • 100Progress reporting. Reports progress

    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)
    • +4No input/output examples
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +3Description length 730: enough signal without eating the budget
    • +4Structure: 18 headings
    • +3Step-by-step instructions: 50 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (3 of 3)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.