CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verification

Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.

Quality

83%

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

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

A tight, well-structured orchestration skill: a clear four-step workflow with explicit evidence checkpoints and stop conditions, concrete commands, and no filler. The only soft spots are a couple of environment-vague actions (browser checking tooling) and a body slightly long enough that some template/checklist content could be offloaded to reference files.

DimensionReasoningScore

Conciseness

The body is lean and dense — the layer/evidence table, the reporting contract ("Checking / Evidence / Next"), the common-breaks checklist, and the report template all assume Claude's competence and explain nothing the model already knows. It matches anchor 5 ("every token earns its place") rather than anchor 4, which reserves room for trimmable over-explanation; only a few rhetorical emphases ("Do not skip this step") exist and they carry operational weight.

5 / 5

Actionability

Concrete, executable guidance throughout: "Run `vercel logs`", "Check `.env.local`, `vercel env ls`", "check git diff or recent Write/Edit tool calls", "Scan `package.json` scripts, route structure (`app/` or `pages/`)", plus a specific boundary-break checklist (missing `await`, wrong HTTP method, import mismatch) and a copy-paste report template. It stays at anchor 4 rather than 5 because a few steps remain environment-dependent and unspecified, e.g. "Open the relevant page, check console, take screenshots" names no concrete browser tooling or command.

4 / 5

Workflow Clarity

Four clearly sequenced steps (infer story → evidence baseline → walk the data flow → report) with explicit checkpoints: "Report what you find at each layer before proceeding", the Checking/Evidence/Next contract, and a dedicated Stop Conditions section with error-recovery guidance ("first broken boundary — report it with evidence and a specific fix, do not continue"; flag observability gaps after two silent layers). This matches anchor 5's explicit validation checkpoints and error-recovery handling; anchor 4 would imply missing checkpoints, which isn't the case.

5 / 5

Progressive Disclosure

No bundle files (references/, scripts/, assets/) exist and none are referenced, so scoring is against the self-contained body, which is well-sectioned and easy to navigate. At ~98 lines it exceeds the under-50-line simple-skill carve-out that would allow a 5 without external references, and the report template and common-breaks checklist are content that could plausibly live in reference files, so anchor 4 ("most content appropriately placed; minor organization gaps") is the best fit rather than 5.

4 / 5

Total

18

/

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 strong description that clearly states a niche capability (end-to-end full-flow verification) with an explicit trigger clause including a natural user phrase. Its main limitation is trigger breadth — the 'when' signals are narrow relative to the many natural variations users would actually say.

Suggestions

Broaden the trigger clause with more natural variations users actually say, e.g. "verify the flow", "check if it works", "end-to-end test", "it almost works but", "works locally but not deployed".

Mention the evidence-based output (e.g., "reports each boundary with evidence and a specific fix") in the 'what' clause so the capability list is more comprehensive.

DimensionReasoningScore

Specificity

The description names two concrete actions — "infers what the user is building" and "verifies the complete flow end-to-end" — and enumerates the verification scope as "browser → API → data → response", which goes beyond anchor 3's bare 1–2 actions. It falls short of anchor 5's comprehensive action list because it omits other things the skill does (evidence gathering, structured reporting).

4 / 5

Completeness

Both halves are explicit: what — "verifies the complete flow end-to-end: browser → API → data → response"; when — "Triggers on dev server start and 'why isn't this working' signals". The 'when' clause is explicit and contains a concrete trigger phrase, but it lists only two signals versus anchor 5's fuller set of concrete trigger phrases, matching anchor 4's "'when' could be more explicit or specific".

4 / 5

Trigger Term Quality

It includes a verbatim natural user phrase ("why isn't this working"), plus "dev server start", "end-to-end", "verification", "flow", "browser", and "API" — good keyword coverage. Anchor 5 requires comprehensive synonym coverage (e.g., "verify the flow", "check if it works", "test end to end", "does it work"), which is only hinted at, so 4 fits better than 5 and clearly better than 3.

4 / 5

Distinctiveness Conflict Risk

"Full-story verification" of a browser → API → data → response flow carves a clear niche distinct from generic debugging or testing skills, with distinctive triggers (dev server start, "why isn't this working"). There is minor overlap risk with general 'debug this' requests, keeping it at anchor 4 rather than 5.

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_version

'metadata.version' is missing

Warning

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

Total

13

/

16

Passed

Repository

vercel/vercel-plugin

Path

skills/verification/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.