SKILLEMALL.ai
GitHub ↗ RU Sign in

BC compliance-officer

Reviews marketing content against FTC, HIPAA, GDPR, SEC 482, SEC Marketing, CCPA, COPPA, and CAN-SPAM — 208 specific laws with URLs.

ClawHub Agent Skills author: Arber X v1.1.0 15 files body ≈ 504 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

AnalyzerSecurityLegalInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
86
Quality 40%
77
Run on models
none yet
Process rating
C
51/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 · 14

✓ No critical or high findings

Medium and low: 14
  • low Secrets in code secret-high-entropy-token README.md:22
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    Explain rule FTC-…ion
    detector
  • low Secrets in code secret-high-entropy-token references/instructions.md:183
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    - A rule ID (e.g., `FTC-…ion`)
    detector
  • low Secrets in code secret-high-entropy-token references/rules-can-spam.json:3
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "CAN-…nal",
    quoted
  • low Secrets in code secret-high-entropy-token references/rules-can-spam.json:52
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "CAN-…ose",
    quoted
  • low Secrets in code secret-high-entropy-token references/rules-can-spam.json:193
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "CAN-…ier",
    quoted
  • low Secrets in code secret-high-entropy-token references/rules-can-spam.json:242
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "CAN-…ess",
    quoted
  • low Secrets in code secret-high-entropy-token references/rules-can-spam.json:343
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "CAN-…nor",
    quoted
  • low Secrets in code secret-high-entropy-token references/rules-ftc-endorsements.json:938
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "FTC-…ion",
    quoted
  • low Secrets in code secret-high-entropy-token references/rules-gdpr.json:193
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "GDPR…est",
    quoted
  • low Secrets in code secret-high-entropy-token references/rules-gdpr.json:387
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "GDPR…ion",
    quoted
  • low Secrets in code secret-high-entropy-token references/rules-gdpr.json:660
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "GDPR…ons",
    quoted
  • low Secrets in code secret-high-entropy-token references/rules-gdpr.json:844
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "GDPR…ons",
    quoted
  • low Secrets in code secret-high-entropy-token references/rules-gdpr.json:1083
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "GDPR…ies",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:47
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    Explain rule FTC-…ion
    detector

Files scanned: 15. 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")

Process rating: all ten parameters 51/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
  • 30Running it twice. 1 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Steps. 5 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 504 tokens
  • 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
  • +2Single-language instructions
  • +3Description length 132: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 5 items
  • +4Has examples (6 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +1License stated

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

External checks

ClawHub: clean
This is an instruction-only compliance review skill with disclosed, purpose-aligned network use for fetching user-provided URLs.
LLM: benign (high) · VirusTotal: benign · 28 May 2026