SKILLEMALL.ai
GitHub ↗ RU Sign in

CD flow-test-strategy-execution

Orchestrate comprehensive test strategy with test suite execution, coverage validation, defect triage, and regression analysis

jmagly/aiwg Agent Skills author: jmagly 1 file body ≈ 6 070 tokens Open the sourcegithub.com↗ analyzed 9 h ago

Orchestrate comprehensive test strategy with test suite execution, coverage validation, defect triage, and regression analysis

As a process D 47/100 · Unfinished process — References files that are not bundled: templates/test/master-test-plan-template.md, templates/test/test-case-card.md, templates/test/use-case-test-card.md

AnalyzerData 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
C
79/100
safety, quality, tests
Safety 60%
100
Quality 40%
48
Run on models
none yet
Process rating
D
47/100
Unfinished process
References files that are not bundled: templates/test/master-test-plan-template.md, templates/test/test-case-card.md, templates/test/use-case-test-card.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: flow-test-strategy-execution (jmagly/aiwg)

The same skill appears in 1 more place: aiwg

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. The text references files that are not there: add them or drop the references.
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 · 0

✓ No critical or high findings

Files scanned: 1. 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")
  • warning body-long SKILL.md body ≈ 6070 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: templates/test/master-test-plan-template.md
  • warning missing-ref reference to a missing file: templates/test/test-case-card.md
  • warning missing-ref reference to a missing file: templates/test/use-case-test-card.md
  • warning missing-ref reference to a missing file: templates/test/defect-card.md
  • warning missing-ref reference to a missing file: templates/test/test-evaluation-summary-template.md
  • note frontmatter-key unknown frontmatter key "namespace"
  • note frontmatter-key unknown frontmatter key "commandHint"

Process rating: all ten parameters 47/100

Will not run. References files that are not bundled: templates/test/master-test-plan-template.md, templates/test/test-case-card.md, templates/test/use-case-test-card.md
  • 0Tools and files. 5 referenced file(s) missing: templates/test/master-test-plan-template.md, templates/test/test-case-card.md, templates/test/use-case-test-card.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 70When it triggers. States when to use, but not when not to
  • 70Execution cost. Instruction body is 6070 tokens
  • 100Steps. 77 steps
  • 100Consistency. Name and required fields are in place
  • low 12 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 126: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 77 items
  • +4Has examples (27 code blocks)

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