agentleFS
Sign inStart free
soophoosoophoo/skills/recover/SKILL.md

recover

Skill0 starsChanged 44 days agoNo licenceView on GitHub

Diagnose why a long session has gone off the rails and apply the right correction. Stops the attempts, lists what was tried, re-establishes ground truth (including whether context/ itself is lying), gets a second opinion from a fresh subagent, and triages between four causes — polluted context, a wrong assumption, a real hidden bug, or a plan that can't work — each with its own cure. Saves the dead ends so the next session doesn't retry them, and fixes the source of a false premise. Use when attempts keep failing and you can't tell why, when `build` stops after repeated failures, or when the user says "we're spiraling", "this isn't working and I don't know why", "recover", "reset", "we're stuck", "on tourne en rond", "je comprends plus rien" — or on your own initiative when a third sound fix for the same problem has failed.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use status.

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.
  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 9 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free