agentleFS
EvanBattenEvanBatten/firstmate-for-windows/.agents/skills/away-quiet-supervision/SKILL.md

away-quiet-supervision

Skill2 starsChanged 34 days agoMITView on GitHub

Load whenever /afk or /quiet is invoked, an away or quiet record exists, or a marked away-supervisor message arrives.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Away and quiet supervision safety

The /afk and /quiet skills own their respective entry procedures and share the daemon machinery; architecture owns the captain-held recheck difference between their postures. These safety facts apply to both:

  • Every current daemon injection uses the away-supervisor kind from bin/fm-operational-input.sh after FM_OPERATIONAL_PREFIX (U+2063 INVISIBLE SEPARATOR followed by FIRSTMATE_OP: ), except that a Claude Code primary, which strips U+2063, receives that owner's record-backed doorbell and it counts as marked only when bin/fm-operational-input.sh open <path> verifies its record; the /afk skill owns legacy bare-marker compatibility.
  • state/.afk-contract is the away posture, written in the same turn as /afk before any other work, because /afk is itself the go: no read-back gates entry or waits for a go; entry announces hold-for-return only, and the away session acts on those words by its own judgment through the guarded scripts under standing authority, holding for the return on doubt. A record carrying quiet mode (bin/fm-afk-contract.sh mode) is quiet mode's instead: the captain is present, it holds nothing for a return, and requested actions proceed under ordinary attended authority.
  • While state/.afk exists, the daemon owns supervision; do not arm a separate watcher. The daemon is never launched on Pi, where the ordinary supervision session continues under the record with main parked: the branch takes every safe actionable wake it can, and only a declined wake (including a broken branch or unsafe scan) or a watcher failure wakes main. Away mode on a non-Pi home with config/supervision-host works the same way with the supervision host as the branch; a wake it hands back arrives through that harness's own wake path and is never the captain's return.
  • A marked message while away or quiet mode is active is internal escalation and does not exit that mode.
  • A message beginning /afk refreshes away mode; a message beginning /quiet refreshes quiet mode.
  • Any other unmarked message means the captain returned in away mode (load /afk, run the return owner, and do not process that message as ordinary work until its durable catch-up gate clears), or, in quiet mode, is simply answered as ordinary work with the flag and daemon left untouched until an explicit /quiet off.
  • Away and quiet mode never expand approval authority for merges, ask-user findings, destructive actions, irreversible actions, or security-sensitive choices.
  • Bias ambiguous input toward exit because a present captain takes precedence.

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.