Pci Dss
Use when the user asks about PCI DSS — the v4.0 (or v4.0.1) twelve requirements, scoping the cardholder data environment (CDE), Self-Assessment Questionnaires (SAQs), Reports on Compliance (ROCs), tokenization, segmentation, merchant levels, or PCI's customized vs defined approach to validation. For merchants, service providers, and their assessors.
Install
npx skills add scytale-labs/GRC-Claude-Skills --skill pci-dssgit clone --depth 1 https://github.com/scytale-labs/GRC-Claude-Skills.git /tmp/GRC-Claude-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/GRC-Claude-Skills/skills/pci-dss ~/.claude/skills/pci-dssPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# PCI DSS Skill You are an expert on the Payment Card Industry Data Security Standard, current with **v4.0.1** (June 2024), the in-force version following v4.0's grace period. ## When to use - Determining merchant level and the right validation path (SAQ vs ROC) - Scoping the cardholder data environment (CDE) and segmentation justification - Implementing or reviewing the 12 requirements - Choosing between the **Defined Approach** (prescriptive controls) and the **Customized Approach** (objective-based with assessor review) - Tokenization, P2PE, and SAQ reduction strategies - Preparing for a QSA assessment or designated entity supplemental validation (DESV) ## Core knowledge (load on demand) - The 12 requirements (organized by 6 goals) — see `references/12-requirements.md` - SAQ types and eligibility — see `references/saq-types.md` - CDE scoping and segmentation — see `references/scoping-cde.md` ## Working style 1. **Scope first.** PCI applies to systems that store, process, or transmit cardholder data (CHD), plus connected systems. Aggressive segmentation reduces scope dramatically. 2. **Cite requirements precisely** — e.g., `Req 3.5.1` (PAN rendered unreadable), `Req 8.4.2` (MFA for non-console admin access), `Req 11.4.x` (intrusion detection), `Req 12.10` (incident response). 3. **Distinguish merchant level vs SAQ vs ROC.** Merchant level (1–4) is brand-set thresholds; SAQ vs ROC is the validation method.
Details
- Skill name
pci-dss- Repository
- scytale-labs/GRC-Claude-Skills
- Path
skills/pci-dss/SKILL.md- License
- MIT
- Repo updated
- 16 April 2026
FAQ
What does the Pci Dss skill do?
Use when the user asks about PCI DSS — the v4.0 (or v4.0.1) twelve requirements, scoping the cardholder data environment (CDE), Self-Assessment Questionnaires (SAQs), Reports on Compliance (ROCs), tokenization, segmentation, merchant levels, or PCI's customized vs defined approach to validation. For merchants, service providers, and their assessors.
How do I install the Pci Dss skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add scytale-labs/GRC-Claude-Skills --skill pci-dss. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pci Dss popular?
It lives in scytale-labs/GRC-Claude-Skills, which has 33 GitHub stars and 14 forks.
Related skills
Fedramp
33scytale-labs/GRC-Claude-Skills
Use when the user asks about FedRAMP — the US government cloud authorization program, impact levels (Low/Moderate/High/LI-SaaS), NIST SP 800-53 control baselines, the System Security Plan (SSP), 3PAO assessment, JAB vs Agency authorization paths, the FedRAMP Marketplace, the ATO (Authority to Operate), or continuous monitoring obligations. For cloud service providers selling to US federal agencies.
Gdpr
33scytale-labs/GRC-Claude-Skills
Use when the user asks about GDPR — lawful bases for processing, data subject rights (DSRs), Records of Processing Activities (ROPA, Article 30), Data Protection Impact Assessments (DPIA, Article 35), international data transfers (SCCs, adequacy, TIA), controller vs processor obligations, breach notification (Articles 33–34), or DPO appointment. For controllers, processors, and sub-processors operating in the EU/EEA or targeting EU residents.
Hipaa
33scytale-labs/GRC-Claude-Skills
Use when the user asks about HIPAA — Privacy Rule, Security Rule (administrative, physical, technical safeguards), Breach Notification Rule, Business Associate Agreements (BAAs), the HITECH Act, OCR audits, or determining whether an organisation is a covered entity or business associate. For US healthcare providers, health plans, clearinghouses, and their business associates and subcontractors.
Sox Itgc
33scytale-labs/GRC-Claude-Skills
Use when the user asks about SOX ITGC (Sarbanes-Oxley IT General Controls) — access management, change management, computer operations, system development, control testing, working papers, deficiency remediation, deficiency severity (SD / MW), or moving from point-in-time to continuous ITGC monitoring. For publicly traded companies, pre-IPO companies preparing for SOX, and their internal audit and finance teams.
Diagnose Errors
48amplitude/mcp-marketplace
Investigates errors across network failures, JavaScript errors, and error clicks to identify what's broken, where, and why. Use when the user says "what's broken", "errors are up", "why are users seeing errors", "JS errors", "network failures", "5xx spike", "something is broken", or wants to triage product reliability issues.
Project Manager
52korchard333/claude-power-platform-community
Power Platform Project Manager (Laura). Use when: gathering requirements, defining acceptance criteria, planning work breakdown, orchestrating multi-agent workflows, tracking deliverables. Handles: requirements elicitation, user stories, Definition of Done governance, agent routing, quality checkpoints. Trigger when user says "plan this", "what do we need", "gather requirements", "orchestrate", or starts a new multi-step Power Platform project.
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.