report

Send concise status updates from agents to a central coordinator via tmux.

5|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/humblemuzzu/ghosttyyy --skill report-humblemuzzu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report
Source: https://github.com/humblemuzzu/ghosttyyy/tree/main/pi-setup/config-skills/report
Command: npx skills add https://github.com/humblemuzzu/ghosttyyy --skill report-humblemuzzu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated agents often need to report progress, blockers, or completion back to the appointed coordinator without spamming or miscommunication.

Core Features & Use Cases

  • Concise progress reporting to a central coordinator from spawned agents.
  • Blocker and scope-change notifications to trigger guidance or re-clarification.
  • Structured etiquette ensuring messages are targeted to the coordinator and clearly labeled with agent identity.

Quick Start

Send a concise status update to the coordinator when a task completes, is blocked, or requires guidance using the provided messaging command.

Frequently Asked Questions about report

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

FAQPage Schema
How do I report progress from spawned agents to a central coordinator?

To report progress from spawned agents, use the messaging format AGENT <your-name>: <message> to deliver concise status updates directly to the coordinator pane in a tmux environment.

What is the correct message format for agent-to-coordinator communication in tmux?

The correct message format for agent-to-coordinator communication is AGENT <your-name>: <message>. This structured etiquette ensures messages are targeted to the coordinator and clearly labeled with agent identity.

Do I need tmux to coordinate spawned agents and send status updates?

Yes, you need tmux to coordinate spawned agents and send status updates. The Skill requires a tmux environment with a designated coordinator pane to receive the structured progress messages.

When should spawned agents notify the coordinator during workflow execution?

Spawned agents should notify the coordinator during workflow execution when a task completes, is blocked by a dependency, or requires guidance due to scope changes. This triggers re-clarification or further instructions.

How can I avoid spamming the coordinator with agent progress messages?

To avoid spamming the coordinator with agent progress messages, send concise status updates only when tasks complete, hit blockers, or undergo scope changes, using the structured AGENT <your-name>: <message> format.

Can I use this reporting skill to handle blocker and scope-change notifications?

Yes, you can use this reporting skill to handle blocker and scope-change notifications. It explicitly supports sending targeted updates to trigger guidance or re-clarification from the appointed coordinator.