vibe-build

Implement an approved new-project slice and report actual checks. For changes to an existing app use vibe-change.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/vibe-build/SKILL.md

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 exceptionally lean and well-structured with strong validation discipline for risky operations, scoring top marks on conciseness and progressive disclosure. Its main weakness is actionability: it relies on high-level direction rather than executable commands or concrete examples.

Suggestions

Add a short numbered checklist of the core build steps to make the sequence explicit and easy to follow.

Include one or two concrete example commands (e.g. how to run the project's checks or record a recovery checkpoint) to raise actionability.

Optionally show a minimal example of the MEMORY.md progress/next-steps update format so the reporting protocol is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Three tight paragraphs with no padding and no explanation of concepts Claude already knows; every sentence carries actionable instruction, matching the lean-and-efficient anchor.	5 / 5
Actionability	It gives concrete direction (specific files to read, run the project's checks, use ../vibe-verify/SKILL.md, named report fields) but no executable commands or code, delegating specifics to other files and leaving key details implicit.	3 / 5
Workflow Clarity	A clear read-criteria-implement-check-report sequence is present with explicit validation checkpoints (recovery checkpoint before risky changes, run checks, never fabricate a commit), though steps are not numbered and a few checkpoints are implicit.	4 / 5
Progressive Disclosure	A short, well-organized skill under 50 lines with a single one-level-deep, clearly signaled external reference (../vibe-verify/SKILL.md) and no bundle files, fitting the simple-skill exception for a top score.	5 / 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 is concise and distinguishes itself from vibe-change with a clear boundary, but it lacks natural user-facing trigger terms and a positive 'Use when' clause, capping completeness and trigger quality. Adding concrete trigger phrases would materially improve activation.

Suggestions

Add a positive 'Use when...' clause (e.g. 'Use when starting a new project from an approved slice') alongside the existing vibe-change boundary.

Replace internal jargon ('slice', 'actual checks') with natural terms users would say, such as 'new project', 'build', and 'verification'.

List one or two more concrete actions (e.g. 'scaffold the project', 'run checks') to broaden the action vocabulary.

Dimension	Reasoning	Score
Specificity	Names the domain ('approved new-project slice') with concrete actions 'Implement' and 'report actual checks', but does not enumerate several specific actions, matching the 1-2 concrete actions anchor rather than the multi-action anchor.	3 / 5
Completeness	It has a clear 'what' (implement a slice and report checks) but no positive 'Use when...' trigger clause — only a negative boundary for vibe-change — so per the missing-trigger cap it sits at the clear-what/weak-when anchor.	3 / 5
Trigger Term Quality	Terms like 'new-project slice', 'approved', 'actual checks', and 'vibe-change' are internal jargon rather than natural phrases a user would say, so it falls below the midpoint with only domain-specific vocabulary and no common user utterances.	2 / 5
Distinctiveness Conflict Risk	It carves a distinct new-project niche and explicitly disambiguates from the sibling skill ('For changes to an existing app use vibe-change'), leaving only minor overlap risk with closely related build skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: KhazP/vibe-coding-prompt-template
Path: .claude/skills/vibe-build/SKILL.md
Commit: b00eb84

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.