CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured advisory skill with strong actionability and exemplary progressive disclosure — reference files exist, are one level deep, and are loaded conditionally per task. The main cost is token weight: duplicated disclaimers, a section on the wider PCI SSC ecosystem tangential to DSS compliance, and date-heavy status content that could be consolidated or moved to a reference.

Suggestions

Merge the two closing disclaimer blocks into one and trim it to two sentences, cutting ~10 lines of redundant tail content.

Move the 'PCI SSC Standards Ecosystem: Status' section (Secure SLC, MPoC, 3DS SDK/SPoC/CPoC) into a reference file or drop it, since it concerns standards other than PCI DSS and adds context cost to every invocation.

Consolidate date-sensitive status notes (FAQ 1331 update, RFC window, 'Last verified') into a single clearly-labeled status block or reference file so time-sensitive facts are easy to re-verify and update.

DimensionReasoningScore

Conciseness

Mostly efficient, table-driven, and rich in domain facts Claude cannot be assumed to know (SAQ control counts, merchant levels, v4.0 changes), but it carries trimmable material: two separate disclaimer blocks at the end, a tangential 'PCI SSC Standards Ecosystem: Status' section covering other standards (Secure SLC, MPoC, 3DS SDK), and pervasive specific dates/versions not isolated in a dedicated section.

3 / 5

Actionability

Concrete, executable guidance throughout — exact output table schemas per task type, a numbered SAQ question sequence, a fixed Requirement → What to Implement → Evidence → Audit Tips response template, and policy document element checklists. Minor abstractions remain (e.g., 'Walk through the decision logic to select the correct SAQ type').

4 / 5

Workflow Clarity

Five workflows are clearly sequenced with numbered steps, explicit status definitions (Compliant/Partial/Non-Compliant/N/A), and a conditional checkpoint (FAQ 1331 rule applied in SAQ workflow step 7). Advisory rather than destructive/batch work, so no validation cap applies, but explicit verification checkpoints are thin compared to the anchor-5 feedback-loop pattern.

4 / 5

Progressive Disclosure

Three real one-level-deep reference files, each signposted at point of use and again in a dedicated 'Reference Files' section with per-task 'When to load' conditions; summary tables stay inline while full detail (all 12 requirements, SAQ decision tree, complete change log) correctly lives in the references.

5 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, explicit 'what' and 'when', dense with natural trigger terms including quoted user questions. The only weakness is that capabilities are presented as a topic inventory rather than concrete verb-led actions, which slightly blurs what the skill actually does.

Suggestions

Lead with a few verb-led actions (e.g., 'Performs gap assessments, selects SAQ types, and scopes CDEs') before the topic list so the 'what' reads as capabilities rather than a keyword inventory.

DimensionReasoningScore

Specificity

Lists many concrete capabilities and topics — 'CDE scoping', 'SAQ types (A, A-EP, B, B-IP, C, C-VT, P2PE, D)', 'ROC, AOC, QSA assessments, ASV scans', 'tokenisation, encryption of PAN data' — but frames them as a coverage list ('advisor covering...') rather than verb-led actions, leaving minor gaps versus the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both 'what' ('Expert PCI DSS compliance advisor covering PCI DSS v4.0.1 (current) and v4.0') and 'when' ('Use this skill whenever a user asks about...', 'Also trigger for questions like...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and acronyms ('PCI DSS', 'payment card security', 'cardholder data', 'SAQ', 'QSA', 'ASV', 'tokenisation') plus verbatim user phrasings like 'are we PCI compliant?', 'how do I scope my CDE?', and 'which SAQ applies to us?', matching the anchor-5 example.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (PCI DSS compliance advising) with domain-specific triggers (SAQ, ROC, AOC, QSA, ASV, CDE) that are unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

Path

plugins/pci-compliance/skills/pci-compliance/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.