limitless
Skill2 starsChanged 52 days agoMITView on GitHub
Keep this Mac awake for the whole agent task using the installed Limitless lifecycle hooks.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- braincandy-parallel/tamarindos-workflow-kittheir own version, first seen Sep 18, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- braincandy-parallel/tamarindos-workflow-kit★ 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
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use both power sources and a 20% battery reserve, within stricter user limits.
- Very specific: line 16
Do not change preferences, use sudo, rearm protection or reacquire a stopped hold.
- Very specific: line 17
Use limitless status if uncertain.
≈ “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
Limitless
Installed lifecycle hooks start protection with the task and end it when the task finishes. Keep them active through thinking and tool calls. Wait for delegated work before ending the turn. Never create dummy work to extend a session.
Use both power sources and a 20% battery reserve, within stricter user limits. Each task releases only its own hold; the last finished task ends protection. A manual Keep awake session takes priority: never change or stop it.
Do not change preferences, use sudo, rearm protection or reacquire a stopped hold.
Use limitless status if uncertain. If setup is missing, report it rather than
claiming protection. Never read transcripts to infer activity.
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.