CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-prd

Write or revise an MVP product requirements document with scope and observable acceptance criteria.

60

Quality

70%

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

The canonical home for this skill is vibe-prd in KhazP/vibe-coding-prompt-template

SKILL.md
Quality
Evals
Security

Quality

Content

86%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-structured instruction skill that offloads detail to appropriately signaled reference files and gives a concrete content checklist with a clear output path. Its only gap is the absence of an inline PRD skeleton or worked example to lift actionability from 4 to 5.

DimensionReasoningScore

Conciseness

The ~27-line body is lean and directive, assumes Claude knows what a PRD is, and avoids padded explanations, matching anchor 5 ('lean and efficient; every token earns its place').

5 / 5

Actionability

Provides a concrete section checklist, an explicit output path, a Handoff Context field list, and two purpose-labeled references, but shows no inline PRD skeleton or worked example, matching anchor 4 ('mostly executable guidance; minor gaps').

4 / 5

Workflow Clarity

The implied gather-write-handoff sequence carries quality checkpoints ('Distinguish agreed facts from assumptions', 'Do not present planned acceptance checks as executed evidence'); it is a non-destructive writing task so no feedback-loop cap applies, matching anchor 4 ('clear sequence with most checkpoints present; minor validation gaps').

4 / 5

Progressive Disclosure

Under 50 lines with the question bank and CLI contract correctly offloaded to two real, one-level-deep references that are clearly signaled with usage context, matching anchor 5 ('clear overview with well-signaled one-level-deep references; content appropriately split').

5 / 5

Total

18

/

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 clearly conveys what the skill produces but lacks an explicit 'when to use it' trigger and common synonyms like 'PRD', leaving it mid-tier on completeness and trigger quality. It is reasonably specific and distinct within the PRD-writing niche.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to write or revise a PRD, product spec, or MVP requirements document.'

Include common synonyms users actually say such as 'PRD', 'spec', or 'feature spec' to broaden natural trigger coverage.

Expand action coverage slightly (e.g. 'scope it, define acceptance criteria, and flag open questions') to lift specificity from 3 toward 4.

DimensionReasoningScore

Specificity

Names the domain ('MVP product requirements document') and two concrete actions ('Write or revise') plus deliverable details, but does not list several specific actions, matching anchor 3 rather than 4.

3 / 5

Completeness

Clearly states what the skill does but provides no 'Use when...' trigger guidance; the missing-trigger guideline caps completeness at 3, matching anchor 3 ('clear what, when missing or weakly implied').

3 / 5

Trigger Term Quality

Contains relevant keywords ('MVP', 'product requirements document', 'scope', 'observable acceptance criteria') but omits common synonyms users say such as 'PRD', 'spec', or 'feature spec', matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

The MVP PRD niche is mostly distinct, though without an explicit trigger it could overlap with general planning/spec skills, matching anchor 4 ('mostly distinct; minor overlap 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.