heads-up

Absorb atmux supervisor heads-up notifications without command parsing errors.

2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/geoyws/atmux --skill heads-up
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: heads-up
Source: https://github.com/geoyws/atmux/tree/main/plugins/atmux/skills/heads-up
Command: npx skills add https://github.com/geoyws/atmux --skill heads-up

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents noisy “Unknown command” errors when the atmux supervisor injects between-turn notifications into a teammate pane.

Core Features & Use Cases

  • Silent acknowledgement: The skill absorbs /atmux:heads-up <message> so the receiving agent can continue cleanly without producing any output or verdict markers.
  • Inbox- and kanban-consistent handling: It instructs receivers to re-check the source-of-truth state (kanban/inboxes/state.db) based on the event args, ensuring missed injections do not desync the workflow.
  • Safe timing semantics: Receivers are told not to interrupt in-flight work; they should fold the nudge into the next idle turn and only then reconcile task/inbox state.

Quick Start

When your pane receives a /atmux:heads-up nudge during an idle boundary, read the event arguments and re-query the relevant inbox or task list on your next idle turn.

Frequently Asked Questions about heads-up

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop tmux agent panes from generating unknown command errors on supervisor notifications?▼

To stop tmux agent panes from generating unknown command errors, use a skill that silently absorbs supervisor heads-up notifications, preventing noisy parsing failures while keeping teammate panes quiet.

How do workflow coordination agents handle between-turn injections without interrupting in-flight work?▼

Workflow coordination agents handle between-turn injections by acknowledging nudges without output and folding the state reconciliation into the next idle turn, ensuring no interruption of in-flight work.

What is the best way to keep kanban and inbox states synced after receiving an atmux task dispatch?▼

The best way to keep kanban and inbox states synced after an atmux task dispatch is to re-query the source-of-truth state using inbox and task list verbs on the receiver's next idle turn.

Does silent notification handling for agent orchestration require any specific dependencies?▼

Silent notification handling for agent orchestration requires no external dependencies, operating with basic implementation depth to parse arguments and reconcile state via native atmux verbs.

When should I not use silent acknowledgement for tmux workflow coordination?▼

You should not use silent acknowledgement for tmux workflow coordination when immediate state reconciliation is required, as receivers are instructed to defer processing until their next idle boundary.