pci-dss-validator
Pci Dss Validator - Auto-activating skill for Security Advanced. Triggers on: pci dss validator, pci dss validator Part of the Security Advanced skill category.
36
3%
Does it follow best practices?
Impact
100%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/pci-dss-validator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak, consisting essentially of just the skill name repeated as trigger terms and a category label. It provides no information about what the skill actually does, what specific PCI DSS validation tasks it performs, or when Claude should select it. It reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add concrete actions the skill performs, e.g., 'Validates configurations against PCI DSS requirements, checks compliance of network segmentation, reviews access control policies, and identifies gaps in cardholder data protection.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about PCI DSS compliance, payment card security audits, cardholder data environment validation, or PCI requirement checks.'
Remove the duplicate trigger term ('pci dss validator' is listed twice) and expand with natural variations users might say, such as 'PCI compliance', 'payment security', 'PCI audit', 'cardholder data protection'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only states the skill name and category ('Security Advanced') without describing what the skill actually does—no mention of validation steps, compliance checks, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'pci dss validator' repeated twice. While 'PCI DSS' is a relevant domain term, there are no natural user phrases like 'compliance check', 'payment card security', 'cardholder data', or 'PCI audit' that users would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'PCI DSS' does narrow the domain to payment card industry compliance, which is a fairly specific niche. However, the lack of concrete actions means it could still overlap with other security-related skills without clear differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty boilerplate template with no actual PCI DSS content. It provides no actionable guidance, no concrete validation steps, no compliance requirements, and no code or commands. It fails on every dimension because it contains no domain-specific information whatsoever—just generic placeholder text.
Suggestions
Add concrete PCI DSS validation content: list specific requirements (e.g., Requirement 1-12), provide actual validation checks, and include executable scripts or commands for scanning/auditing.
Define a clear multi-step workflow for PCI DSS validation (e.g., 1. Scope assessment, 2. Requirement mapping, 3. Evidence collection, 4. Gap analysis, 5. Remediation tracking) with explicit validation checkpoints.
Include actionable code examples such as network scan commands, configuration audit scripts, or compliance report templates that Claude can directly use.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with lean, domain-specific guidance that assumes Claude's existing knowledge of security concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no domain-specific information about PCI DSS validation, and every section is generic template text that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific PCI DSS requirements, no validation steps, no compliance checks. The content only describes what the skill supposedly does in vague, abstract terms without any executable or actionable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. PCI DSS validation inherently involves multi-step processes (scoping, requirement checking, evidence gathering, remediation) but none are described. There are no steps, no sequence, and no validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic template with no references to supporting files, no structured navigation, and no layered content. There are no bundle files to reference either, but the skill body itself lacks any meaningful organization beyond generic headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
13d35b8
- 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.