SKILLEMALL.ai

AC test-master

Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.

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

Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.

As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
99
Quality 40%
84
Run on models
none yet
Process rating
C
59/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

    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 references/security-testing.md:114
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)
      | **Access** | IDOR, privilege escalation |
      fixture

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "triggers"
    • note frontmatter-key unknown frontmatter key "role"
    • note frontmatter-key unknown frontmatter key "scope"
    • note frontmatter-key unknown frontmatter key "output-format"

    Process rating: all ten parameters 59/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
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 23 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 884 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)
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 189: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 23 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (10 of 10)

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