deep
Skill1 starsChanged 49 days agoMITView on GitHub
Ask Fable one hard, self-contained question. For "deep" or a bug that resisted two attempts.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- agoopintsai/shiprighttheir own version, first seen Nov 1, 2026
- 0kim0bos/yamtheir own version, first seen Oct 29, 2026
- Seth090502/osanwe-publictheir own version, first seen Oct 20, 2026
- oprogramadorreal/optimus-claudetheir own version, first seen Sep 4, 2026
- kbichave/skillstheir own version, first seen Sep 1, 2026
- Olayeeeyo/claude-skillstheir own version, first seen Apr 5, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- oprogramadorreal/optimus-claude★ 75same name
- agoopintsai/shipright★ 2same name
- kbichave/skills★ 2same name
- 0kim0bos/yam★ 1same name
- Olayeeeyo/claude-skills★ 0same name
- Seth090502/osanwe-public★ 0same name
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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
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 15
Read only the files the question needs.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Question:
$ARGUMENTS
The forked agent cannot see the conversation that sent this, so the question above must stand alone: the goal, the files involved, what was tried and what happened.
Read only the files the question needs. Answer in at most 300 words: the verdict first, then the reasoning that decides it, then the one check to run before acting. If the question cannot be answered from what you can read, say what is missing.
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.