CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-review

Review a proposed change against requirements, regressions, verification evidence, and relevant security risks.

62

Quality

74%

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 ./.claude/skills/vibe-review/SKILL.md

The canonical home for this skill is vibe-review in KhazP/vibe-coding-prompt-template

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, instruction-only review procedure that respects token budget and gives concrete guidance with a defined finding format. Its main gaps are the absence of a worked example and explicit numbered checkpoints.

DimensionReasoningScore

Conciseness

Two lean paragraphs with every sentence carrying an instruction ("Trace changed behavior into its callers and tests", "Do not claim independent checks unless you ran them"), assuming Claude's competence and adding no padding, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Gives concrete, specific guidance and a defined finding format ("file/line, trigger, impact, and suggested correction"), but provides no example finding output, leaving a minor gap versus the fully copy-paste-ready level-5 anchor.

4 / 5

Workflow Clarity

A clear implicit sequence (read diff/instructions → trace into callers and tests → look for issues → report findings) with verification discipline ("disclose remaining verification gaps"), though presented as prose without explicit numbered checkpoints; it is read-only review, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed and no bundle files present; content is organized into an examination paragraph and a reporting paragraph, good structure with minor gaps versus the well-signaled, sectioned level-5 anchor.

4 / 5

Total

17

/

20

Passed

Description

66%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 concretely names the review domain and its key dimensions and is largely distinct, but it omits an explicit 'Use when...' trigger clause, which caps its completeness and leaves some natural trigger synonyms uncovered.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke the skill (e.g., reviewing a diff, PR, or staged change against its requirements).

Include common trigger synonyms users say — 'diff', 'pull request', 'PR', 'code review' — alongside the existing terms.

Tie the trigger to a concrete entry point so it is distinguishable from generic code-review skills.

DimensionReasoningScore

Specificity

Names the domain and several concrete review dimensions — "requirements, regressions, verification evidence, and relevant security risks" — covering multiple specific actions with only minor gaps, fitting the 'lists several specific actions' anchor rather than the fully comprehensive level 5.

4 / 5

Completeness

Clearly states what the skill does, but lacks any "Use when..." or equivalent explicit trigger guidance; per the rubric a missing trigger clause caps completeness at 3, and the level-4 anchor requires an explicit 'when'.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ("review", "proposed change", "regressions", "security risks") but omits common synonyms/variations such as "diff", "PR", or "code review", matching the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The 'proposed change against requirements, regressions, verification evidence, and security risks' niche is fairly distinct, though it has minor overlap risk with general code-review skills, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

15

/

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