Apollo 13
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.
Install
$ agentstack add skill-jakeschincariol-unhinged-claude-skills-apollo-13 ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jakeschincariol-unhinged-claude-skills-apollo-13) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jakeschincariol
- Source: Jakeschincariol/unhinged-claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.