Development
Skill
/memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
Claude Code
$ npx -y skills add AVIDS2/memorix --skill memorix-orchestrate --agent claude-code
Codex
$ npx skills add AVIDS2/memorix --skill memorix-orchestrate -a codex -y
Cursor
$ npx skills add AVIDS2/memorix --skill memorix-orchestrate -a cursor -y
Gemini CLI
$ npx skills add AVIDS2/memorix --skill memorix-orchestrate -a gemini-cli -y
GitHub Copilot
$ npx skills add AVIDS2/memorix --skill memorix-orchestrate -a github-copilot -y
OpenCode
$ npx skills add AVIDS2/memorix --skill memorix-orchestrate -a opencode -y
Windsurf
$ npx skills add AVIDS2/memorix --skill memorix-orchestrate -a windsurf -y
SKILL.md
memorix-orchestrate.SKILL.mdname: memorix-orchestrate
description: Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
Memorix Orchestrate
Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.
The standard setup uses the `lite` MCP profile. Coordination MCP tools are exposed only by `team` or `full`; use the CLI fallback for ordinary installations, or explicitly start the server with `--mode team`. Do not probe unavailable team tools in a loop.
Tool Router
| Situation | Prefer | CLI fallback | |---|---|---| | Run managed subagent execution | CLI | `memorix orchestrate --goal "<goal>" --agents claude:1,codex:1` | | Register coordination identity | `team_manage` action `join` | `memorix team join --agentType <agent>` | | Create or inspect tasks | `team_task` | `memorix task create|list|claim|complete` | | Send or read coordination messages | `team_message` | `memorix message send|broadcast|inbox` | | Share structured handoff | `memorix_handoff` | `memorix handoff send` | | Avoid file conflicts | `team_file_lock` | `memorix lock lock|unlock|status` | | Poll joined coordination state | `memorix_poll` | `memorix poll` |
Boundaries
- For ordinary memory, do not join coordination state.
- For production multi-agent execution, prefer `memorix orchestrate` so the main process owns planning, dispatch, retries, and verification gates.
- In worker prompts, use the worker agent ID returned by session start or team join; never use the coordinator ID as the worker identity.
Read more
name: memorix-orchestrate description: Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
Memorix Orchestrate
Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.
The standard setup uses the `lite` MCP profile. Coordination MCP tools are exposed only by `team` or `full`; use the CLI fallback for ordinary installations, or explicitly start the server with `--mode team`. Do not probe unavailable team tools in a loop.
Tool Router
| Situation | Prefer | CLI fallback | |---|---|---| | Run managed subagent execution | CLI | `memorix orchestrate --goal "<goal>" --agents claude:1,codex:1` | | Register coordination identity | `team_manage` action `join` | `memorix team join --agentType <agent>` | | Create or inspect tasks | `team_task` | `memorix task create|list|claim|complete` | | Send or read coordination messages | `team_message` | `memorix message send|broadcast|inbox` | | Share structured handoff | `memorix_handoff` | `memorix handoff send` | | Avoid file conflicts | `team_file_lock` | `memorix lock lock|unlock|status` | | Poll joined coordination state | `memorix_poll` | `memorix poll` |
Boundaries
- For ordinary memory, do not join coordination state.
- For production multi-agent execution, prefer `memorix orchestrate` so the main process owns planning, dispatch, retries, and verification gates.
- In worker prompts, use the worker agent ID returned by session start or team join; never use the coordinator ID as the worker identity.
Stats
926
Stars
77
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
Last commit
Created
Ships withmemorix
Open-source cross-agent memory layer for coding agents via MCP. Compatible with Claude Code, Codex, Cursor, Windsurf, Gemini CLI, Antigravity, OpenClaw, Hermes Agent, Oh-my-Pi, Pi, Copilot, Kiro, OpenCode, and Trae.
8827 skills1 MCP
Stars on GitHub
Momentum
- stars in total
- 882
Other skills on memorix.
More skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about memorix-orchestrate.
- Which coding agents can use memorix-orchestrate?
- memorix-orchestrate installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.