CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vibe-verify

Exercise a running product against acceptance criteria and report evidence. Build success alone does not verify behavior.

Quality

72%

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 ./workflow/skills/vibe-verify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-structured process skill: it defines a concrete reporting framework, covers fallback behavior when tooling is unavailable, and sets clear safety limits, all without padding. Its only real gaps are the absence of an example evidence report and unnumbered workflow steps.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concepts are re-explained and nearly every sentence adds operational guidance. It sits just below anchor 5 because of minor trims available (the screenshot caution appears in two nearby sentences), matching anchor 4.

4 / 5

Actionability

Concrete process guidance throughout: a named three-status report (Setup/Build/Behavior checked) with what to record for each, an explicit fallback labeled "Not checked", and clear safety boundaries. It falls short of anchor 5's copy-paste-ready standard only in that no example evidence report is shown.

4 / 5

Workflow Clarity

A clear sequence runs from reading acceptance criteria, through identifying applicable checks, to exercising the journey and reporting three statuses, with recording requirements acting as checkpoints. It matches anchor 4 rather than 5 because the steps are not explicitly numbered and error-recovery loops are only implicit.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is organized into coherent labeled sections and bullets. Per the rubric's simple-skill provision, this earns a 5.

5 / 5

Total

17

/

20

Passed

Description

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

The description states a clear, distinct capability in third person without padding, but it lacks any explicit "when to use" trigger guidance and misses the natural vocabulary (test, check, verify) users would most likely employ. It is a solid but incomplete description sitting at the midpoint of the rubric.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to verify, test, or check that a built feature actually works, or wants evidence beyond a passing build."

Include natural trigger synonyms users would say — "test the app", "check it works", "smoke test", "acceptance testing" — to broaden keyword coverage.

Enumerate one or two more concrete actions (e.g. which kinds of checks or evidence artifacts) to lift specificity from two actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Exercise a running product against acceptance criteria and report evidence" names the domain plus two concrete actions, but coverage is not comprehensive — no product types, evidence kinds, or check categories. This matches anchor 3 (domain + 1-2 concrete actions) rather than anchor 4, which requires several specific actions.

3 / 5

Completeness

The "what" is clear, but there is no "Use when..." clause; the "when" is only weakly implied by "Build success alone does not verify behavior". Per the judging guidelines, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ("acceptance criteria", "running product", "verify behavior", "build success"), but common user phrasings like "test the app", "check it works", "smoke test", or "QA" are missing. Anchor 3 (some relevant keywords, missing common variations/synonyms) is the best fit — not 4, since more than a few natural terms are absent.

3 / 5

Distinctiveness Conflict Risk

The niche — exercising a running product against acceptance criteria to gather evidence — is mostly distinct with a clear trigger concept, with only minor overlap risk against general testing or run/launch skills. Fits anchor 4 rather than 5 because the verify/test framing could collide with adjacent skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

KhazP/vibe-coding-prompt-template

Path

workflow/skills/vibe-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.