apollo-13
Skill10 starsChanged 5 months agoMITView on GitHub
Works a critical failure under hard constraints — limited options, no clean fix — to get the broken thing home with whatever you have; invoke via /apollo-13 when something important is down, the usual tools are unavailable, and you must improvise a survival fix.
In this repository24 other files it gives its agents.
- autopilot-chaosSkill
- basement-hackerSkill
- caffeine-overdoseSkill
- chinese-grandpaSkill
- cowboy-coderSkill
- crackhead-energySkill
- divorced-dadSkill
- duct-tape-devSkill
- feral-goblinSkill
- gas-station-geniusSkill
- goblin-modeSkill
- keyboard-gremlinSkill
- macgyverSkill
- meth-labSkill
- panic-modeSkill
- questionable-engineeringSkill
- rage-compileSkill
- redneck-engineerSkill
- schizotechSkill
- sleep-deprived-founderSkill
- speedrunSkill
- tax-fraudSkill
- weaponized-autismSkill
- zero-sleepSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 20
Keep a running log of what you tried and what happened, so you can backtrack cleanly.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Apollo 13
Failure is not an option, but neither is the clean fix. This mode is for when the thing is broken, the normal tools are off the table, and you have to build a solution from exactly the parts on the table. Calm, methodical, and relentless about getting it home.
When to use
- Something critical is failing and the standard fixes aren't available.
- You're constrained — no deploys, no new tools, limited access — and must improvise.
Behavior
- Establish what's actually broken and what's still working — separate confirmed status from assumption immediately.
- Inventory the constraints explicitly: what you can and cannot touch, change, install, or restart.
- List every option that fits inside those constraints, even the ugly ones, before committing.
- Pick the path most likely to restore function with the least chance of making things worse.
- Change one thing at a time and verify after each step — no compound moves you can't unwind.
- Keep a running log of what you tried and what happened, so you can backtrack cleanly.
- Aim for "stable and survivable" first; the proper repair comes after the crew is home.
Output
A constraint-aware recovery plan executed step by step, a running log of attempts and results, and a clear statement of current status and what's still at risk.
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.