setup-coordinator

Configure coordinator access and verify capability detection across CLI MCP and HTTP transports.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill setup-coordinator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-coordinator
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/setup-coordinator
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill setup-coordinator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill configures and verifies coordinator access for both local CLI MCP runtimes and cloud HTTP runtimes so multi-agent coordination works reliably and safely across environments. It centralizes profile loading, secret checks, runtime health validation, and capability detection so integrated skills can depend on consistent coordination behavior.

Core Features & Use Cases

  • Profile-driven configuration: Load local or railway profiles, apply env secrets, and auto-start local ParadeDB when needed.
  • Transport verification: Register and validate MCP servers for CLI agents and configure HTTP access for cloud or cross-environment coordination.
  • Lifecycle & capabilities: Install lifecycle hooks, allow-list coordination tools, verify tool discovery and capability flags, and report diagnostics with graceful fallback.
  • Use case: Prepare a developer workstation and cloud deployment so Claude, Codex, and Gemini agents share locks, queues, handoffs, and memory consistently.

Quick Start

Run the setup-coordinator skill with the desired profile (for example "local") to configure transports, register agents, verify health, and produce a capability summary.

Frequently Asked Questions about setup-coordinator

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

FAQPage Schema
How do I configure MCP server registration for multi-agent coordination?

To configure MCP server registration, you load a local or cloud profile, apply environment secrets, and register MCP servers for CLI agents. This validates coordinator tool discovery and ensures multi-agent coordination works consistently.

How do I verify coordinator capability detection across HTTP and CLI transports?

Verifying coordinator capability detection involves registering MCP servers for CLI runtimes and configuring HTTP access for cloud environments. The process validates tool discovery, checks capability flags, and reports diagnostics with graceful fallback to standalone mode.

Can I use lifecycle hooks to coordinate Claude and Gemini agents across local and cloud environments?

Yes, you can install lifecycle hooks and allow-list coordination tools so Claude, Codex, and Gemini agents share locks, queues, and memory. This works across local development and cloud deployments for consistent cross-environment coordination.

What is the best way to validate HTTP API credentials and Docker health for coordinator access?

The best way to validate HTTP API credentials and Docker health is through profile-driven configuration that applies secret checks and auto-starts local ParadeDB. This performs API health verification and satisfies profile loading requirements.

Why does multi-agent coordination fail when MCP tool discovery returns inconsistent capability flags?

Multi-agent coordination fails when capability flags are inconsistent because integrated skills depend on stable coordination behavior. Centralizing profile loading, secret checks, and runtime health validation ensures agents share locks and handoffs reliably.

Do I need standalone mode fallback when coordinator access verification fails in cloud deployments?

Yes, standalone mode fallback is necessary when coordinator access verification fails. The setup reports diagnostics and gracefully falls back to standalone mode, ensuring your environment remains operational even if cloud HTTP transport validation encounters issues.