away
Skill1 starsChanged 2 months agoMITView on GitHub
Away mode. Keeps the prompt cache warm by pinging the session periodically via in-session cron. Use only when the user explicitly types /away. Never invoke on your own.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- leodiegoo/orqtheir own version, first seen Oct 3, 2026
- chadthornton/claude-continuitytheir own version, first seen Sep 30, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- leodiegoo/orq★ 2same name
- chadthornton/claude-continuity★ 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
4 rules. About 0 are common, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Follow the output above.
- Very specific: line 18
If the output contains AWAY_PING_CRON= and AWAY_EXPIRY_CRON= lines (away mode starts):
- Very specific: line 24
If the output contains an AWAY_DISARM line (disarm):
- Very specific: line 25
Run CronList and CronDelete every job whose prompt is [away ping] or [away expired]
≈ “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
!bash "${CLAUDE_SKILL_DIR}/arm.sh" "$ARGUMENTS"
Follow the output above.
If the output contains AWAY_PING_CRON= and AWAY_EXPIRY_CRON= lines (away mode starts):
- Call
CronCreatetwice- cron: the
AWAY_PING_CRONvalue, prompt:[away ping], recurring: true - cron: the
AWAY_EXPIRY_CRONvalue, prompt:[away expired], recurring: false
- cron: the
- Relay the first line of the output ("Away mode: …") to the user verbatim and stop. Say nothing else.
If the output contains an AWAY_DISARM line (disarm):
- Run
CronListandCronDeleteevery job whose prompt is[away ping]or[away expired] - Relay the first line of the output to the user verbatim and stop
Rules from then on:
- Turn whose prompt is
[away ping]: reply with exactly "ack". No reasoning, no tools - Turn whose prompt is
[away expired]: runCronListandCronDeleteevery job whose prompt is[away ping]or[away expired](a fired one-shot job still appears in the list, so delete this job itself too), then reply with exactly "Away mode ended" - Turn where the hook says
[away] The user is back…: follow it, delete the[away ping]/[away expired]jobs withCronListandCronDelete, then handle the user's input as usual. Do not mention away mode
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.

