CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-agents

Create project agent instructions and tool configuration from agreed product and technical decisions.

54

Quality

61%

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

68%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 lean, actionable, and appropriately scoped for a short instruction-only skill, citing real CLI commands and file targets. Its main weakness is workflow clarity: scenarios are interleaved in prose without explicit validation checkpoints despite involving destructive setup operations.

Suggestions

Restructure the body into labeled sub-sections (e.g. "Targeted AGENTS.md edit", "Initial Vibe Workflow setup", "No filesystem access") so the scenario branching is explicit.

Add an explicit validation/verification checkpoint for destructive setup, e.g. run "npx vibeworkflow doctor" and confirm affected files are reviewed before applying replacement flags.

Consider a short numbered checklist for the initial-setup path to surface the sequence and its safeguards.

DimensionReasoningScore

Conciseness

The body is efficient, directive prose that assumes Claude's competence and avoids explaining known concepts; minor advisory sentences could be trimmed but nothing is heavily padded.

4 / 5

Actionability

Provides concrete executable guidance including specific CLI commands ("npx vibeworkflow --dry-run --json", "npx vibeworkflow doctor") and concrete file targets (AGENTS.md, docs/context-pack.md), with minor gaps in copy-paste-ready coverage.

4 / 5

Workflow Clarity

A rough scenario sequence (targeted edit, initial setup, no-filesystem fallback) is present but implicit in prose with no explicit validation checkpoints; since the skill touches destructive operations (file replacement, tool permissions), the rubric cap of 3 applies.

3 / 5

Progressive Disclosure

This short (~24 line) single-purpose skill keeps all content appropriately inline with no need for bundle files; the only gap is the absence of sub-headers to delineate the distinct scenarios, a minor organization issue.

4 / 5

Total

15

/

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 third-person, specific about its domain, and clearly states what the skill does, but it omits any explicit "when to use it" trigger guidance and lacks natural user-facing keywords and synonyms. It is a solid, concise statement that would benefit from an added trigger clause.

Suggestions

Append a "Use when..." clause naming concrete triggers, e.g. "Use when setting up or editing project AGENTS.md / agent instructions and tool configuration from agreed product and technical decisions."

Add natural synonyms users would actually say (e.g. "AGENTS.md", "agent setup", "configure project agents") alongside the current domain terms.

Tighten "tool configuration" to a more specific phrase to reduce overlap with generic setup/config skills.

DimensionReasoningScore

Specificity

Names the domain concretely ("project agent instructions and tool configuration") and source ("agreed product and technical decisions") with ~2 concrete actions, but does not enumerate a comprehensive set of specific actions.

3 / 5

Completeness

Clearly answers "what" (create agent instructions and tool config from decisions) but provides no "when" / "Use when..." trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ("agent instructions", "tool configuration", "product and technical decisions") but lacks the natural phrases a user would say (e.g. "set up AGENTS.md", "configure agents") and any synonyms or variations.

3 / 5

Distinctiveness Conflict Risk

Targets a recognizable niche (producing project agent instructions and tool config from product/technical decisions) with only minor overlap risk against closely related setup skills; not a 5 because the missing trigger guidance and broad "tool configuration" phrasing leave slight conflict risk.

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.