ZES-skill-orchestrator

Coordinate discovery, loading, and routing of modular skills in the ZES framework.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-skill-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ZES-skill-orchestrator
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/.agents/skills/ZES-skill-orchestrator
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-skill-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the fragmentation of agent capabilities by providing a centralized discovery and routing mechanism for the entire ZES ecosystem, ensuring agents always access the correct tools.

Core Features & Use Cases

  • Centralized Discovery: Automatically indexes and prioritizes 28+ ZES and ECC skills across multiple directory paths.
  • Hierarchy Management: Enforces strict routing rules to ensure ZES-prefixed skills take precedence over global or cached plugins.
  • Use Case: When starting a new development session, use this skill to initialize the environment, ensuring the agent correctly identifies and loads the specific ZES-subagent or ZES-memory-ops tools required for the task.

Quick Start

Invoke the ZES skill orchestrator to scan all available directories and establish the current session's skill hierarchy.

Frequently Asked Questions about ZES-skill-orchestrator

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

FAQPage Schema
How do I manage skill hierarchy and routing for modular agent instruction sets?

Skill hierarchy and routing for modular agent instruction sets is managed by enforcing priority-based indexing and path resolution across local directories, plugin caches, and global instruction sets. This ensures deterministic access to core capabilities during agentic workflows.

What is the best way to automate discovery and loading of modular skill units?

Automating discovery and loading of modular skill units is best handled by a centralized orchestration mechanism that automatically indexes and prioritizes available skills across multiple directory paths. This enforces strict precedence rules for deterministic tool access.

How do I initialize a development session to ensure correct ZES-subagent and ZES-memory-ops tool loading?

Initializing a development session for correct tool loading requires invoking an orchestrator to scan all available directories and establish the current session's skill hierarchy. This ensures the agent identifies and loads the specific modular tools required for the task.

Can I use priority-based indexing to enforce ZES-prefixed skills over cached plugins?

Yes, priority-based indexing enforces strict routing rules that ensure ZES-prefixed skills take precedence over global or cached plugins. This hierarchy management guarantees that agents access the correct tools across local and global directory paths.

Why does my agent access fragmented tools instead of the correct modular skill units?

Agents access fragmented tools instead of correct modular skill units due to a lack of centralized discovery and routing. Implementing an orchestration framework with strict priority-based indexing solves this fragmentation by ensuring deterministic path resolution.