aiming-lab/do-not-retry-without-diagnosis
memory_data/skills/do-not-retry-without-diagnosis/SKILL.md
Common mistake — retrying the same failing command or API call without understanding why it failed. Always diagnose the root cause before retrying anything.
$ install --global
skillsauthnpx skillsauth add aiming-lab/metaclaw do-not-retry-without-diagnosisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 28, 2026, 2:50 PM36.1s1 file scanned
SKILL.md
- name:
- do-not-retry-without-diagnosis
- description:
- Common mistake — retrying the same failing command or API call without understanding why it failed. Always diagnose the root cause before retrying anything.
- category:
- common_mistakes
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.
Related Skills
aiming-lab/visualization-selection
development
VerifiedTrustedCommunity
Use this skill when creating charts, plots, or dashboards. Choose the visualization type that best communicates the data relationship before writing any plotting code.
2,755SKILL.mdUpdated Mar 27, 2026
aiming-lab/verify-before-irreversible-action
testing
VerifiedTrustedCommunity
Use this skill before taking any action that is hard to reverse — deleting files, overwriting data, sending messages, pushing to remote, modifying production systems. Always pause, state what you are about to do, and confirm before executing.
2,755SKILL.mdUpdated Mar 27, 2026
aiming-lab/uncertainty-acknowledgment
research
VerifiedTrustedCommunity
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.
2,755SKILL.mdUpdated Mar 27, 2026
aiming-lab/tool-selection-strategy
tools
VerifiedTrustedCommunity
Use this skill when deciding which tools to call in an agentic workflow. Always choose the minimal, most direct tool for each step and avoid redundant or speculative tool calls.
2,755SKILL.mdUpdated Mar 27, 2026