CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-change

Add one bounded feature to an existing app while preserving current behavior. Do not restart the full new-project workflow.

58

Quality

68%

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-change/SKILL.md

The canonical home for this skill is vibe-change 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 an efficient, actionable instruction-only skill that sequences the work clearly and preserves behavior with explicit validation and recovery checkpoints. Its only notable gap is the lack of explicit section headers and the reference points to an external skill outside the bundle.

Suggestions

Add lightweight section headers (e.g., '## Inspect', '## Implement', '## Verify & report') to improve navigation and progressive disclosure.

Surface a short explicit numbered sequence for the core workflow to make checkpoints unmistakable.

Confirm the `../vibe-verify/SKILL.md` reference resolves or note the dependency explicitly so the single external reference is reliable.

DimensionReasoningScore

Conciseness

The body is lean and dense with no padding or over-explanation of concepts Claude already knows; every sentence instructs and earns its place.

5 / 5

Actionability

Provides concrete actionable guidance including a specific report format ('Changed, Checked, Not checked, Next decision, Recovery') and a concrete file reference; minor gaps remain as an instruction-only skill with no executable code or commands.

4 / 5

Workflow Clarity

A clear sequence is present (inspect, baseline, checkpoint, implement, regression checks, rerun, verify, report) with validation checkpoints like 'rerun the affected checks' and 'recovery checkpoint', though steps are in prose rather than an explicit numbered checklist.

4 / 5

Progressive Disclosure

Content is well organized into a logical flow with a single clearly-signaled one-level reference ('Use `../vibe-verify/SKILL.md`'); minor gaps as there are no section headers to aid navigation.

4 / 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 is concise and clearly states what the skill does, with a useful distinction from the new-project workflow. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and limits trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when adding a single feature to an existing app without restarting project setup').

Include natural user-facing synonyms such as 'small change', 'incremental feature', or 'tweak' to improve trigger-term coverage.

List one or two more concrete actions (e.g., 'run affected checks', 'record a recovery checkpoint') to lift specificity above 3.

DimensionReasoningScore

Specificity

Names the domain and a couple of concrete actions ('Add one bounded feature', 'preserving current behavior', 'Do not restart the full new-project workflow') but coverage is not comprehensive.

3 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause; the 'when' is only weakly implied, capping completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

Contains relevant keywords like 'feature', 'existing app', and 'behavior' but lacks natural trigger phrases or common synonyms a user would say.

3 / 5

Distinctiveness Conflict Risk

Explicitly carves a niche (bounded feature change vs the full new-project workflow), leaving only minor overlap risk with closely related 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
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.