SKILLEMALL.ai
GitHub ↗ RU Sign in

BC qa-test-planner

Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

davila7/claude-code-templates Agent Skills author: davila7 MIT 8 files · 2 scripts body ≈ 4 545 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers.

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

GeneratorFigmaData and analyticstype 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
B
91/100
safety, quality, tests
Safety 60%
99
Quality 40%
78
Run on models
none yet
Process rating
C
64/100
Has gaps
Result and completion w 14
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: RA-Skills, RA-Skills

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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/bug_report_templates.md:301
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - [ ] Privilege escalation

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "trigger"

Process rating: all ten parameters 64/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 8 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4545 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 112 steps
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress

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 165: enough signal without eating the budget
  • +4Structure: 37 headings
  • +3Step-by-step instructions: 112 items
  • +4Has examples (17 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)
  • +3All 2 scripts are documented

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