ralph-tui-create-json
Convert PRDs to prd.json format for ralph-tui execution. Creates JSON task files with user stories, acceptance criteria, and dependencies. Triggers on: create prd.json, convert to json, ralph json, create json tasks.
92
88%
Does it follow best practices?
Impact
100%
1.21xAverage 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 its purpose, lists concrete capabilities, and provides explicit trigger terms. It occupies a distinct niche (PRD to ralph-tui JSON conversion) that minimizes conflict risk. The description is concise yet comprehensive, covering both what the skill does and when it should be activated.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Convert PRDs to prd.json format', 'Creates JSON task files with user stories, acceptance criteria, and dependencies'. These are concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (converts PRDs to prd.json format, creates JSON task files with user stories, acceptance criteria, and dependencies) and 'when' (explicit 'Triggers on:' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'create prd.json', 'convert to json', 'ralph json', 'create json tasks'. These cover multiple natural phrasings a user might use, including the tool name and file format. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specifically targets PRD-to-JSON conversion for ralph-tui execution. The combination of 'prd.json', 'ralph-tui', and specific task structure 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 well-structured, highly actionable skill that provides clear guidance for converting PRDs to prd.json format. Its main strengths are the complete input/output example, explicit anti-patterns, and the validation checklist. Its weaknesses are moderate verbosity (some sections repeat information covered elsewhere) and a monolithic structure that could benefit from splitting detailed reference material into separate files.
Suggestions
Consolidate the anti-patterns section into a more compact table or shorter format — four separate code blocks for wrong patterns is verbose when a brief list with one example would suffice.
Extract the full end-to-end example (Input PRD → Output prd.json) into a separate EXAMPLE.md file and reference it, reducing the main skill's length while keeping the schema template inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~250 lines) with some redundancy. The anti-patterns section, while useful, is verbose with four separate wrong examples. The conversion rules section largely repeats information already covered in the output format and other sections. However, most content is domain-specific knowledge Claude wouldn't inherently know. | 2 / 3 |
Actionability | Highly actionable with a complete JSON schema, a full input-to-output example (PRD markdown → prd.json), explicit anti-patterns with concrete wrong/right examples, and clear conversion rules. The output is copy-paste ready and leaves no ambiguity about the expected format. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: extract quality gates → parse stories → append gates to criteria → set dependencies → output JSON. The checklist at the end serves as a validation checkpoint before saving. The step-by-step process with explicit dependency ordering (schema → backend → UI) and the 'ask user if missing' fallback for quality gates provides good error recovery. | 3 / 3 |
Progressive Disclosure | The content is entirely monolithic in a single file with no references to supporting documents. For a skill of this length (~250 lines), some content like the full example or the anti-patterns section could be split into separate reference files. However, the sections are well-organized with clear headers, making navigation reasonable despite the length. | 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.