Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, mostly lean help skill: concrete start syntax, exact promise-tag format, and clear use/not-use guidance. The main gaps are duplicated mechanism explanations and slightly vague cancel/output instructions.
Suggestions
Merge the 6-step iteration list and the 'How it works' list under 'Starting a Ralph Loop' into one description of the stop-hook cycle to remove the duplicated explanation (conciseness).
Give an explicit example phrase for cancelling (e.g. "Stop the ralph loop") and state where the <promise> tag should appear in the agent's output (actionability).
Replace the vague Output section with a concrete note on answer structure — e.g. lead with a one-line definition of the Ralph Loop, then address the user's specific question (workflow_clarity).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and the self-referential-loop concept is genuinely non-obvious, so its explanation earns its tokens. One clear redundancy: the stop-hook/feed-same-prompt cycle is described twice (the 6-step iteration list and the 5-step 'How it works' list), which could be merged. Mostly efficient with minor trimmable duplication — anchor 4, not 5. | 4 / 5 |
Actionability | The start command is copy-paste ready with both flags documented, and the completion promise is shown as an exact `<promise>TASK COMPLETE</promise>` tag. Anchor 4 rather than 5 because cancelling is given only as a paraphrased instruction ("Ask the agent to cancel the ralph loop") without an example phrasing, and where to place the promise tag is implied rather than stated. | 4 / 5 |
Workflow Clarity | Both the loop lifecycle (numbered 1–6) and the start procedure (numbered 1–5) are clearly sequenced, and no destructive or batch operations exist to require validation checkpoints. Falls short of anchor 5 because the closing Output section ("Present the above information clearly to the user, tailored to their specific question") is directionally vague about structure or ordering of the answer. | 4 / 5 |
Progressive Disclosure | A well-organized single file with clear section headers and external links inline; no bundle files exist, and none are needed. It exceeds 50 lines, so the simple-skill 5-exception does not apply, and the 'When to Use Ralph' and detailed mechanics sections slightly pad what a leaner overview would carry — good structure with minor organization gaps, anchor 4. | 4 / 5 |
Total | 16 / 20 Passed |