ralph-tui-create-beads-rust
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI). Creates an epic with child beads for each user story. Use when you have a PRD and want to use ralph-tui with beads-rust as the task source. Triggers on: create beads, convert prd to beads, beads for ralph, ralph beads, br beads.
91
88%
Does it follow best practices?
Impact
96%
1.60xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its purpose, specifies concrete actions, and provides explicit trigger guidance. It uses third-person voice correctly, includes a 'Use when' clause, and lists specific trigger terms. The domain-specific terminology ensures high distinctiveness with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Convert PRDs to beads', 'Creates an epic with child beads for each user story', and specifies the tool chain (beads-rust, br CLI, ralph-tui). These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (convert PRDs to beads, create epic with child beads for user stories) and 'when' (explicit 'Use when' clause plus a 'Triggers on' list with specific phrases). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'create beads', 'convert prd to beads', 'beads for ralph', 'ralph beads', 'br beads'. Also includes domain-specific terms like PRD, ralph-tui, beads-rust, and br CLI that users in this ecosystem would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: the intersection of PRDs, beads-rust (br CLI), and ralph-tui. The domain-specific terminology makes it extremely unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with executable examples and a clear workflow for converting PRDs to beads. Its main weakness is verbosity—some concepts are repeated across sections (dependency ordering appears in three places), and the entire document could benefit from splitting reference material (comparison table, splitting examples) into separate files. The checklist at the end is an excellent validation mechanism.
Suggestions
Consolidate the dependency ordering guidance into a single section instead of repeating it in 'Story Ordering', 'Dependencies with br dep add', and 'Conversion Rules'.
Move the 'Differences from beads (Go version)' comparison table and 'Splitting Large PRDs' examples into separate reference files, linked from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~250 lines) with some redundancy—dependency ordering is explained in both 'Story Ordering' and 'Dependencies with br dep add' sections. The good/bad criteria examples and right-sized/too-big story examples add value but could be tighter. Some sections like 'The Job' overview repeat what's detailed later. | 2 / 3 |
Actionability | Provides fully executable bash commands with proper HEREDOC syntax, a complete end-to-end example converting a PRD to beads, specific CLI flags, and copy-paste ready commands for every step including sync and running ralph-tui. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow: extract quality gates → create epic → create child beads → add dependencies → sync → run ralph-tui. Includes a comprehensive pre-creation checklist that serves as validation, handles the 'missing quality gates' edge case, and the dependency ordering is explicit with correct/wrong examples. | 3 / 3 |
Progressive Disclosure | All content is inline in a single file with no references to external documentation. While the sections are well-organized with clear headers, the conversion rules, splitting guidance, and comparison table could be split into separate reference files to keep the main skill leaner. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- subsy/ralph-tui
- Commit
1d4670f
- 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.