Skip to main content
skill CX Codex

pci-compliance · sickn33 — Claude Code skill: what it does, how to install

pci-compliance traces payment data through your project and gathers control evidence for a scoped PCI assessment. It does not certify compliance.

MIT ★ 50,109 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sickn33/agentic-awesome-skills --skill pci-compliance -a claude-code
Open on GitHub

What pci-compliance does

The skill walks a project and lists where card data turns up: forms, APIs, queues, storage, logs, telemetry, backups and support exports. It then lines those flows up with the control areas a scoped PCI assessment expects and returns a table of controls, evidence, gaps and owners, plus a remediation plan. Attestation stays outside its scope, and so does the decision on whether you qualify for an assessment.

Bring the merchant or service-provider role, the acquiring institution, how the processor is wired in, which systems touch account data, and the current assessment documents from the PCI SSC library. Applicability gets confirmed by your assessor or acquirer, not by the skill. Inside sits resources/implementation-playbook.md, which sets the order of the mapping work.

A tokenization claim in the integration docs says nothing about what your application actually receives, so the check starts at that boundary. Log and response fields should come from an allowlist, because a denylist will miss nested errors and retries. Exercise success, failure and retry paths with synthetic data only.

What it helps with

  • map every system that touches account data
  • gather evidence for network boundaries and access control
  • replace card fields in webhook logs with an allowlisted payload
  • build a control/evidence/gap/owner table with named owners
  • test nested errors and retries with synthetic data

Example prompts for the agent

  • Walk the checkout flow and list every place card data shows up: forms, API handlers, queues, logs and backups
  • Build the control/evidence/gap/owner table for our payment service and mark the controls we have not verified yet
  • Check the webhook logs for card fields and rerun success, failure and retry cases with synthetic data

How to install pci-compliance

1Skills CLI (Vercel)

npx skills add sickn33/agentic-awesome-skills --skill pci-compliance -a claude-code

2Manually: put the files in place

~/.claude/skills/pci-compliance/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/pci-compliance/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about pci-compliance

How do I install pci-compliance in Claude Code?

Run npx skills add sickn33/agentic-awesome-skills --skill pci-compliance -a claude-code. The skill file lands at ~/.claude/skills/pci-compliance/SKILL.md.

What does pci-compliance do?

It matches the payment data flows it finds against the controls of a scoped PCI assessment and produces an evidence, gap and owner table with a remediation plan.

Does the skill certify PCI compliance?

No. It keeps unverified controls marked as gaps, and encryption, hosted checkout or a passed scan on their own prove nothing. SAQ eligibility and formal attestation stay with your assessor.

Source text

SKILL.md · MIT
---
name: pci-compliance
description: "Review payment data flows and engineering control evidence for a scoped PCI assessment, without claiming certification."
risk: critical
source: community
date_added: "2026-02-27"
---

# Payment Data and PCI Evidence Review

## When to Use

Review payment data flows, prepare engineering controls or collect evidence for a scoped PCI assessment. This skill does not certify compliance or determine assessment eligibility on its own.

## Inputs and prerequisites

Identify the merchant/service-provider role, acquiring institution, processor integration, systems handling account data and the applicable assessment documents. Obtain the current documents from the [PCI SSC document library](https://www.pcisecuritystandards.org/document_library/); confirm applicability with the responsible assessor or acquiring institution.

## Procedure

1. Follow `resources/implementation-playbook.md` to map forms, APIs, storage, queues, logs, telemetry, backups and support exports.
2. Prefer provider-hosted collection when appropriate. Verify what the application actually receives; a tokenization claim does not prove that raw account data never reaches another system.
3. Minimize retained data and document purpose, access, retention and deletion. Do not retain sensitive authentication data after authorization, even encrypted. Do not build a custom card vault from an illustrative encryption snippet.
4. Map required controls to implementation evidence: network boundaries, system configuration, data protection, access, monitoring, testing and operational ownership. Keep unverified controls marked as gaps.
5. Use allowlisted event fields in logs and responses. Test nested errors and retries with synthetic data; denylist filtering cannot anticipate every sensitive field name.
6. Verify role and resource authorization together. A broad payment role does not grant access to every customer's payment method.
7. Produce a control/evidence/gap/owner table and remediation plan. Treat SAQ eligibility, transaction thresholds and formal attestation as decisions requiring the applicable current guidance.

## Example

Input: a checkout webhook is copied into application logs. Replace the log payload with approved event type, internal request ID and outcome fields. Exercise success, failure and retries using the processor's test environment. Verify the logs contain no synthetic account-data markers and that payment handling still meets its contract.

## Verification

- Data-flow inventory reconciled with actual integration and telemetry.
- Access denial produces no payment or data side effect.
- Redaction checked on nested data and exceptions.
- Evidence tied to actual configuration and test results, with explicit gaps.

## Limitations

Encryption, hosted checkout or a passed scan alone does not prove compliance. This package includes no automated audit script, payment processor client or certified encryption utility. Use reviewed integration code and qualified assessment for the actual environment; never use live cardholder data as a test fixture.

© sickn33 · MIT · sickn33/agentic-awesome-skills

Similar skills

All skills for Security →

pci-compliance by other authors comes first.

pci-compliance Seth Hobson The pci-compliance skill guides PCI DSS work for payment systems, including tokenization, encryption, access control, logging, and cardholder data handling. CX Codex +1 10,600installs pci-dss-compliance devops-skills pci-dss-compliance — a skill that maps PCI DSS v4.0 requirements onto your project: pick the right SAQ, scope the CDE, plan the controls. CX Codex +1 362installs pci-secure-software transilienceai Checks an app against PCI Secure Software Standard v2.0 and returns a status for every Test Requirement, tied to a cited line of code or docs. CX Codex +1 141installs dd-audit-compliance-report datadog-labs dd-audit-compliance-report is a Claude Code skill that generates Datadog audit reports for SOC 2 and PCI DSS. It runs on requests for auditor evidence or control compliance checks. CX Codex +1 561installs pci-audit briiirussell pci-audit reviews apps and infrastructure that handle payment card data against PCI DSS v4.0.1, settling scope first and then the engineering requirements. CX Codex +1 407installs PCI DSS v4.0.1 Compliance Checker shyshlakov PCI DSS v4.0.1 Compliance Checker is an MCP server for Claude Code that scans Go payment service codebases against PCI DSS v4.0.1. Every finding maps to a numbered requirement. CX Codex +1 ★ 5repo stars payment-pci-security vtex payment-pci-security enforces PCI DSS requirements and Secure Proxy routing when building payment connectors that handle card authorization, token exchange, and post-auth requests. CX Codex +1 1,100installs

From the same set187

The whole set →
vector-database-engineer vector-database-engineer picks a vector store and sets up embedding search for RAG, recommendations or similarity lookup. Comes in when recall and latency start to matter. CX Codex +1 ★ 50,109repo stars rag-implementation rag-implementation is a Claude Code skill that guides an eight-phase RAG implementation, from embedding selection to hybrid search and quality evaluation. CX Codex +1 ★ 50,109repo stars llm-application-dev-ai-assistant llm-application-dev-ai-assistant — a skill for designing conversational AI assistants: dialogue context, integration boundaries, validation. Fits projects where the bot calls tools and keeps memory of a user. CX Codex +1 ★ 50,109repo stars seo-content-auditor seo-content-auditor reads the draft you hand it, scores depth, E-E-A-T, readability and keyword use, then lists fixes. Useful before a post goes live. CX Codex +1 ★ 50,109repo stars security-compliance-compliance-check security-compliance-compliance-check guides regulatory compliance checks for GDPR, HIPAA, SOC2, and PCI-DSS, generating gap analyses, checklists, and technical control code. CX Codex +1 ★ 50,109repo stars varlock-claude-skill The varlock-claude-skill skill adds explicit checks for environment variables and secret exposure across Claude sessions, terminals, logs, and Git commits. CX Codex +1 ★ 50,109repo stars secrets-management secrets-management — a skill that walks an agent through secret handling in CI/CD: picking a backend, scoping access, rotating credentials and proving values never reach logs or artifacts. CX Codex +1 ★ 50,109repo stars security-scanning-security-sast security-scanning-security-sast — a skill for static code analysis (SAST) that detects vulnerabilities, hardcoded secrets, and security policy violations across multiple languages and frameworks. CX Codex +1 ★ 50,109repo stars

Project sponsors

Companies that keep this analytics open