agentleFS
Sign inStart free
toveruxtoverux/cantrips/skills/afk/SKILL.md

afk

Skill3 starsChanged 4 months agoMITView on GitHub

Keep the session's prompt cache warm while you step away.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use fmx-respond, harness-adapters and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • karanmrnSkill

    fmx-respond

    Agent-only playbook for handling an X mention in X mode. Use on an "x-mention <request_id>" check: wake - read the stashed mention (with any in_reply_to conversation context); the direct author is the firstmate's own owner (captain) under owner-only routing, so classify it as an actionable request to act on through the normal lifecycle, a question to answer from live fleet state, or a pure acknowledgment to dismiss without replying; act autonomously (escalating only destructive/irreversible/security-sensitive work). For a request that spawns real work, acknowledge first, act, link the task with bin/fm-x-link.sh, and let the completion follow-up post on the done wake; for a question or completed action, post or preview a short public-safe reply with bin/fm-x-reply.sh; for a pure acknowledgment, call bin/fm-x-dismiss.sh. Clear the inbox file only after a successful reply or dismiss. Loaded only when X mode is enabled.

    Also in 3 projects that use this

  • karanmrnSkill

    harness-adapters

    Agent-only reference for firstmate harness operations. Use before spawning or recovering a crewmate or secondmate, handling a trust dialog, sending a harness-specific skill invocation, interrupting or exiting an agent, resuming an exited agent, or verifying a new harness adapter. Contains verified facts for claude, codex, opencode, and pi.

    Also in 3 projects that use this

  • +3 more from karanmrn

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Claude Code only: If you do not have a ScheduleWakeup tool, say so and stop — a shell sleep or an external scheduler runs outside this …

    line 8
  2. Very specific:

    Keep this session warm across a break.

    line 10
  3. Very specific:

    Stop the loop when the user returns, or when you reach ten pings (failure mode).

    line 19
  4. Very specific:

    Call ScheduleWakeup with stop: true so a pending wakeup cannot fire once the loop has ended.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 18 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Claude Code only. If you do not have a ScheduleWakeup tool, say so and stop — a shell sleep or an external scheduler runs outside this session and warms nothing.

Keep this session warm across a break. Schedule the next wakeup with ScheduleWakeup:

  • prompt — /afk verbatim, so the wakeup re-enters this skill and chains the next one.
  • delaySeconds — 3000.
  • reason — name cache warming, so the user reads why the session woke.

On each wake, reply with just "ping X" (number them), schedule the next wakeup, and leave the user's work untouched.

Stop the loop when the user returns, or when you reach ten pings (failure mode). Call ScheduleWakeup with stop: true so a pending wakeup cannot fire once the loop has ended.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free