SKILLEMALL.ai
GitHub ↗ RU Sign in

CC pci-dss-specialist

PCI DSS v4.0 payment card data security compliance, assessment, and implementation. Use for PCI DSS scoping, cardholder data environment (CDE) security, SAQ and ROC preparation, QSA engagement, tokenization, and merchant compliance.

borghei/Claude-Skills Agent Skills author: borghei 9 files · 2 scripts body ≈ 1 778 tokens Open the sourcegithub.com↗ analyzed 7 h ago

PCI DSS v4.0 payment card data security compliance, assessment, and implementation. Use for PCI DSS scoping, cardholder data environment (CDE) security, SAQ…

As a process C 55/100 · Has gaps — References files that are not bundled: ../infrastructure-compliance-auditor/, ../nist-csf-specialist/, ../soc2-compliance-expert/

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
C
86/100
safety, quality, tests
Safety 60%
90
Quality 40%
80
Run on models
none yet
Process rating
C
55/100
Has gaps
References files that are not bundled: ../infrastructure-compliance-auditor/, ../nist-csf-specialist/, ../soc2-compliance-expert/
Tools and files w 18
0
Inputs and preconditions w 11
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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 · 10

✓ No critical or high findings

Medium and low: 10
  • low Risky intent intent-offensive-security references/infrastructure-controls-and-roadmap.md:15
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Penetration testing from non-CDE segments attempting to reach CDE
  • low Risky intent intent-offensive-security references/infrastructure-controls-and-roadmap.md:182
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    3. **Penetration testing** — External and internal pen tests (Req 11.4)
  • low Risky intent intent-offensive-security references/pci-infrastructure-security.md:309
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    └── NO lateral movement to other VLANs
  • low Risky intent intent-offensive-security references/pci-infrastructure-security.md:378
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - API-specific penetration testing (OWASP API Security Top 10)
  • low Risky intent intent-offensive-security references/pci-infrastructure-security.md:381
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Authorization testing (vertical and horizontal privilege escalation)
  • low Risky intent intent-offensive-security references/requirements-and-changes.md:335
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - **11.4.1** — External penetration testing at least annually and after significant changes
  • low Risky intent intent-offensive-security references/requirements-and-changes.md:336
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - **11.4.3** — Internal penetration testing at least annually and after significant changes
  • low Risky intent intent-offensive-security references/requirements-and-changes.md:337
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - **11.4.4** — Vulnerabilities found during penetration testing are corrected
  • low Risky intent intent-offensive-security references/tools-validation-troubleshooting.md:192
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - [ ] Annual penetration testing
  • low Risky intent intent-offensive-security references/tools-validation-troubleshooting.md:222
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    - Quarterly ASV scans passing with no exploitable vulnerabilities, and annual penetration testing completed with findings remediated
    detector

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../infrastructure-compliance-auditor/
  • warning missing-ref reference to a missing file: ../nist-csf-specialist/
  • warning missing-ref reference to a missing file: ../soc2-compliance-expert/
  • warning missing-ref reference to a missing file: ../information-security-manager-iso27001/
  • warning missing-ref reference to a missing file: ../nis2-directive-specialist/

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: ../infrastructure-compliance-auditor/, ../nist-csf-specialist/, ../soc2-compliance-expert/
  • 0Tools and files. 5 referenced file(s) missing: ../infrastructure-compliance-auditor/, ../nist-csf-specialist/, ../soc2-compliance-expert/
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 1 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 55Failures and branches. 1 branches
  • 100Steps. 27 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1778 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

  • +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 232: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 27 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (6 of 6)
  • +3All 2 scripts are documented
  • +1License stated

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