SKILLEMALL.ai

BF clawsec-feed

Security advisory feed with automated NVD CVE polling for OpenClaw-related vulnerabilities. Updated daily.

modbender/skill-library-mcp Agent Skills author: modbender MIT 5 files body ≈ 6 354 tokens Open the sourcegithub.com analyzed 2 d ago

Security advisory feed with automated NVD CVE polling for OpenClaw-related vulnerabilities.

As a process F 50/100 · Will not run — References files that are not bundled: ../../wiki/exploitability-scoring.md, ../clawsec-suite/SKILL.md

ProcedureGitHubAI and agentsInfrastructureSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
99
Quality 40%
51
Run on models
none yet
Process rating
F
50/100
Will not run
References files that are not bundled: ../../wiki/exploitability-scoring.md, ../clawsec-suite/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
20
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.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. The text references files that are not there: add them or drop the references.
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 Exfiltration exfil-webhook-url advisories/feed.json:406
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    "description": "OpenClaw is a personal AI assistant. Telegram bot tokens can appear in error messages and stack traces (for example, when request URLs include `https://api.telegram.org/bot<token>/...`
    placeholder

Files scanned: 5. 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")
  • warning body-long SKILL.md body ≈ 6354 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../../wiki/exploitability-scoring.md
  • warning missing-ref reference to a missing file: ../clawsec-suite/SKILL.md
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "clawdis"

Process rating: all ten parameters 50/100

Will not run. References files that are not bundled: ../../wiki/exploitability-scoring.md, ../clawsec-suite/SKILL.md
  • 0Tools and files. 2 referenced file(s) missing: ../../wiki/exploitability-scoring.md, ../clawsec-suite/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 6354 tokens
  • 100Steps. 47 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 18 top-level sections: this looks like several domains in one skill

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 106: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 38 headings
  • +3Step-by-step instructions: 47 items
  • +3Output format is stated explicitly
  • +4Has examples (22 code blocks)

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