SKILLEMALL.ai
GitHub ↗ RU Sign in

AC qa-expert

This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.

daymade/claude-code-skills Agent Skills author: daymade 9 files body ≈ 2 464 tokens Open the sourcegithub.com↗ analyzed 2 h ago

This skill should be used when establishing comprehensive QA testing processes for any software project.

As a process C 64/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

GeneratorData and analyticsSecuritytype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
98
Quality 40%
91
Run on models
none yet
Process rating
C
64/100
Has gaps
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
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:150
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      1. **A01: Broken Access Control** - RLS bypass, privilege escalation

    Files scanned: 9. 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 64/100

    • 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. 4 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 95 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2464 tokens
    • 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
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 518: enough signal without eating the budget
    • +4Structure: 26 headings
    • +3Step-by-step instructions: 95 items
    • +4Has examples (7 code blocks)
    • +4Reference files are cited in the instructions (5 of 5)
    • +3All 2 scripts are documented

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