error-recovery
Skill0 starsChanged 5 days agoMITView on GitHub
Take an item whose mistake was never recovered without help and write a variation of the same task under the id the plan prints, so the learner works with the idea and not with the memory of the sentence, then record the graded attempt in the learning ledger; use it when a mistake was never recovered, and it writes a file, so run it only when asked.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- REPOZY/superpowers-optimizedtheir own version, first seen Nov 8, 2026
- github/squadtheir own version, first seen Nov 8, 2026
- NoobyGains/godmodetheir own version, first seen Nov 1, 2026
- microsoft/fsi-banking-payments-dispute-resolution-acceleratortheir own version, first seen Oct 25, 2026
- microsoft/github-vteam-industry-demostheir own version, first seen Oct 25, 2026
- microsoft/wazatheir own version, first seen Oct 20, 2026
Used with
Projects with it also use squad-commands, architectural-proposals and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkillsquad-commands
Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.
Also in 4 projects that use this
Microsoft AzureSkillarchitectural-proposals
How to write comprehensive architectural proposals that drive alignment before code is written
Also in 3 projects that use this
- +10 more from Azure
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- bojieli/ai-agent-book-projects★ 53ksame name
- bojieli/ai-agent-book★ 53ksame name
- github/gh-aw★ 5.6ksame name
- github/squad★ 3.4ksame name
- microsoft/waza★ 1.5ksame name
- Azure/fleet★ 227same name
- kubefleet-dev/kubefleet★ 165same name
- REPOZY/superpowers-optimized★ 147same name
- NoobyGains/godmode★ 120same name
- marcusgoll/Spec-Flow★ 94same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- adaptive-scaffoldSkill
- calibration-coachSkill
- compression-challengeSkill
- counterfactualSkill
- defuddleSkill
- dependency-checkSkill
- json-canvasSkill
- memory-palaceSkill
- misconception-drillSkill
- mistake-reviewSkill
- new-concept-noteSkill
- new-trackSkill
- no-ai-checkpointSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- pretestSkill
- process-paperSkill
- process-webSkill
- quizSkill
- record-attemptSkill
- recovery-after-inactivitySkill
- retention-auditSkill
- review-queueSkill
- run-checksSkill
- schedule-reviewSkill
- spoken-mockSkill
- teach-the-agentSkill
- transfer-labSkill
- vault-searchSkill
- visual-reconstructionSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run the list of errors and read it.
- Distinctive: line 21
Read the original item and the source note behind it.
- Distinctive: line 23
Write the variation. It keeps the same mechanism and changes the surface: new numbers, a new context, a different wording, a different …
- Distinctive: line 28
If the answer is wrong, or the learner asks to try again, use the hint ladder one step at a time: hint, strong hint, partial example, …
- Distinctive: line 30
Ask for confidence from 1 to 5 before the reveal.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tutor mode: the learner attempts first and without notes. The agent never writes the learner's notes or answers. Hints come one step at a time and only after an attempt: hint, strong hint, partial example, answer. Confidence from 1 to 5 is asked before the reveal. The agent never grades an attempt the learner did not confirm.
- Run the list of errors and read it.
python3 -I 90_System/Scripts/schedule_review.py --errors- Take the first item. Each line gives the objective, the item id, how many attempts it had and
when the last one happened. It also gives the id a variation of the task must carry, for
example
item-a-v2. - Read the original item and the source note behind it. Find the mechanism the item tests: the rule, the contrast, the step that makes the answer right.
- Write the variation. It keeps the same mechanism and changes the surface: new numbers, a new context, a different wording, a different order. The learner must work with the idea and not with the memory of the sentence. Give the variation the id the plan printed.
- Give the variation and wait. Say nothing about the content before the attempt: no excerpt, no summary, no hint.
- If the answer is wrong, or the learner asks to try again, use the hint ladder one step at a time: hint, strong hint, partial example, answer. Never skip a step.
- Ask for confidence from 1 to 5 before the reveal. Then reveal and grade the learner's words against the source.
- Record the attempt only after the learner confirms the result. Use the id of the variation, not the id of the original item.
python3 -I 90_System/Scripts/record_attempt.py --objective <id> --item <id> --mode <mode> \
[--correct|--incorrect] [--at <iso>] --confidence <1-5> [--probability <0-1>] [--hints <n>] \
[--assistance <level>] [--grading <method>] [--rubric <ver>] [--revision <rev>] [--minutes <n>]- A mistake is closed only after a correct recall later, without help. A right answer right
after the hint ladder does not close it. When the learner gets it right later without help,
mark the entry
closed YYYY-MM-DDin50_Review/Mistakes.md. - Show the learner the line that was written. Never edit or delete a line of the ledger.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

