do-not-retry-without-diagnosis
Do Not Retry Without Diagnosis
Mistake pattern: Tool call fails → retry the same call → fails again → repeat.
Fix: After the first failure, read the error message carefully and diagnose the root cause before retrying.
Questions to ask:
- Is this a transient error (network timeout, rate limit)? Retry with backoff.
- Is this a permanent error (wrong input, missing resource, permission denied)? Fix the cause.
Anti-pattern: Blindly retrying or escalating without examining the error output.
More from aiming-lab/metaclaw
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.
13codebase-navigation
Use this skill when exploring an unfamiliar codebase, tracing code paths, or answering questions about how the system works. Read before writing, and build a mental model of the architecture before making changes.
12graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
11uncertainty-acknowledgment
Use this skill when you are not sure about a fact, have outdated knowledge, or the question is contested. Explicitly communicate the level of confidence instead of asserting uncertain things as fact.
11plan-before-multi-step-execution
Use this skill before executing a sequence of 3 or more steps, especially when steps are irreversible or depend on each other. Write out the plan and verify it before starting execution.
9task-decomposition
Use this skill when a user presents a large, vague goal. Break it into concrete, ordered sub-tasks before starting any work. Apply whenever the request is larger than a single focused action.
9