Common mistake — retrying the same failing command or API call without understanding why it failed. Always diagnose the root cause before retrying anything.
| Publisher | aiming-lab |
| Repository | MetaClaw |
| Skill name | do-not-retry-without-diagnosis |
| Stars | 3.5K |
| Forks | 454 |
| Bundled files | Instructions only |
| License | MIT |
| Links |
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Everything the model needs lives in the instructions — no extra files to sync.
Published by aiming-lab on GitHub. Read the source before you install it.
Install the Do Not Retry Without Diagnosis AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.
TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.
Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.
git clone --depth 1 https://github.com/aiming-lab/MetaClaw.git /tmp/MetaClaw
mkdir -p .claude/skills
cp -r /tmp/MetaClaw/memory_data/skills/do-not-retry-without-diagnosis .claude/skills/do-not-retry-without-diagnosisEnable Do Not Retry Without Diagnosis in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.
AI skills are plain Markdown instructions rather than provider-specific code, so Do Not Retry Without Diagnosis is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.
This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.
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:
Anti-pattern: Blindly retrying or escalating without examining the error output.
Common mistake — retrying the same failing command or API call without understanding why it failed. Always diagnose the root cause before retrying anything.
Because you install it once and use it with any model. Do Not Retry Without Diagnosis is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.
Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/aiming-lab/MetaClaw/tree/main/memory_data/skills/do-not-retry-without-diagnosis. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.
Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.
As many as you like. As long as a model supports skills, you can use Do Not Retry Without Diagnosis with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.
Yes. It is published on GitHub by aiming-lab under the MIT license. You only pay your own AI provider for the tokens you use.
An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.
A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.
Writing Plans
Use when you have a spec or requirements for a multi-step task, before touching code
Writing Skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Api Design
Patrones de diseño REST API incluyendo nomenclatura de recursos, códigos de estado, paginación, filtrado, respuestas de error, versionado y rate limiting para APIs de producción.
Backend Patterns
Patrones de arquitectura backend, diseño de API, optimización de base de datos y buenas prácticas del lado del servidor para Node.js, Express y rutas API de Next.js.
Get notified about new features and future giveaways by subscribing to our newsletter 👇
