ralph
Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json from this, ralph json.
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ralph/SKILL.mdQuality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
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 concrete examples and a complete JSON schema. The workflow is clear with proper validation via the final checklist. Main weakness is length - some sections are repetitive and the document could benefit from splitting detailed examples into separate files.
Suggestions
Consolidate the 'Right-sized stories' and 'Too big' sections into a single compact table or bullet list to reduce redundancy
Consider moving the full conversion example to a separate EXAMPLES.md file and keeping just a minimal example inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy. The 'Right-sized stories' and 'Too big' examples could be more compact, and some explanations (like why stories need to be small) repeat the same concept multiple times. | 2 / 3 |
Actionability | Excellent actionability with complete JSON schema, concrete examples of good/bad criteria, a full input-to-output conversion example, and a clear checklist. Everything is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | Clear sequential workflow: check for existing prd.json → archive if needed → convert PRD → verify with checklist. The checklist at the end provides explicit validation steps, and the archiving section handles state management. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a long monolithic file (~200 lines). The archiving section and detailed examples could potentially be split into separate reference files for a cleaner overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 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 |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- Repository
- snarktank/ralph
- Commit
6c53cb0
- 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.