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.
91
88%
Does it follow best practices?
Impact
99%
1.52xAverage 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 well-crafted skill description that clearly communicates its purpose, specifies concrete actions, and provides explicit trigger guidance. It uses third-person voice correctly, includes both a 'Use when' clause and explicit trigger terms, and occupies a very distinct niche that minimizes conflict risk with other skills.
| 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 execution context (ralph-tui). These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (converts PRDs to beads, creates epics with child beads for user stories) and 'when' (explicit 'Use when' clause plus explicit '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'. Also includes domain terms like 'PRD', 'epic', 'user story', and 'ralph-tui' that users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with domain-specific terminology ('beads', 'ralph-tui', 'PRD to beads'). These are niche terms unlikely to conflict with other skills, creating a clear and unique trigger profile. | 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 that provides clear executable commands and a comprehensive end-to-end example. Its main weakness is verbosity—several concepts are explained redundantly across sections, and the monolithic structure could benefit from splitting detailed examples into referenced files. The workflow is clear with good validation via the final checklist.
Suggestions
Consolidate the 'Story Ordering' and 'Dependencies with bd dep add' sections to eliminate redundant dependency ordering explanations.
Move the full end-to-end example into a separate EXAMPLES.md file and reference it from the main skill to reduce length and improve progressive disclosure.
| 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 bd dep add' sections, and conversion rules repeat what was already covered. Good/bad examples for acceptance criteria and story sizing are helpful but could be tighter. Some sections like the note about future tracker plugins are unnecessary context. | 2 / 3 |
Actionability | Provides fully executable bash commands with exact `bd create` and `bd dep add` syntax, HEREDOC patterns, and a complete end-to-end example converting a PRD to beads. The commands are copy-paste ready with clear flag usage and real-world content. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: extract quality gates → create epic → create child beads → add dependencies → run ralph-tui. The final checklist serves as an explicit validation checkpoint before execution, and 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 external documentation for advanced topics. While the sections are well-organized with clear headers, the length suggests some content (like the full example or splitting guidelines) could be split into separate reference files. For a skill of this complexity, some progressive disclosure would improve scannability. | 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.