SKILLEMALL.ai

AB qa-expert

Sets up QA testing processes: test strategies, Google Testing Standards test cases, P0-P4 bug tracking, quality metrics, progress reports, autonomous execution via master prompts, and OWASP security testing, with third-party QA handoff docs. Use when establishing QA infrastructure, writing test cases, executing test plans, or tracking bugs. Not for auditing an already-rendered UI (use frontend-visual-qa).

daymade/claude-code-skills Agent Skills author: daymade MIT 15 files · 2 scripts body ≈ 3 072 tokens Open the sourcegithub.com↗ analyzed 32 h ago

Sets up QA testing processes: test strategies, Google Testing Standards test cases, P0-P4 bug tracking, quality metrics, progress reports, autonomous…

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

AnalyzerData and analyticsSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
98
Quality 40%
95
Run on models
none yet
Process rating
B
70/100
Nearly there
Failures and branches w 10
0
Running it twice w 4
30
Result and completion w 14
40
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 Exfiltration read-dotenv references/day1_onboarding.md:26
      Reads a .env file (documentation of a security skill)
      cp .env.example .env
      security skill
    • low Risky intent intent-offensive-security SKILL.md:184
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      1. **A01: Broken Access Control** - RLS bypass, privilege escalation

    Files scanned: 15. 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 70/100

    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 9 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 88 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3072 tokens
    • 100Progress reporting. Reports progress
    • low 11 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
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 408: enough signal without eating the budget
    • +4Structure: 26 headings
    • +3Step-by-step instructions: 88 items
    • +4Has examples (7 code blocks)
    • +4Reference files are cited in the instructions (11 of 11)
    • +3All 2 scripts are documented

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