mxOrchestrate

Manage persistent mxLore workflow stacks and session state via MCP APIs.

29|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/MicrotronX/mxLore --skill mxorchestrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mxOrchestrate
Source: https://github.com/MicrotronX/mxLore/tree/main/claude-setup/skills/mxOrchestrate
Command: npx skills add https://github.com/MicrotronX/mxLore --skill mxorchestrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

mxOrchestrate provides a centralized, always-on orchestrator for mxLore sessions, enabling reliable workflow state management, ad-hoc task tracking, and team-agent coordination across prompts and sessions.

Core Features & Use Cases

  • Persistent workflow stack: manages a LIFO stack of active workflows with automatic park/resume logic.
  • Ad-hoc task tracking and team-agent support: creates TODO items and can spawn team agents for parallel work.
  • Session-bound context enrichment and strict logging: injects context into prompts, logs events, and enforces reconciliation rules to keep local and MCP state in sync.

Quick Start

Trigger a workflow with /mxOrchestrate start <type> or rely on the SessionStart hook to load the current workflow state.

Frequently Asked Questions about mxOrchestrate

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

FAQPage Schema
How do I manage persistent workflow state across multiple MCP sessions?

Persistent workflow state across MCP sessions is managed using a stack-based model that tracks active workflows in a central state file, automatically parking and resuming work while injecting session-bound context into prompts.

How does session state synchronization work for multi-project MCP environments?

Session state synchronization works by enforcing strict event logging with delta tracking and reconciliation rules, keeping local state files and MCP API state in sync across multi-project environments.

Can I track ad-hoc tasks and spawn team agents for parallel work?

Yes, you can track ad-hoc tasks and spawn team agents for parallel work, creating TODO items that run alongside the persistent workflow stack to coordinate multi-agent activities.

What's the best way to resume a parked workflow in a state machine orchestration model?

Resuming a parked workflow in a state machine orchestration model is handled automatically through a LIFO stack, loading the previous workflow state via SessionStart hooks and applying resume enrichment rules.

Do I need a specific MCP setup to use workflow orchestration with mxLore?

Workflow orchestration with mxLore requires an MCP environment supporting specific API calls including session start, document creation, detail retrieval, search, and document update to manage state synchronization.

Why use a LIFO stack for workflow orchestration instead of a flat task list?

A LIFO stack for workflow orchestration automatically handles park and resume logic hierarchically, ensuring the most recently interrupted workflow is prioritized and context is preserved across nested task switches.