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.
Install with Tessl CLI
npx tessl i github:subsy/ralph-tui --skill ralph-tui-create-beads-rustOverall
score
88%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 excels across all dimensions. It clearly specifies the concrete action (converting PRDs to beads with epic/child structure), explicitly states when to use it, and provides excellent trigger term coverage. The domain-specific terminology ensures it won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Convert PRDs to beads', 'Creates an epic with child beads for each user story', and names specific tools (beads-rust, br CLI, ralph-tui). | 3 / 3 |
Completeness | Clearly 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-rust'). Includes explicit 'Use when' clause and 'Triggers on' section. | 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'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining PRDs, beads-rust, ralph-tui, and br CLI. The domain-specific terminology (beads, ralph, br) makes conflicts with other skills very unlikely. | 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, actionable skill with excellent executable examples and clear workflow sequencing. The main weakness is verbosity - some concepts are repeated and the document could be more concise while maintaining clarity. The comprehensive example and checklist are particularly valuable for ensuring correct execution.
Suggestions
Consolidate the repeated explanations of dependency ordering (appears in 'Story Ordering', 'Dependencies with br dep add', and 'Conversion Rules') into a single authoritative section
Move the 'Differences from beads (Go version)' comparison table to a separate reference file since it's only needed for users migrating between tools
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations (e.g., explaining what ralph-tui does multiple times, repeating dependency ordering concepts). The 'Right-sized stories' vs 'Too big' section and the 'Good criteria' vs 'Bad criteria' examples add value but could be more condensed. | 2 / 3 |
Actionability | Excellent executable guidance with complete, copy-paste ready bash commands using proper HEREDOC syntax. The full example conversion from PRD to beads commands is comprehensive and directly usable. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow with explicit sequence: extract quality gates → create epic → create child beads → add dependencies → sync. The checklist at the end serves as validation, and the dependency ordering rules are explicit with correct/wrong examples. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a long monolithic document (~300 lines) that could benefit from splitting detailed examples or the comparison table into separate reference files. The note about the alternative skill is good progressive disclosure. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.