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.
Install with Tessl CLI
npx tessl i github:subsy/ralph-tui --skill ralph-tui-create-beadsOverall
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 provides specific actions, explicit trigger terms, clear when/what guidance, and occupies a distinct niche. The only minor consideration is that users unfamiliar with 'beads' or 'ralph-tui' terminology might not know to use these triggers, but the PRD-related terms provide good fallback coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Convert PRDs to beads', 'Creates an epic with child beads for each user story'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Convert PRDs to beads, creates epic with child beads') and when ('Use when you have a PRD and want to use ralph-tui with beads'). Includes explicit 'Triggers on:' clause. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'create beads', 'convert prd to beads', 'beads for ralph', 'ralph beads'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining PRDs, beads, and ralph-tui. The domain-specific terminology (beads, ralph-tui, epic) makes it very 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, actionable skill with excellent executable examples and clear workflow guidance. The complete PRD-to-beads conversion example is particularly valuable. Main weakness is length - the document could be more concise by reducing redundant explanations and potentially splitting the large example into a separate file.
Suggestions
Trim redundant explanations of dependency ordering (appears in multiple sections with overlapping content)
Consider moving the full PRD-to-beads example to a separate EXAMPLES.md file and linking to it
Remove the 'Wrong order' example - the 'Correct order' list already makes the point clearly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant explanations (e.g., explaining what ralph-tui does multiple times, repeating dependency ordering concepts). The 'Wrong order' example and some explanatory text could be trimmed. | 2 / 3 |
Actionability | Excellent executable examples with complete bash commands using HEREDOC syntax. The full PRD-to-beads conversion example is copy-paste ready with realistic content. Commands like `bd create` and `bd dep add` are fully specified. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow: extract quality gates → create epic → create child beads → add dependencies → run ralph-tui. The checklist at the end serves as explicit validation. Dependency ordering is thoroughly explained 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. The example section alone is substantial and could be a separate file. No external references for advanced topics. | 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.