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 a narrow, specific capability (converting PRDs to beads for ralph-tui), provides explicit 'Use when' guidance, and lists concrete trigger terms. The domain-specific terminology makes it highly distinctive and unlikely to conflict with other skills. The description is concise yet comprehensive.
| 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 epics with child beads) and 'when' (explicit 'Use when' clause plus a 'Triggers on' list with specific phrases). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms: 'create beads', 'convert prd to beads', 'beads for ralph', 'ralph beads', 'br beads'. These cover the natural variations a user familiar with this toolchain would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with domain-specific terms like 'beads-rust', 'br CLI', 'ralph-tui', and 'PRD to beads'. This is a very clear niche that is 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 strong, highly actionable skill with clear workflow sequencing and a comprehensive end-to-end example. Its main weakness is length—there's some redundancy between sections (dependency ordering appears twice) and the content could be more concise by trimming explanatory text that Claude can infer. The single-file structure works but is pushing the limits of what should be inline vs. referenced.
Suggestions
Consolidate the 'Story Ordering' and 'Dependencies with br dep add' sections to eliminate redundant dependency ordering explanations.
Trim the 'Story Size' section—the examples are useful but the explanatory paragraphs about ralph-tui spawning fresh agents could be reduced to one line since this is context Claude can retain from a brief mention.
| 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, and the good/bad criteria examples repeat patterns. Some sections like 'Story Size' over-explain concepts Claude can infer. However, most content is domain-specific and not general knowledge Claude would already have. | 2 / 3 |
Actionability | Provides fully executable bash commands with correct syntax, a complete end-to-end example converting a PRD to beads, specific HEREDOC syntax guidance, and copy-paste ready `br create` and `br dep add` commands. The example section alone is highly actionable with real input/output. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: extract quality gates → create epic → create child beads → add dependencies → sync. The checklist at the end serves as a validation checkpoint, and the skill explicitly addresses error cases (missing quality gates section, stories too large). The dependency ordering rules provide clear guardrails against incorrect sequencing. | 3 / 3 |
Progressive Disclosure | The content is entirely self-contained in one file with no references to supporting documents, which is reasonable given no bundle files exist. However, at ~250 lines, some sections (the full example, the comparison table, the splitting guidance) could benefit from being extracted to separate reference files. The structure within the file is well-organized with clear headers. | 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
8191b80
- 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.