amoa-remote-agent-coordinator

Use when coordinating remote AI agents via AI Maestro messaging. NOT for human coordination. Trigger with agent delegation or multi-agent requests. Loaded by ai-maestro-orchestrator-agent-main-agent

7 stars

Best use case

amoa-remote-agent-coordinator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when coordinating remote AI agents via AI Maestro messaging. NOT for human coordination. Trigger with agent delegation or multi-agent requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Teams using amoa-remote-agent-coordinator should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/amoa-remote-agent-coordinator/SKILL.md --create-dirs "https://raw.githubusercontent.com/Emasoft/ai-maestro-orchestrator-agent/main/skills/amoa-remote-agent-coordinator/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/amoa-remote-agent-coordinator/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How amoa-remote-agent-coordinator Compares

Feature / Agentamoa-remote-agent-coordinatorStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when coordinating remote AI agents via AI Maestro messaging. NOT for human coordination. Trigger with agent delegation or multi-agent requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Remote Agent Coordinator

## Overview

Delegates tasks to remote AI agents via AI Maestro messaging.

## Prerequisites

AI Maestro (AMP) running, Python 3.9+, registered agents.

## Instructions

1. Verify AI Maestro running and agents registered
2. Prepare task with ACK block, context, scope, criteria
3. Send via AMP, wait for ACK (5 min timeout)
4. Monitor progress every 10-15 min
5. Enforce 4 verification loops before PR approval

Copy this checklist and track your progress:

- [ ] Verify AMP running and agents registered
- [ ] Send task with ACK block and criteria
- [ ] Monitor progress and enforce 4 verification loops
- [ ] Approve or reject PR

## Output

ACK confirmations, progress reports, verification results, PR decisions.

## Examples

**Input:** `Delegate "fix auth bug #42" to libs-auth-agent`
**Output:** Task sent, ACK received, 4 loops done, PR approved.

## Error Handling

See [error-handling-protocol.md](./references/error-handling-protocol.md).
<!-- TOC: Table of Contents | 0 Overview | 1 FAIL-FAST Principle | 2 When Agents Must Stop and Report | 0 Error Reporting Format | 1 Error Report Message Schema | 2 Error Types | 0 Orchestrator Response to Errors | 1 Acknowledging Error Reports | 2 Providing Solutions | 3 Escalation When Needed | 0 Troubleshooting | Problem: Agent Not Reporting Errors | Problem: Agent Reports Same Error Repeatedly | Problem: Unclear Error Type | Problem: False Blocker Reports -->

## Resources

- [agent-registration.md](./references/agent-registration.md)
- [echo-acknowledgment-protocol.md](./references/echo-acknowledgment-protocol.md)
- [verification-loops-protocol.md](./references/verification-loops-protocol.md)
- [progress-monitoring-protocol.md](./references/progress-monitoring-protocol.md)
- [error-handling-protocol.md](./references/error-handling-protocol.md)
- [escalation-procedures.md](./references/escalation-procedures.md)
- [messaging-protocol.md](./references/messaging-protocol.md)
- [task-instruction-format.md](./references/task-instruction-format.md)
- [rule-15-no-implementation.md](./references/rule-15-no-implementation.md)
- [rule-14-immutable-requirements.md](./references/rule-14-immutable-requirements.md)
- [script-output-rules.md](./references/script-output-rules.md)
- [examples-remote-coordination.md](./references/examples-remote-coordination.md)

Related Skills

amoa-verification-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when verifying implementations. Trigger with verification, testing, or evidence requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-two-phase-mode

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-task-distribution

7
from Emasoft/ai-maestro-orchestrator-agent

Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-progress-monitoring

7
from Emasoft/ai-maestro-orchestrator-agent

Use when monitoring agent progress. Trigger with status check or stall detection requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-plan-phase

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running Plan Phase of two-phase mode. Trigger with planning, requirements, or plan approval requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when breaking down tasks for human developers. Trigger with task decomposition requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-loop

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running the orchestrator loop or managing stop hook behavior. Trigger with loop, stop hook, or state file requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-sync

7
from Emasoft/ai-maestro-orchestrator-agent

Use when syncing modules with GitHub Issues or troubleshooting module state. Trigger with sync, issue, or module troubleshooting requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-management

7
from Emasoft/ai-maestro-orchestrator-agent

Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-lifecycle

7
from Emasoft/ai-maestro-orchestrator-agent

Use when adding, modifying, removing, prioritizing, or reassigning modules. Trigger with module CRUD requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-messaging-templates

7
from Emasoft/ai-maestro-orchestrator-agent

Use when sending inter-agent messages. Trigger with task assignment, status report, or escalation needs. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-label-taxonomy

7
from Emasoft/ai-maestro-orchestrator-agent

Use when applying GitHub labels. Trigger with label query or assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent