CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aw-verify

Proves a feature works end to end, locally or on the PR preview: reuses the brief and specs `/aw` wrote, gets the environment ready, probes it in the browser (ui-verify) with concurrency and fault cases, then reads what the services recorded (telemetry-verify), fixes what it finds on a local stack one commit per finding, and reports with real screenshots. `setup` writes the committed `.agents/aw/` config every suite skill reads. Triggers on "/aw-verify".

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/testing/aw-verify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body is a tightly written orchestrator playbook: ordered run card, concrete dispatch commands, explicit feedback loops, and a definition of done. Its one serious defect is that the progressive-disclosure layer is broken — nearly all referenced rules/*.md files are missing from the bundle, so steps that say "Read a step's rule before its first action" cannot be executed as shipped.

Suggestions

Ship the missing ./rules/ directory (config.md, intent.md, local-stack.md, browser-verification.md, findings.md, fix-loop.md, report.md, lessons.md, auth.md, setup.md, pr-comment.md, delegation.md) or remove the dead links and inline each run-card step's minimal procedure so the skill is executable from SKILL.md alone.

If the rules files will be added later, verify every markdown link target and anchor resolves within the bundle before publishing, since 12 of 13 external references currently 404.

Reduce link noise by linking each rules file once at its first mention instead of repeating pr-comment.md (3 links) and fix-loop.md/config.md/lessons.md (2 links each) with different anchors.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no padding, no explanations of concepts Claude already knows — e.g. the run card compresses each step to its essentials. It falls short of anchor 5 because a few passages (notably the long PR-comment paragraph stacking posting policy, trusted bots, and rendering rules into one sentence) are overloaded and could be trimmed or split for clarity.

4 / 5

Actionability

Mostly concrete and executable: an exact dispatch snippet (Skill("ui-verify", "run .agent/<branch>/specs.md --env <env> ...")), precise artifacts ("intent.md", "probes.jsonl", "findings.jsonl"), literal output strings ("telemetry: skipped (Dash0 MCP server '<name>' not connected)"), and a flag table. It is not anchor 5 because key execution details are delegated to rules/*.md files that are not present in the bundle, leaving gaps the body alone cannot fill.

4 / 5

Workflow Clarity

The Run card gives a clearly ordered 0–6 sequence with explicit validation and feedback loops — "After a fix, re-run the probe that found it; stop at `✅ verified` or at `--loops`", "restore every injected fault before the next batch", plus a verdict rule and a Definition-of-done checklist. It misses anchor 5 because each step's detailed procedure lives in the missing rules files, so the workflow has execution gaps as shipped.

4 / 5

Progressive Disclosure

References are well-labeled with section anchors (e.g. "[`rules/fix-loop.md § Own PR](./rules/fix-loop.md#own-pr-fix-until-verified)"), but scored against the actual bundle, 12 of the 13 distinct external targets — every ./rules/*.md link (config, intent, local-stack, browser-verification, findings, fix-loop, report, lessons, auth, setup, pr-comment, delegation) — do not exist; only references/design.md and scripts/verify-comment.mjs are present. The intended structure is good, but most navigation is broken, which fits anchor 2's minimal-structure/broken-organization level rather than anchor 1 (the body itself is well-organized, not a wall of text).

2 / 5

Total

14

/

20

Passed

Description

75%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 dense, action-rich description that clearly conveys what the skill does and carries an explicit trigger clause. Its weaknesses are the slash-command-only trigger guidance, some suite-internal jargon ("/aw", "ui-verify", "telemetry-verify") that obscures capabilities to a fresh reader, and a slightly generic phrase ("gets the environment ready").

Suggestions

Broaden the trigger clause beyond the slash command to natural-language conditions, e.g. "Use when asked to verify or prove a feature works end to end, locally or on a PR preview."

Briefly gloss suite jargon such as "/aw" or "(ui-verify)" so the capabilities read standalone rather than requiring knowledge of the surrounding skill suite.

DimensionReasoningScore

Specificity

Lists many concrete actions — "probes it in the browser (ui-verify) with concurrency and fault cases", "reads what the services recorded (telemetry-verify)", "fixes what it finds on a local stack one commit per finding, and reports with real screenshots" — but phrases like "gets the environment ready" are generic and "reuses the brief and specs `/aw` wrote" is opaque without suite context, leaving minor gaps that keep it below the comprehensive anchor 5.

4 / 5

Completeness

The "what" is explicit (probe in browser, read telemetry, fix, report) and "when" is present via the explicit trigger clause "Triggers on \"/aw-verify\"", which avoids the missing-trigger cap of 3; however the "when" covers only the slash command and gives no natural-language use conditions, so it is not the fully explicit anchor 5.

4 / 5

Trigger Term Quality

Good natural-term coverage: "Proves a feature works end to end", "verify", "browser", "telemetry", "real screenshots" are phrases a user would plausibly say, but common variations like "test the feature", "e2e", or "QA" are missing, so it stops short of the comprehensive-synonym anchor 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear orchestrator niche ("Proves a feature works end to end, locally or on the PR preview") distinct from generic verify/test skills, but it explicitly names sibling skills "ui-verify" and "telemetry-verify" whose domains overlap its own sub-actions, creating minor conflict risk with closely related skills.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 17 missing

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/testing/aw-verify/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.