ralph

MCP-owned Ralph loop around background evolve_step jobs

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ralph/SKILL.md

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, highly actionable workflow with strong validation checkpoints and feedback loops for a destructive batch loop. It is slightly verbose in places and could trim restated guidance, but overall provides clear, executable direction.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and information-dense, but several passages restate the same dispatch/observer guidance across sections and could be tightened without losing clarity.	3 / 5
Actionability	Concrete MCP tool calls with exact arguments, host-specific spawn commands, and copy-ready report templates give mostly executable guidance, with only minor gaps around runtime-specific tool-name resolution.	4 / 5
Workflow Clarity	Steps are clearly sequenced with explicit validation checkpoints ('fail closed unless the bounded payload passes canonical v1 validation'), error-recovery fallbacks, and feedback loops for this batch/destructive loop.	5 / 5
Progressive Disclosure	A single well-organized self-contained file with clear section headers and no nested references; with no bundle files present the structure is good but a few dense inline sections could be split out.	4 / 5
	Total	16 / 20 Passed

Description

46%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description conveys a clear, distinctive 'what' but lacks any explicit 'when to use' trigger guidance and relies heavily on technical jargon, weakening trigger-term quality and completeness. Adding a 'Use when...' clause with natural-language triggers would lift the capped dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user says ralph, don't stop, or keep going until the evolution converges'.

Soften the jargon by including natural-language synonyms ('evolution loop', 'keep iterating') alongside 'evolve_step' so users' phrasing matches the description.

List one or two more concrete actions (e.g. 'starts background jobs, monitors progress, and stops on QA pass or convergence') to broaden specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Ralph loop around background evolve_step jobs') and a couple of concrete actions (looping, background jobs), but coverage is not comprehensive and no further actions are enumerated.	3 / 5
Completeness	It clearly answers 'what' the skill does but provides no 'Use when...' or equivalent trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	'Ralph' is a natural trigger term, but the description leans on technical jargon ('MCP-owned', 'evolve_step jobs') and omits the common natural phrases users would say, missing synonyms and variations.	2 / 5
Distinctiveness Conflict Risk	'MCP-owned Ralph loop around background evolve_step jobs' carves a distinct niche with minimal overlap risk; only minor overlap with closely related Ouroboros skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Q00/ouroboros
Path: skills/ralph/SKILL.md
Commit: 80333ae

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.