SKILLEMALL.ai

AC security-audit

Audit codebases and infrastructure for security issues. Use when scanning dependencies for vulnerabilities, detecting hardcoded secrets, checking OWASP top 10 issues, verifying SSL/TLS, auditing file permissions, or reviewing code for injection and auth flaws.

ClawHub Agent Skills author: gitgoodordietrying v1.0.0 2 files body ≈ 3 846 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

AnalyzerSoftware developmentInfrastructureSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
98
Quality 40%
84
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

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

    ✓ No critical or high findings

    Medium and low: 2
    • low Secrets in code secret-password-literal SKILL.md:446
      Hard-coded password / key literal (may be an example) (placeholder value)
      API_KEY="sk-a…..."
      placeholder
    • low Secrets in code secret-password-literal SKILL.md:453
      Hard-coded password / key literal (may be an example) (placeholder value)
      API_KEY=sk-a…...
      placeholder

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 52/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 40Consistency. Frontmatter name (security-audit) differs from the folder (security-audit-toolkit)
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 13 steps
    • 100Execution cost. Instruction body is 3846 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
    • +1No license
    • +2Single-language instructions
    • +3Description length 260: enough signal without eating the budget
    • +4Structure: 30 headings
    • +3Step-by-step instructions: 13 items
    • +4Has examples (22 code blocks)

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

    External checks

    ClawHub: suspicious
    This security-audit guide is mostly purpose-aligned, but it needs review because it suggests broad host inspection, unpinned tool execution, automatic fixes, and persistent git hooks without enough scoping or approval guidance.
    LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026