SKILLEMALL.ai
GitHub ↗ RU Sign in

AB qa-only

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 1 file body ≈ 4 447 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Report-only QA testing.

As a process B 70/100 · Nearly there — weak spots: when it triggers, inputs and preconditions

AnalyzerData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
94
Quality 40%
85
Run on models
none yet
Process rating
B
70/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
20
Result and completion w 14
60
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Bash Read Write AskUserQuestion
    • low Dangerous commands cmd-pipe-to-shell-known-host SKILL.md:120
      Pipe-to-shell installer from a well-known host (still executes remote code) (quoted — discussed, not commanded)
      3. If `bun` is not installed: `curl -fsSL https://bun.sh/install | bash`
      quoted

    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 70/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 20When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 70Execution cost. Instruction body is 4447 tokens
    • 85Steps. 100 steps, 1 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Failures and branches. 5 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 13 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (3 tags): a typed call is more reliable

    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

    • +4Description does not say when NOT to use the skill (false activations)
    • -5TODO / placeholder text left in the skill
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 3 example trigger phrases
    • +3Description length 304: enough signal without eating the budget
    • +4Structure: 34 headings
    • +3Step-by-step instructions: 100 items
    • +3Output format is stated explicitly
    • +4Has examples (18 code blocks)

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