# Quiet

Enter quiet supervision mode when the captain invokes /quiet or asks for quiet mode...

- Repository: https://github.com/kunchenguid/firstmate (8480 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kunchenguid/firstmate --skill quiet -g -a claude-code -y`
Codex: `npx skills add kunchenguid/firstmate --skill quiet -g -a codex -y`
Cursor: `npx skills add kunchenguid/firstmate --skill quiet -g -a cursor -y`
Gemini CLI: `npx skills add kunchenguid/firstmate --skill quiet -g -a gemini-cli -y`

## Description

Enter quiet supervision mode when the captain invokes /quiet or asks for quiet mode, quiet-while-present, or fewer routine wake turns while they stay in the session. Unlike /afk, ordinary captain chat does not exit it; only an explicit `/quiet off` does.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# quiet

Quiet supervision mode (kunchenguid/firstmate#2356): the same token-saving
daemon tradeoff as `/afk`, made explicit for a captain who is staying,
watching the session, and does not want to exit the mode just by chatting.

Where a daemon runs, this skill is a thin wrapper.
The `afk` skill owns the daemon's injection, busy/composer guards, and reliability properties; quiet mode uses that machinery while the captain remains present.
For captain-held rechecks under quiet, see [architecture](../../../docs/architecture.md).

## What it does

0. **First check whether quiet mode needs anything here.**
   On Pi or pi-signed, enter nothing: the attended branch already keeps routine wakes out of this conversation (the `afk` skill's step 2); tell the captain so.
   Everywhere else run `bin/fm-afk-launch.sh quiet-check`; its header's QUIET MODE owns what each result means.
   - Exit 0: enter nothing - no record, no flag, no daemon, and `/quiet off` then needs nothing either.
     Tell the captain in `AGENTS.md` section 9 language that supervision here already works that way: routine fleet events stay off this conversation, while decisions, failures, credentials, and review-ready work still reach them.
     When its line says the supervision session is paused, say instead that routine updates reach them until it recovers, and when it next retries.
   - Exit 2: an away record is live, so the captain has returned: run the `afk` skill's return and clear its catch-up gate, then run `quiet-check` again and follow its new result.
   - Exit 1: go on to step 1; if it printed a line, first tell the captain plainly what keeps supervision from already being quiet here.

The rest: https://github.com/kunchenguid/firstmate/blob/HEAD/.agents/skills/quiet/SKILL.md