ralph-medium
- Repo stars 1
- Author updated Live
- Author repo Ralph-Anti-loop-Bundle-Skill
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 92 / 100 · audit passed
- Author / version / license
- @00Blacksheep00 · v1.0 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Linux
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: ralph-medium
description: > | Use ralph-small | Use ralph-medium (this) | Use ralph-huge | |---------------------|--------…
category: other
runtime: no special runtime
---
# ralph-medium output preview
## PART A: Task fit
- Use case: > | Use ralph-small | Use ralph-medium (this) | Use ralph-huge | |---------------------|----------------------------|-------------------| | 1-3 steps, quick ops | 4-10 steps, moderate deps | 10+ steps, complex deps | | Single command/edit | Multi-file edits, configs | Refactors, debugging, architecture | | Lookup, simple Q&A | Sequential workflows | Alrea….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Skill Routing / 6 Rules / 1. No claim without proof” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “> | Use ralph-small | Use ralph-medium (this) | Use ralph-huge | |---------------------|----------------------------|-------------------| | 1-3 steps, quick ops | 4-10 steps, moderate deps | 10+ steps, complex deps | | Single command/edit | Multi-file edits, configs | Refactors, debugging, architecture | | Lookup, simple Q&A | Sequential workflows | Alrea…”.
- **02** When the source has headings, the agent prioritizes “Skill Routing / 6 Rules / 1. No claim without proof” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/home`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Skill Routing / 6 Rules / 1. No claim without proof”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: ralph-medium
description: > | Use ralph-small | Use ralph-medium (this) | Use ralph-huge | |---------------------|--------…
category: other
source: 00Blacksheep00/Ralph-Anti-loop-Bundle-Skill
---
# ralph-medium
## When to use
- > | Use ralph-small | Use ralph-medium (this) | Use ralph-huge | |---------------------|----------------------------|-…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Skill Routing / 6 Rules / 1. No claim without proof” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "ralph-medium" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Skill Routing / 6 Rules / 1. No claim without proof
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Ralph Medium — Mid-Weight Anti-Loop
Do it, prove it, track it. If stuck, pivot — don't repeat.
Skill Routing
| Use ralph-small | Use ralph-medium (this) | Use ralph-huge |
|---|---|---|
| 1-3 steps, quick ops | 4-10 steps, moderate deps | 10+ steps, complex deps |
| Single command/edit | Multi-file edits, configs | Refactors, debugging, architecture |
| Lookup, simple Q&A | Sequential workflows | Already failed 3 times here |
Auto-escalation: 3 failed unique attempts on the same sub-task → switch to ralph-huge (/home/ubuntu/.openclaw/skills/ralph-huge/SKILL.md) for full Circuit Breaker + 8-level Pivot Ladder.
6 Rules
1. No claim without proof
Don't say "done" / "sent" / "fixed" unless tool output proving it is in THIS turn.
CLAIM: [What you say you did]
ACTION: [Tool that did it]
PROOF: [Output line confirming success]Can't fill all three? → You're not done.
2. No orphan promises
"I'll do X" / "Let me run Y" → tool call for X/Y MUST exist in same turn. Can't execute? → "I can't [X] because [blocker]. I need [thing]."
3. Track attempts, force diversity
Log every failed attempt. Next try MUST change at least one of:
- Tool (grep → semanticsearch)
- Params (different path, ID, scope)
- Strategy (edit → rewrite, read → create)
- Source (config A → config B)
#1 [method] → [error]
#2 [different method] → [error]
#3 [different method] → [error] → ESCALATE to ralph-hugeSame method twice = Ralph loop violation. Change or escalate.
4. Progress updates
Before starting (if 4+ steps expected):
▶ Starting: [task] — ~[N] stepsEvery 3-4 steps:
⏳ [X/Y] done — current: [what's happening]On completion:
✅ Done: [summary] — Evidence: [proof]If blocked:
⚠️ Blocked: [issue] — Need: [specific thing]The user should never have to ask "what's happening?"
5. Act first, ask only if stuck
Have enough info (even partial)? → Do it, then confirm assumptions. Missing ONE critical piece? → Ask exactly 1 question. Never ask 2+ questions when you could act on the first one.
6. Three-attempt diagnostic
After 3 unique failed attempts on the same sub-task, STOP:
⛔ 3 attempts exhausted
#1 [Method] → [Error]
#2 [Method] → [Error]
#3 [Method] → [Error]
Likely cause: [1-2 sentences]
Options:
→ [A: what you need from user]
→ [B: alternative approach]
→ [C: skip and continue]Then WAIT for user input. Do not attempt #4 without new info.
Quick Pivot Menu
When a method fails, pick next from:
- Different params — same tool, change path/query/ID/scope
- Different tool — grep → glob → semanticsearch
- Different strategy — modify → rewrite → template
- Ask user — 1 specific question, last resort
Between pivots: "Method A failed: [reason]. Trying B: [1-line description]." Then execute B immediately.
Top 5 Anti-Patterns
| Pattern | Symptom | Fix |
|---|---|---|
| Ghost Completion | "Done ✅" but nothing happened | No tool output = not done |
| Groundhog Day | Same error, same approach, 3 turns | Same error twice → forced pivot |
| Promise Spiral | "I'll do X" → next turn, no X | Promise = tool call in same turn |
| Silent Struggle | Working for ages, zero updates | Update every 3-4 steps |
| Interrogation | 4 questions, 0 actions | Act on what you have, ask max 1 |
Closure: self-improvement
After you verify success on a non-trivial task (evidence in this turn): if you learned something worth replaying (pattern, failure mode, fix, gateway/tool quirk), open self-improvement and append to this workspace’s .learnings/ (LEARNINGS.md / ERRORS.md) using its format — or promote to TOOLS.md / AGENTS.md when it’s recurring. Consider skill extraction only when self-improvement criteria apply or the user asks. Skip if nothing material. Never log secrets or full raw output. Do not delay the user-facing answer for long write-ups; a short inline log in the same turn is enough when lightweight.
Skill: /home/ubuntu/.openclaw/skills/self-improvement/SKILL.md — template for new skills: .learnings/SKILL-TEMPLATE.md in the workspace.
Config
Tool-level loop detection: tools.loopDetection in /home/ubuntu/.openclaw/openclaw.json
Docs: /home/ubuntu/.npm-global/lib/node_modules/openclaw/docs/tools/loop-detection.md
Decide Fit First
Design Intent
How To Use It
Boundaries And Review