SKILLEMALL.ai
GitHub ↗ RU Sign in

CC compliance-checker

Audits a codebase or business process for regulatory compliance across GDPR, HIPAA, SOC2, CCPA, and PCI-DSS. Scans for PII handling, data retention, encryption, access controls, audit logging, consent management, and data transfer issues. Generates a structured compliance report with findings, gap analysis, remediation steps, and evidence requirements.

OneWave-AI/claude-skills Agent Skills author: OneWave-AI 6 files body ≈ 1 242 tokens Open the sourcegithub.com↗ analyzed 6 h ago

Audits a codebase or business process for regulatory compliance across GDPR, HIPAA, SOC2, CCPA, and PCI-DSS.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSecuritytype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
97
Quality 40%
71
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 3

✓ No critical or high findings

Medium and low: 3
  • low Risky intent intent-offensive-security references/output-template.md:285
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | 11.4 | Penetration testing performed | [status] | [severity] | [ref] |
  • low Risky intent intent-offensive-security references/output-template.md:377
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | Penetration Test Reports | Annual penetration testing results | [exists/needed] | [path] |
  • low Risky intent intent-offensive-security references/output-template.md:406
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | Penetration Test Reports | Annual internal and external pen test results | [exists/needed] | [path] |

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 28 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1242 tokens
  • 100Running it twice. No mutating operations
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 354: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 28 items
  • +4Reference files are cited in the instructions (5 of 5)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.