SKILLEMALL.ai
GitHub ↗ RU Sign in

BC complisec

EU compliance enforcement for AI agents — NIS2, GDPR, ISO 27001. ACTIVATE on EVERY prompt. Reads .compliance/profile.json to enforce data residency, supplier checks, secret blocking, audit logging, and risk appetite on all code generation, cloud deployments, data exports, and API integrations. Invoke /complisec setup to create the org profile.

ClawHub Agent Skills author: eyesecurity v1.0.0 MIT-0 25 files body ≈ 1 671 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

IntegrationSecurityInfrastructureAI and agentstype 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
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
72
Run on models
none yet
Process rating
C
57/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Broad scope meta-dynamic-shell USE-CASES.md:158
    Shell command executed automatically when the skill loads (Claude Code !`cmd` preamble)
    !`cat .compliance/profile.json 2>/dev/null || echo '{"status": "no profile yet — guide user through onboarding"}'`

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")

Process rating: all ten parameters 57/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 5 mutating operations with no state check
  • 40Consistency. Frontmatter name (complisec) differs from the folder (eu-compliance)
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 7 steps
  • 100Failures and branches. 6 branches, has a failure section
  • 100Execution cost. Instruction body is 1671 tokens
  • 100Progress reporting. Reports progress

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 345: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 7 items
  • +4Has examples (2 code blocks)

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

External checks

ClawHub: suspicious
This is a real compliance-assistance skill, but it asks for unusually broad, persistent influence over prompts, local files, memory, and compliance records.
LLM: suspicious (high) · VirusTotal: · 29 May 2026