CtrlK
BlogDocsLog inGet started
Tessl Logo

prd-writer

Turn a feature idea into a clear PRD — problem, users, requirements, and success metrics.

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 ./apps/desktop/electron/default-skills/prd-writer/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is a tight, well-structured instruction-only skill with a clear process and output template, scoring high across all dimensions. The main improvement would be adding a short worked-example PRD to push actionability and conciseness of guidance toward the top anchor.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with only minor editorial gloss ('A good PRD isn't a feature list', 'Non-goals prevent scope creep as much as goals drive it') that could be trimmed; it is efficient but not quite the every-token-earns-its-place level of 5.

4 / 5

Actionability

It provides a concrete section-by-section template, a sequenced 4-step process, and an explicit output structure (Summary, Problem, Users & Context, Goals/Non-goals, Requirements, Success Metrics, Risks & Open Questions); the missing worked example PRD is the gap that keeps it from 5.

4 / 5

Workflow Clarity

'How to work' lays out a clear 4-step sequence and 'If you can't state the problem, the feature isn't ready' acts as a soft gate on step 1; no explicit validation checkpoints are present, but they are not required for non-destructive doc writing, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references, so the well-organized sections (When to use, What a PRD needs to answer, Principles, How to work, Output format) qualify it for the simple-skill 5 exception.

5 / 5

Total

17

/

20

Passed

Description

61%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 names a distinct niche with a clear 'what', but it lacks any 'Use when...' trigger guidance, which caps completeness and limits trigger-term quality. Adding an explicit when-clause with natural synonyms would lift the two capped dimensions.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when turning a feature idea, request, or rough notes into a PRD or one-pager.'

Add natural synonyms users say — 'product spec', 'product requirements document', 'one-pager' — to broaden trigger-term coverage.

Spell out PRD once ('product requirements document (PRD)') so the acronym is discoverable by users who don't use the abbreviation.

DimensionReasoningScore

Specificity

The description gives one concrete action ('Turn a feature idea into a clear PRD') plus an output breakdown (problem, users, requirements, success metrics), matching the anchor that names a domain with limited distinct actions; it is not a 4 because only one verb is offered and the rest are deliverables rather than separate actions.

3 / 5

Completeness

The 'what' is clearly stated but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3 and matches the anchor for a clear what with missing when.

3 / 5

Trigger Term Quality

'PRD', 'feature idea', 'requirements', and 'success metrics' are natural terms a user would say, giving good keyword coverage; it falls short of 5 because common synonyms like 'product spec', 'one-pager', or the spelled-out 'product requirements document' are missing.

4 / 5

Distinctiveness Conflict Risk

'PRD' names a clear niche with low conflict risk, but minor overlap with adjacent writing skills and the absence of explicit trigger phrasing keep it from a 5.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
holaboss-ai/holaOS
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.