SKILLEMALL.ai

BC sqlmap-database-pentesting

Provide systematic methodologies for automated SQL injection detection and exploitation using SQLMap.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 3 127 tokens Open the sourcegithub.com analyzed 3 d ago

Provide systematic methodologies for automated SQL injection detection and exploitation using SQLMap.

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

AnalyzerSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
97
Quality 40%
78
Run on models
none yet
Process rating
C
58/100
Has gaps
Result and completion w 14
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

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

    ✓ No critical or high findings

    Medium and low: 3
    • low Risky intent intent-offensive-security SKILL.md:2
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      name: sqlmap-database-pentesting
    • low Risky intent intent-offensive-security SKILL.md:24
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # SQLMap Database Penetration Testing
    • low Risky intent intent-offensive-security SKILL.md:36
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - **Authorization**: Written permission for penetration testing activities

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"

    Process rating: all ten parameters 58/100

    • 0Result and completion. Does not say what the result is
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 37 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3127 tokens
    • 100Progress reporting. Reports progress
    • 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 101: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Structure: 48 headings
    • +3Step-by-step instructions: 37 items
    • +4Has examples (24 code blocks)

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