Menú
Background Agent Pings
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Maestro spec-driven development for Claude Code. Load this skill when invoking Maestro commands so workflows stay aligned with LeIndex and the Rust TUI.
Maestro spec-driven development for Gemini CLI. Load this skill when invoking Maestro commands so workflows stay aligned with LeIndex and the Rust TUI.
Maestro spec-driven development for Amp CLI. Load this skill when invoking Maestro commands so workflows stay aligned with LeIndex and the Rust TUI.
Show users how Maestro works - the opinionated setup with hooks, memory, and coordination
Full 5-layer analysis of a specific function for debugging or deep understanding
Get a token-efficient overview of any project using the TLDR stack
| name | background-agent-pings |
| description | Background Agent Pings |
| user-invocable | false |
Trust system reminders as agent progress notifications. Don't poll.
When you launch a background agent, continue working on other tasks. The system will notify you via reminders when:
Agent <id> progress: X new tools used, Y new tokens1. Task(run_in_background=true, prompt="... Output to: .maestro/cache/agents/<type>/output.md")
2. Continue with next task immediately
3. When system reminder shows agent activity, check if output file exists
4. Read output file only when agent signals completion
# BAD: Polling wastes tokens and time
Task(run_in_background=true)
Bash("sleep 5 && ls ...") # polling
Bash("tail /tmp/claude/.../tasks/<id>.output") # polling
TaskOutput(task_id="...") # floods context
TaskOutput floods main context with full agent transcript