SKILLEMALL.ai
GitHub ↗ RU Sign in

BC security-sentinel

Scan the workspace for security vulnerabilities, exposed secrets, and misconfigurations.

ClawHub Agent Skills author: autogame-17 v1.0.1 6 files body ≈ 331 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

IntegrationSecuritytype 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
80/100
safety, quality, tests
Safety 60%
88
Quality 40%
69
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Secrets in code medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

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 · 8

✓ No critical or high findings

Medium and low: 8
  • medium Secrets in code secret-private-key index.js:16
    Private key material (detector / deny-list definition; key header without key body)
    { name: 'Private Key', regex: /-----BEGIN PRIVATE KEY----- …
    detectorheader only
  • low Secrets in code secret-high-entropy-token package-lock.json:24
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…HyM+jmUB…wDz+E2LA…ZDQ==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:33
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…1gh+ckoa…m0h+EZd1EhEumSB+ZdDL…Afg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:53
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…3dS+nxxS…uex+k0GF…oCQ==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:96
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…tQV+jkVj…fOB/iy3ssJCD+3KuZ…lAg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:120
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…JgI+2Q5U…e1E+Nyvgdz/aIyN…n58/GELp3+w==",
    detector

A further 2 matches are quotations in this security skill's documentation and are not counted as findings.

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 59/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 100Tools and files. No external tools needed
  • 100Steps. 7 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 331 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)
  • +3Description length 88: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 7 items
  • +4Has examples (2 code blocks)

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

External checks

ClawHub: clean
This skill behaves like a workspace security scanner, with some rough edges but no evidence of exfiltration, destructive behavior, or hidden persistence.
LLM: benign (high) · VirusTotal: suspicious · 28 May 2026