reduce-context-switch-for-human

Routes delegated agent progress through manager roll-ups and queues user notifications.

1|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill reduce-context-switch-for-human-zhiyuan-zhang0206
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reduce-context-switch-for-human
Source: https://github.com/zhiyuan-zhang0206/Ava/tree/main/ava_builtins/plugins/ava_fleet/skills/reduce-context-switch-for-human
Command: npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill reduce-context-switch-for-human-zhiyuan-zhang0206

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In multi-agent delegation trees, every progress update pushed to the human costs a context switch. This Skill defines an interrupt discipline so agents default to queueing updates via ava.ui.notify, roll progress up through managers, and reserve out-of-band pushes for true emergencies. ## Core Features & Use Cases - Queue-first notification discipline: Deliveries go to the ava.ui.notify queue, which the user drains on their own schedule; delivering to the queue counts as completion with no escalation for missing acknowledgments. - Milestone-based roll-up: Each manager maintains one rolling notice that supersedes its predecessor, updated only on real milestones, blockers, completion, or genuine need. - Roll-up bisection: Authorization and decision requests go directly to the user from any depth, while progress and conclusions flow to the parent task's manager for aggregation. - Use Case: A fleet of delegated agents completes subtasks overnight; instead of dozens of pings, the user finds one aggregated notice per manager in the queue, with a push only if an irreversible risk emerges. ## Quick Start Apply this interrupt discipline so delegated agents queue milestone updates through their managers and only push me for genuine emergencies.

Frequently Asked Questions about reduce-context-switch-for-human

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

FAQPage Schema
How do I reduce interruptions from delegated AI agents?▼

Default all agent output to a queue such as ava.ui.notify that the user drains on their own schedule. Progress rolls up to each delegation's manager, which posts a single aggregated notice instead of every agent messaging the user directly.

When should an agent push a notification instead of queueing it?▼

Push only for true emergencies: irreversible risk in motion, the entire effort blocked on the user, or the user explicitly asked to be woken. Everything else, including routine progress and acknowledgments, stays in the queue.

How often should delegated agents report progress to the user?▼

Updates are milestone-based by default: roll up on a real milestone, blocker, completion, or genuine need, never routine progress. A delegator wanting a different cadence must state it explicitly in the delegation brief.

What happens when the user replies directly to an agent?▼

A direct reply counts as the user responding. The agent judges whether the exchange resolves its open notice; if resolved it withdraws or supersedes the notice, otherwise it keeps or re-posts it. The framework never clears notices automatically.

Do authorization requests also go through the manager roll-up?▼

No. Authorization and decision requests that only the user can answer go directly to the user from any depth in the delegation tree. Only progress and conclusions roll up through managers for aggregation.