SKILLEMALL.ai

AB backend-security-coder

Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 2 397 tokens Open the sourcegithub.com analyzed 2 d ago

Expert in secure backend coding practices specializing in input validation, authentication, and API security.

As a process B 72/100 · Nearly there — weak spots: failures and branches, running it twice

AnalyzerSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
99
Quality 40%
87
Run on models
none yet
Process rating
B
72/100
Nearly there
Failures and branches w 10
0
Running it twice w 4
30
When it triggers w 12
50
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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Risky intent intent-offensive-security SKILL.md:34
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - **Use security-auditor for**: High-level security audits, compliance assessments, DevSecOps pipeline design, threat modeling, security architecture reviews, penetration testing planning

    Files scanned: 1. 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 72/100

    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 1 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 102 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2397 tokens
    • 100Progress reporting. Reports progress
    • low 10 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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 188: enough signal without eating the budget
    • +4Structure: 20 headings
    • +3Step-by-step instructions: 102 items
    • +3Output format is stated explicitly
    • +4Has examples (0 code blocks)

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