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.

56

Quality

64%

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 ./.agents/skills/vibe-change/SKILL.md
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 lean, well-sequenced change workflow with concrete guidance and a built-in report checklist, plus a single clearly signaled cross-skill reference. Main improvement is making the sequence an explicit numbered list with validation gates so checkpoints are unambiguous.

Suggestions

Convert the prose workflow into a numbered step list with explicit validation gates (e.g. baseline → implement → run affected checks → verify with vibe-verify → report).

Replace "appropriate approved commands" with a concrete example command or a pointer to where approved commands are defined.

Add short section headers (e.g. ## Baseline, ## Implement, ## Verify) to improve navigation and lift progressive disclosure to 5.

DimensionReasoningScore

Conciseness

Three dense paragraphs with no concept explanations Claude already knows and no padding; every line carries an instruction, matching the lean/efficient anchor.

5 / 5

Actionability

Concrete directives like "Establish the baseline with appropriate approved commands and one existing user journey", "Identify the smallest affected area and implement one feature", and the explicit report list ("Changed, Checked, Not checked, Next decision, Recovery") are actionable, though "appropriate approved commands" leaves the exact commands unspecified.

4 / 5

Workflow Clarity

A clear inspect → confirm → baseline → implement → add regression checks → rerun → verify → report sequence exists with checkpoints ("rerun the affected checks", "record a real recovery checkpoint"), but steps are prose rather than an explicit numbered checklist, leaving minor gaps.

4 / 5

Progressive Disclosure

Under 50 lines with a single clearly signaled one-level reference ("Use ../vibe-verify/SKILL.md") and logically phased paragraphs; it stops short of 5 only because sections lack headers that would aid navigation.

4 / 5

Total

17

/

20

Passed

Description

46%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, bounded purpose and distinguishes itself from the new-project workflow, but lacks an explicit trigger/"Use when" clause and natural keyword coverage. Adding when-to-use guidance with common user phrases would lift completeness and trigger quality.

Suggestions

Append a "Use when adding a small feature or change to an existing app..." clause with natural trigger phrases like "extend", "modify", or "add a feature".

Broaden trigger synonyms to match how users actually phrase incremental change requests.

Optionally list 1-2 more concrete sub-actions to push specificity from 1-2 actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Add one bounded feature to an existing app while preserving current behavior" names the domain and a concrete action plus constraints, but does not enumerate multiple specific actions, so it stops at the 1-2 concrete actions anchor rather than the comprehensive 5.

3 / 5

Completeness

It gives a clear "what" (add a bounded feature while preserving behavior) but no explicit "when"/trigger clause, so per the missing-trigger cap it cannot exceed 3.

3 / 5

Trigger Term Quality

The only natural phrases are "add ... feature" and "existing app"; there is no "Use when..." clause and common synonyms users would actually say (e.g. "modify", "extend", "change") are absent, leaving it with one or two generic keywords.

2 / 5

Distinctiveness Conflict Risk

"Add one bounded feature" plus "Do not restart the full new-project workflow" carves a distinct niche separate from the new-project skill, with only minor overlap risk against general coding skills.

4 / 5

Total

12

/

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.

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