CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/pci-dss-control-test-author

Use whenever tests must prove payment card handling meets PCI DSS v4.0: no stored or logged CVV, full card number (PAN), track data or PIN, card data only over strong TLS, cardholder data environment boundaries and segmentation, key management, SAQ level, scope reduction with hosted fields.

Quality

93%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%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 build-an-X workflow: executable test code per PCI requirement, explicit halt-and-remediate checkpoints at every consequential step, and a clean split between the inline workflow and two real, well-signaled reference files. The main deductions are the verbatim duplication of strategies.md content in Step 7 and test code that references undeclared ORM models and clients beyond the documented harness stubs.

Suggestions

Remove or compress the 'PAN-storage format default (Req 3.4)' paragraph in Step 7 — it restates references/strategies.md almost word-for-word; a one-line pointer to the reference file is enough.

Declare CardVault, AuditLog, client, and user in the helper-stubs section (or replace them with the harness stubs like export_database() / recent_logs()) so every code block's identifiers are grounded and copy-paste executable.

Trim the Step 1 aside about segmentation-testing cadence (6-month / qualified tester) or move it to the segmentation section of the scope catalog, since it is assessment-process context rather than test-authoring instruction.

DimensionReasoningScore

Conciseness

The body is code-dense and assumes competence (no padding explaining what PCI DSS is), but the Step 7 paragraph "PAN-storage format default (Req 3.4): the four is_* checks ... are an OR because pre-existing systems..." duplicates references/strategies.md nearly verbatim, and the Step 1 aside "must be performed at least every 6 months by a qualified internal resource OR external penetration tester" is tangential context. This fits the 4 anchor (efficient with minor over-explanation to trim) rather than the 5 anchor's every-token-earns-its-place.

4 / 5

Actionability

Mostly executable pytest-style code with concrete patterns (regexes, harness stubs, explicit assertions), but several identifiers are used without being declared in the helper-stub section or elsewhere: "CardVault.objects.first()", "client.post('/cde-api/login')", "AuditLog.objects.filter", "user.access_card". This matches the 4 anchor (concrete code with minor gaps) — not the 5 anchor's fully copy-paste-ready coverage — though the harness-stub framing partially justifies the environment-dependent parts.

4 / 5

Workflow Clarity

Seven explicitly sequenced steps, each mapping to a numbered PCI requirement, with five of the six test steps carrying an explicit "Checkpoint" validation gate ("halt and remediate the network policy before proceeding", "File a severity-1 finding and trigger your incident response process before re-running", "immediate secret rotation before continuing") — clear feedback loops for error recovery. This matches the 5 anchor; the destructive/batch cap does not apply since these are assert-only verification tests, and the 4 anchor's 'most checkpoints' understates how consistently they appear.

5 / 5

Progressive Disclosure

SKILL.md is the workflow; the bulk catalog material (SAQ table, gateway-specific hosted-fields patterns, anti-patterns) is correctly offloaded to references/pci-scope.md and references/strategies.md, both of which exist in the bundle, are one level deep, and are clearly signaled with their contents described ("The full scope catalog - SAQ level selection (A / A-EP / D), PAN-storage rules, per-gateway hosted-fields patterns ... is in references/pci-scope.md"). Matches the 5 anchor's well-signaled one-level-deep references with easy navigation; the minor Step 7 duplication is a conciseness issue, not a structural one.

5 / 5

Total

18

/

20

Passed

Description

100%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 dense, trigger-rich description that explicitly states when to use the skill and concretely enumerates what the resulting tests prove across the full PCI DSS v4.0 surface. It is third-person/imperative in voice, free of fluff, and unmistakably distinct from neighboring compliance skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete verification targets — "no stored or logged CVV, full card number (PAN), track data or PIN, card data only over strong TLS, cardholder data environment boundaries and segmentation, key management, SAQ level, scope reduction with hosted fields" — comprehensively covering the PCI DSS test surface with no vague language. It matches the 5 anchor (multiple specific concrete actions, comprehensive coverage) and is clearly above the 4 anchor, which anticipates gaps in coverage.

5 / 5

Completeness

Both elements are explicit: 'when' via the leading "Use whenever tests must prove payment card handling meets PCI DSS v4.0" and 'what' via the colon-enumerated list of assertions the tests prove. This matches the 5 anchor (clearly and explicitly answers both what AND when with concrete trigger phrases); the 4 anchor would require the 'when' to be less explicit than it is here.

5 / 5

Trigger Term Quality

It contains the natural vocabulary a user needing this skill would actually say: "PCI DSS", "payment card", "CVV", "PAN", "track data", "PIN", "TLS", "segmentation", "SAQ", "hosted fields", "scope reduction". Within this domain the jargon IS the natural language (developers say CVV/PAN/SAQ, not paraphrases), matching the comprehensive 5 anchor rather than the 4 anchor's "a few natural terms missing".

5 / 5

Distinctiveness Conflict Risk

"PCI DSS v4.0" payment-card compliance testing is a clear niche with distinct triggers (CVV, PAN, SAQ, hosted fields) and minimal conflict risk — it would not fire for adjacent compliance skills (GDPR, HIPAA, SOC 2) which have different trigger vocabulary. Matches the 5 anchor exactly.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page