ralph-tui-create-beads

Convert PRDs to beads for ralph-tui execution. Creates an epic with child beads for each user story. Use when you have a PRD and want to use ralph-tui with beads as the task source. Triggers on: create beads, convert prd to beads, beads for ralph, ralph beads.

1.52x

Quality

76%

Does it follow best practices?

Impact

99%

1.52x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ralph-tui-create-beads/SKILL.md

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.

Highly actionable with concrete, copy-paste-ready commands and a full worked example. Weaker on conciseness (repeated dependency-ordering content) and workflow clarity (no post-creation validation for this batch operation), and the monolithic single-file structure leaves progressive disclosure underdeveloped.

Suggestions

Add a post-creation verification step (e.g. cat .beads/beads.jsonl and confirm each child bead + bd dep add resolved) to satisfy the batch-operation validation requirement and lift workflow clarity above 3.

De-duplicate the schema→backend→UI ordering guidance, which appears in both 'Story Ordering' and 'Dependencies with bd dep add', to improve conciseness.

Move the large worked example and/or the 'Splitting Large PRDs' detail into a one-level-deep reference file (e.g. references/example.md) referenced from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence on generic concepts, but repeats the schema→backend→UI dependency ordering across 'Story Ordering' and 'Dependencies with bd dep add', and the worked example is lengthy; these could be tightened.	3 / 5
Actionability	Fully executable guidance: copy-paste-ready `bd create` commands with single-quoted HEREDOC syntax, `bd dep add` calls with stated semantics, priority values, and a complete end-to-end worked example covering the common case.	5 / 5
Workflow Clarity	A clear numbered job sequence and a pre-creation checklist exist, but creating many beads is a batch operation with no post-creation verification (e.g. confirm .beads/beads.jsonl, validate dependencies resolved), which caps workflow clarity at 3 per the batch-operation rule.	3 / 5
Progressive Disclosure	Well-sectioned with clear headers, but the skill is a single ~230-line monolith with no bundle/reference files; the large worked example and detailed rules are inlined rather than split into one-level-deep references.	3 / 5
	Total	14 / 20 Passed

Description

87%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 what it does and when to use it, with concrete actions and natural trigger phrases. Minor room to expand action coverage and synonym breadth.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Convert PRDs to beads', 'Creates an epic with child beads for each user story') naming the domain and the core transformation steps, but omits related actions like dependency wiring and quality-gate extraction, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Convert PRDs to beads... Creates an epic with child beads') and when ('Use when you have a PRD and want to use ralph-tui with beads as the task source. Triggers on: ...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural trigger phrases ('create beads', 'convert prd to beads', 'beads for ralph', 'ralph beads') plus an explicit 'Use when' clause, though the terms are domain-narrow rather than spanning synonyms and file extensions.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (ralph-tui + beads + PRDs) with distinct, domain-specific triggers, making conflict with unrelated skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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: subsy/ralph-tui
Path: skills/ralph-tui-create-beads/SKILL.md
Commit: af44322

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.