orchestrator

Aggregate skill checkpoints into unified project status and routing recommendations.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/asfbay-bit/opchain --skill orchestrator-asfbay-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/asfbay-bit/opchain/tree/main/skills/orchestrator
Command: npx skills add https://github.com/asfbay-bit/opchain --skill orchestrator-asfbay-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pipeline coordination across multiple skills to provide a single source of truth for status, routing, and next actions, reducing context-switching and miscommunication.

Core Features & Use Cases

  • Reads and aggregates checkpoints from all skills to present a cross-project view.
  • Routes vague intents to the right skill, and suggests next actions.
  • Provides a unified project registry with status and prioritization.

Quick Start

Use /ops to view status, /ops next for the single highest-priority action, and /ops route to dispatch a vague request.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I coordinate cross-skill pipelines to get a unified project status?

Cross-skill pipeline coordination aggregates checkpoints from multiple skills to publish a single source of truth for project status. It reads all skill states without writing to them, ensuring a non-blocking, additive orchestration model.

What is the best way to route vague user intents to the correct skill?

Routing vague intents is handled by analyzing aggregated skill checkpoints and generating intelligent routing recommendations. This dispatches ambiguous requests to the appropriate skill while suggesting relevant next actions.

How do I view the highest-priority next action across multiple projects?

Viewing the highest-priority next action across multiple projects requires aggregating all skill statuses into a unified registry. You can use the /ops next command to surface the single most critical task immediately.

Can I aggregate checkpoints from multiple skills without modifying their original state?

Aggregating checkpoints from multiple skills without modifying their state is supported through a read-only, non-blocking orchestration model. The coordinator reads all skill data to enforce an additive workflow without writing back.

Does cross-skill orchestration work for managing multiple projects at the same time?

Cross-skill orchestration works across multiple projects by reading and aggregating status data from all available skill checkpoints. It provides a centralized project registry with comprehensive status tracking and prioritization.