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 defines its purpose, lists concrete actions, provides explicit trigger guidance, and occupies a distinct niche. It follows the recommended pattern of stating what it does, when to use it, and what terms trigger it. The description is concise without being vague.
| 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 terms like 'beads', 'ralph-tui', 'PRD to beads'. This is a very narrow 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 well-structured, highly actionable skill that provides clear executable commands and a complete worked example for converting PRDs to beads. Its main weakness is moderate verbosity—some sections are redundant (dependency ordering appears twice) and the content could be ~30% shorter without losing clarity. The workflow is well-sequenced with a useful validation checklist.
Suggestions
Consolidate the 'Story Ordering' and 'Dependencies with bd dep add' sections into a single section to eliminate redundancy about dependency ordering.
Move the 'Conversion Rules' numbered list into the checklist at the end, since it largely restates guidance already given in preceding sections.
| 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 the conversion rules section largely restates what was already covered. The good/bad criteria examples and right-sized/too-big examples add value but could be tighter. It doesn't over-explain basic concepts Claude knows, but there's room to consolidate. | 2 / 3 |
Actionability | Provides fully executable bash commands with exact `bd create` and `bd dep add` syntax, HEREDOC patterns, concrete flag usage, and a complete end-to-end example converting a PRD to bead commands. The output is copy-paste ready and leaves no ambiguity about what to produce. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: extract quality gates → create epic → create child beads → add dependencies → run ralph-tui. The checklist at the end serves as a validation checkpoint, and the skill explicitly handles the error case of missing quality gates. Dependency ordering is well-explained with correct/wrong examples. | 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, the skill is long enough that sections like the full example and the splitting guidance could benefit from being in separate referenced files. The note about future tracker plugins hints at broader architecture but doesn't provide navigation. | 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.