skills.rest
tinkermonkey
tinkermonkeyCOMMUNITY
Explore all skills by this author →
GitHub

orchestrator-ref

Reference Elasticsearch indices, event types, Docker patterns, and pipeline flows for the Claude Code Agent Orchestrator.

Updated Sep 22, 2025
Search Tags:#reference#observability#docker#events#pipelines#orchestrator#elasticsearch
One-click install
npx skills add https://github.com/tinkermonkey/switchyard --skill orchestrator-ref
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrator-ref
Source: https://github.com/tinkermonkey/switchyard/tree/main/.claude/skills/orchestrator-ref
Command: npx skills add https://github.com/tinkermonkey/switchyard --skill orchestrator-ref

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides quick, structured reference data for the Claude Code Agent Orchestrator, enabling faster onboarding, debugging, and design discussions.

Core Features & Use Cases

  • Comprehensive reference for indices, event taxonomy, and deployment patterns.
  • Useful for onboarding engineers and debugging workflow issues.
  • Example: quickly fetch index and event definitions when diagnosing a pipeline run.

Quick Start

Refer to this guide to quickly locate index patterns, event types, and docker patterns when configuring or debugging the orchestrator.

Frequently Asked Questions about orchestrator-ref

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

FAQPage Schema
What Elasticsearch indices and event types does the Claude Code Agent Orchestrator use?▼

The orchestrator uses specific Elasticsearch indices and a defined event taxonomy to track pipeline runs. Referencing these event types and index patterns is essential for diagnosing workflow issues and understanding task orchestration behavior.

How do I find Docker usage patterns for deploying the Claude Code Agent Orchestrator?▼

You can find common Docker usage patterns by consulting reference guides that detail the orchestrator's deployment configurations. This helps ensure correct container setup and smooth integration during architecture and deployment discussions.

How can I quickly reference orchestrator pipeline flows during troubleshooting?▼

To troubleshoot orchestrator pipeline flows, use a structured reference that maps out indices, event taxonomies, and common queries. This enables faster onboarding and debugging by providing quick access to internal workflow data.

Can I use this orchestrator reference for observability and task debugging?▼

Yes, this reference is designed for observability and debugging task orchestration. It provides structured data on Elasticsearch indices and events, making it easier to diagnose pipeline runs and resolve workflow issues.

Does this orchestrator reference require any dependencies to use?▼

No, this orchestrator reference does not require any external dependencies. It serves as a standalone knowledge base for quickly fetching index patterns, event definitions, and Docker configurations during integration.

Related Skills

Explore More Software Engineering Skills→
tinkermonkeytinkermonkey

pipeline-investigate

Aggregate timelines, Docker logs, and decision events to diagnose pipeline run failures.

Community
Advanced
tinkermonkeytinkermonkey

claude-live-logs

Analyze Claude Code execution logs in Elasticsearch by task_id, pipeline_run_id, or agent_name.

Community
Intermediate
DevelopersGlobalDevelopersGlobal
65

observability

Implement structured logging, distributed tracing, and alerting with OpenTelemetry.

Official
Advanced
saajunaidsaajunaid

aws-serverless-eda

Guide serverless architecture design on AWS with patterns and best practices.

Community
Intermediate