ralph-loop
The Ralph Loop pattern for Agent Team teammates. Use when spawning builder teammates that need to iterate until all tests, lint, and type checks pass. Provides the standard retry logic, max attempts, and escalation rules.
What this skill does
# Ralph Loop — Iterate Until Green The Ralph Loop is a persistent retry pattern for AI coding agents. Instead of writing code and hoping it works, the agent implements → tests → fixes → retests in a loop until everything passes. ## The Pattern ``` implement → test → [FAIL?] → read error → fix → test again → [PASS?] → lint → [FAIL?] → fix → lint again → [PASS?] → typecheck → [FAIL?] → fix → typecheck again → [PASS?] → DONE ``` ## Rules 1. **Max 5 retries per unique error.** If the same test fails 5 times with the same root cause, stop and escalate. 2. **Max 3 retries before escalating.** If stuck on the same error after 3 attempts, message the team lead with: - The error message - What you've tried - Your hypothesis about why it's failing 3. **Run checks in order:** tests → lint → typecheck. Don't skip ahead. 4. **Each retry should be different.** Don't repeat the same fix. If approach A failed, try approach B. If both fail, try a fundamentally different strategy. 5. **Read the error message carefully.** Most failures contain the answer. Parse stack traces, find the actual line, understand the assertion. ## Verification Commands Read these from CLAUDE.md "Build Commands" section. Common patterns: | Stack | Tests | Lint | Typecheck | |-------|-------|------|-----------| | Next.js/React | `npm test` or `npx vitest` | `npm run lint` | `npx tsc --noEmit` | | Python | `pytest` | `ruff check .` | `mypy .` | | Node.js | `npm test` | `npx eslint .` | `npx tsc --noEmit` | | Go | `go test ./...` | `golangci-lint run` | (built into compiler) | ## When to Break the Loop Stop looping and escalate when: - Same error persists after 3 different fix attempts - The fix requires changes outside your assigned task scope - You need a dependency or config change that affects other teammates - The test itself appears to be wrong (explain why to the team lead) ## Anti-Patterns - **Don't suppress errors** to make tests pass. Fix the root cause. - **Don't delete failing tests.** Fix the code or fix the test, but don't remove coverage. - **Don't retry without changing anything.** Each attempt must try something different. - **Don't fix unrelated tests.** If a pre-existing test fails, note it and move on — it's not your task.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.