CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pci-compliance

Implement PCI DSS compliance requirements for secure handling of payment card data and payment systems. Use when securing payment processing, achieving PCI compliance, or implementing payment card security measures.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/payment-processing/skills/pci-compliance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

The body delivers concrete, largely executable patterns for the highest-value PCI topics (prohibited-data handling, tokenization, encryption) with a well-signaled reference file. It is held back by a lengthy restatement of the 12 PCI DSS requirements, pseudocode-ish spots in the Stripe example, and the absence of any explicit workflow or validation sequence for achieving and verifying compliance.

Suggestions

Cut or compress the 'PCI DSS v4.0.1 Requirements (12 Core Requirements)' listing to a one-line pointer (the titles are knowledge Claude already has) and drop the opening sentence that restates the description.

Fix the Stripe tokenization example: replace the Python method with a docstring-embedded JavaScript snippet ending in 'pass' with an actual fenced JS block for the client-side code, and import json (and define SecurityError) so the Python examples run as written.

Add an explicit sequenced workflow with validation checkpoints — e.g., 1. classify compliance level, 2. confirm no prohibited data storage (validate_no_prohibited_storage), 3. tokenize/encrypt, 4. verify against the compliance checklist in references/details.md — and move the full class implementations to references/details.md to slim SKILL.md.

DimensionReasoningScore

Conciseness

Mostly efficient code-centric content, but roughly 40 lines restate the 12 PCI DSS requirement titles and compliance-level thresholds Claude already knows, the opening sentence duplicates the description, and the 'PCI DSS v4.0.1' version pin is time-sensitive without deprecation framing — fitting the some-unnecessary-explanation anchor rather than the minor-trimming one.

3 / 5

Actionability

Provides mostly executable, concrete code (PAN masking, Stripe token charges, AES-256-GCM encrypt/decrypt, Talisman HTTPS config) covering common cases. Minor gaps keep it from copy-paste-ready: the Stripe client-side example embeds JavaScript inside a Python docstring ending in 'pass', TokenVault uses json.dumps without importing json, and SecurityError is undefined.

4 / 5

Workflow Clarity

The topical ordering (Data Minimization → Tokenization → Encryption) implies a progression but there is no explicit step sequence, no validation checkpoints, and no compliance-verification step such as how to confirm or test compliance — matching the sequence-present-but-checkpoints-missing anchor rather than the most-checkpoints-present one.

3 / 5

Progressive Disclosure

Good structure with clear section headers and a real, one-level-deep reference ('More detailed templates and worked examples live in references/details.md') that exists in the bundle and appropriately holds access control, audit logging, SAQ guidance, and checklists. The main gap is that ~150 lines of full class implementations remain inline in SKILL.md where the top anchor expects a leaner overview.

4 / 5

Total

14

/

20

Passed

Description

78%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 that clearly states both capability and explicit 'Use when' triggers in third person. Its main gaps are limited action specificity ('implement', 'secure handling') and missing a few natural trigger synonyms like 'credit card data' and 'PCI audit'.

DimensionReasoningScore

Specificity

Names the domain precisely ('PCI DSS compliance requirements', 'payment card data and payment systems') with a couple of concrete actions, but 'implement' and 'secure handling' are generic and coverage is not comprehensive, matching the 1-2-concrete-actions anchor rather than the several-specific-actions anchor above.

3 / 5

Completeness

Explicitly answers both what ('Implement PCI DSS compliance requirements for secure handling of payment card data and payment systems') and when ('Use when securing payment processing, achieving PCI compliance, or implementing payment card security measures') with three concrete trigger phrases, matching the top anchor; the weaker anchors lack either an explicit 'when' clause or concrete triggers.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('securing payment processing', 'achieving PCI compliance', 'implementing payment card security measures') with good coverage, but misses common variations like 'credit card data', 'cardholder data', and 'PCI audit', so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

PCI DSS compliance is a clear niche with distinct triggers ('PCI DSS', 'payment card data'), but 'securing payment processing' could overlap with a generic application-security skill, giving minor conflict risk rather than minimal.

4 / 5

Total

16

/

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

wshobson/agents

Path

plugins/payment-processing/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.