CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-agents

Generate project agent instructions from agreed requirements and technical decisions. Not for ordinary incremental feature changes.

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

The canonical home for this skill is vibe-agents 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 token-efficient and actionable, with concrete CLI commands, a validation checkpoint, and sensible handling of destructive changes (--force guard). The main improvement is converting the prose workflow into an explicit numbered sequence with headers.

Suggestions

Convert the workflow into a numbered checklist so the sequence (read inputs → dry-run → initialize → fill placeholders → doctor → resolve errors) is unambiguous.

Add section headers (e.g. '## Setup', '## Fill placeholders', '## Chat without filesystem') to signpost the logical groups and lift progressive disclosure.

Specify how placeholders are filled (e.g. which file, which decision source maps to which placeholder) to close the actionability gap.

DimensionReasoningScore

Conciseness

The body is lean and dense, assuming Claude's competence throughout — it references 'vibe.project.json paths', 'Handoff Context', 'AGENTS.md', and 'agent_docs' without padding or explaining basics, and every sentence carries instruction.

5 / 5

Actionability

It provides concrete executable commands ('npx vibeworkflow --dry-run --json', 'npx vibeworkflow doctor') and specific file paths, but 'Fill required placeholders from decisions' leaves the exact mechanism implicit, a minor gap.

4 / 5

Workflow Clarity

There is a clear sequence (read PRD/Tech Design → dry-run → initialize → fill placeholders → doctor → resolve errors) with a validation checkpoint ('Run npx vibeworkflow doctor and resolve required setup errors'), but it is prose rather than an explicit ordered checklist, leaving minor sequencing gaps.

4 / 5

Progressive Disclosure

The body is short, self-contained, and grouped into logically distinct paragraphs (read inputs, setup, fill/verify, chat fallback), but it lacks explicit section headers; no bundle files exist to reference, so structure is good but not maximally signposted.

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 states a clear purpose and draws a useful negative boundary, but lacks a positive 'Use when...' trigger clause and natural trigger phrases, leaving it at a competent-but-not-exemplary level. Trigger term coverage and completeness are the main limiters.

Suggestions

Add an explicit positive 'Use when...' clause naming concrete triggers, e.g. 'Use when bootstrapping agent instructions from a freshly agreed PRD and Tech Design.'

Include natural trigger synonyms users would say ('set up project agents', 'generate AGENTS.md from the PRD') alongside the domain terms.

List 1-2 more concrete actions (e.g. 'reconcile PRD/Tech Design conflicts, fill template placeholders, run setup checks') to lift specificity.

DimensionReasoningScore

Specificity

It names the domain ('project agent instructions') and one concrete action ('Generate ... from agreed requirements and technical decisions'), but offers only that single action rather than a comprehensive list.

3 / 5

Completeness

A clear 'what' is present, but the 'when' is only weakly implied via the negative boundary 'Not for ordinary incremental feature changes' rather than an explicit positive 'Use when...' clause, capping completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'project agent instructions', 'agreed requirements', and 'technical decisions' are relevant but read as domain jargon; common natural variations a user would actually say are missing.

3 / 5

Distinctiveness Conflict Risk

The niche (generating agent instructions from a PRD/Tech Design) is fairly distinct, and the explicit exclusion of ordinary incremental changes reduces overlap risk, with only minor overlap with general scaffolding 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.

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.