CtrlK
BlogDocsLog inGet started
Tessl Logo

ralph-tui-prd

Generate a Product Requirements Document (PRD) for ralph-tui task orchestration. Creates PRDs with user stories that can be converted to beads issues or prd.json for automated execution. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

63

Quality

74%

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 ./skills/ralph-tui-prd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

A well-structured, actionable PRD-generation skill with a clear workflow and closing checklist. It is held back from top marks by repetition of the quality-gates content and a long inline example that adds token weight without proportional value.

Suggestions

De-duplicate the quality-gates example, which appears nearly verbatim in Step 1, Step 2, and the example PRD — show it once and reference it.

Tighten the worked example PRD (e.g., trim to 2 user stories) so the structure section's format examples carry the load rather than a near-redundant full example.

Add an explicit validation/retry step (e.g., 'if a user story's acceptance criteria are not verifiable, re-ask before finalizing') to push workflow_clarity to a clear checkpoint loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient but repeats the same quality-gates question and example in multiple places, and the full worked example PRD re-states content already shown in the structure section, adding padding.

3 / 5

Actionability

It provides concrete, executable guidance: exact question formats, the `[PRD]...[/PRD]` output markers, a full copy-paste-ready example PRD, and specific file naming. Minor gaps in that some instructions are advisory rather than prescriptive.

4 / 5

Workflow Clarity

A clear sequenced workflow (clarify -> adaptively probe -> generate -> wrap) with a closing checklist acting as a validation checkpoint, but validation is implicit (a checklist) rather than an explicit fail-and-recover loop.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections (The Job, Step 1, Step 2, examples, checklist) with no bundle files and no nested references; the full inline example is somewhat long for a SKILL.md overview but appropriately placed for this single-purpose skill.

4 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description that explicitly states both what it does and when to trigger it with natural user phrases. Minor overlap risk on the generic planning/requirements triggers keeps it just below perfect distinctiveness.

Suggestions

Qualify the generic triggers (e.g., 'plan this feature for ralph-tui', 'spec out a ralph-tui task') to reduce overlap with general planning skills.

Name a couple more concrete PRD outputs explicitly to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain (PRD generation for ralph-tui) and several concrete actions ('Creates PRDs with user stories', 'converted to beads issues or prd.json for automated execution'), but the actions are somewhat broad and not fully enumerated.

4 / 5

Completeness

It clearly answers both 'what' (generates a PRD with user stories convertible to beads issues or prd.json) and 'when' via an explicit 'Triggers on:' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes explicit natural trigger phrases ('create a prd', 'write prd for', 'plan this feature', 'requirements for', 'spec out'), which are phrases users would naturally say, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The ralph-tui-specific framing and PRD-specific triggers make it fairly distinct, but generic phrases like 'plan this feature' and 'requirements for' could overlap with general planning or spec skills.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
subsy/ralph-tui
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.