SKILLEMALL.ai
GitHub ↗ RU Sign in

CC api-security-auditor

(no description)

ClawHub Hermes author: heroinyan-stack v1.0.0 MIT-0 2 files body ≈ 2 201 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

APIs are the 1 attack vector for web applications (Gartner, 2026).

As a process C 55/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, running it twice

IntegrationSecuritytype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
C
73/100
safety, quality, tests
Safety 60%
97
Quality 40%
37
Run on models
none yet
Process rating
C
55/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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 skill-card.md:17
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    Developers and security reviewers use this skill to perform static API security reviews of REST and GraphQL endpoints before release, audit, or penetration testing. It helps organize findings by OWASP
  • low Risky intent intent-offensive-security SKILL.md:46
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Needs to prepare for a penetration test or security audit
  • low Risky intent intent-offensive-security SKILL.md:261
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Does not replace professional penetration testing for regulated industries

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

Against the Agent Skills spec

  • error description-missing SKILL.md: no `description` — the skill can never trigger
  • note frontmatter-key unknown frontmatter key "trigger_keywords"
  • note frontmatter-key unknown frontmatter key "pricing"

Process rating: all ten parameters 55/100

  • 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
  • 30Running it twice. 5 mutating operations with no state check
  • 50When it triggers. States when to use, but not when not to
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 41 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2201 tokens

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

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

External checks

ClawHub: clean
This skill is a static API security-audit guide with no install scripts, persistence, credential use, or hidden runtime behavior found.
LLM: benign (high) · VirusTotal: · 13 Aug 2026