CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qa-evidence

Run BDD scenarios and file the proof. Trigger: executing scenarios, test evidence, screenshots, QA results on a work item.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An opinionated, genuinely actionable process skill: concrete CLI commands, an exact evidence layout, explicit validation gates (Jev PASS discipline, BLOCKED classification), and well-designed feedback loops for re-runs and regressions. Its weaknesses are mild — the run order must be inferred from section order rather than a numbered sequence, and the central Jev interaction is described but not demonstrated.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — no explaining what BDD, Docker, or Loki is — and nearly every line carries a rule. A few aphoristic justification sentences ("Six months from now the name is all anyone has", "The evidence exists so a person can look at it. You do not have to.") could be trimmed without losing guidance, matching anchor 4 rather than 5.

4 / 5

Actionability

Concrete executable commands (docker compose logs --since 5m, ado wi comment/create-child), an exact evidence directory layout, and a precise fingerprint format (rule|screen|cause). The core browser/Jev flow is directed ("call jev_check_page with that snapshot and the Then verbatim") but never shown as a concrete invocation, and report.md's format is only loosely specified — minor gaps per anchor 4.

4 / 5

Workflow Clarity

Strong validation checkpoints ("A missing key or a failed Jev call is not PASS — it is BLOCKED") and real feedback loops (before/after re-run proof pairs, occurrence counting, regression reopen). However the run sequence is distributed across topic sections — the reader must assemble the order (read app-guide → pick instrument → run → capture → file) themselves — which fits anchor 4 rather than anchor 5's explicit ordered sequence with checklists.

4 / 5

Progressive Disclosure

No bundle files exist, so this is scored on the body's own structure: well-organized sections with clearly signaled, one-level-deep cross-references to other skills, each with a stated load condition ("Before the run, read .ywai/app-guide.md", "Load the jev-gate skill", "see condition-based-waiting", "Use the ado skill"). The Logs section carries environment-specific detail inline that could live in a reference file — good structure (anchor 4) with minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description that clearly states what the skill does and gives explicit, enumerated trigger guidance. The trigger coverage is good and the niche is distinct; the only weakness is that the what-side lists just two actions, leaving the skill's fuller scope (logs, bug filing, regression tracking) unadvertised.

Suggestions

Add one or two more concrete actions to the what-side (e.g., capture per-scenario screenshots and log evidence, file Bugs for failures) so the description reflects the skill's full scope.

Include a common natural variation in the trigger clause (e.g., "run the tests", "regression", or "Cucumber/BDD scenarios") to broaden keyword coverage.

Optionally add "capture" or "evidence" phrasing that distinguishes it from generic screenshot skills, reducing overlap risk.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("Run BDD scenarios", "file the proof") but does not list several specific actions — log capture, bug filing, and reporting detail all live in the body rather than the description. This matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive'; score 4 would require a broader list of specific actions.

3 / 5

Completeness

Explicitly answers both sides: "Run BDD scenarios and file the proof" (what) and "Trigger: executing scenarios, test evidence, screenshots, QA results on a work item" (when, with concrete trigger phrases). Matches anchor 5; anchor 4's caveat (when could be more explicit) does not apply since the trigger clause is specific and enumerated.

5 / 5

Trigger Term Quality

"executing scenarios", "test evidence", "screenshots", "QA results on a work item" are natural phrases users would say, covering both the run and filing sides. Missing common variations such as "run the tests", "regression", or framework names (Cucumber, Gherkin), so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"BDD scenarios" and "QA results on a work item" carve out a clear niche with distinct triggers, but "screenshots" and "test evidence" carry minor overlap risk with a general testing or screenshot skill. Mostly distinct (anchor 4) rather than minimal conflict risk (anchor 5).

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

YoizenSA/dev-ai-workflow

Path

ywai/skills/qa-evidence/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.