omc-reference

Name: omc-reference
Availability: InStock
Author: xdkp

Centralizes OMC agent catalog, tool usage, workflow routing and commit protocol references for Claude Code sessions.

Updated May 20, 2026

Search Tags:#state management #orchestration #skills registry #workflow routing #commit protocol #tool reference #agent catalog

Ready to run

npx skills add https://github.com/xdkp/oh-my-claudecode --skill omc-reference-xdkp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: omc-reference
Source: https://github.com/xdkp/oh-my-claudecode/tree/main/skills/omc-reference
Command: npx skills add https://github.com/xdkp/oh-my-claudecode --skill omc-reference-xdkp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of not having the complete OMC agent catalog, tool reference, and workflow registry available during a session, which forces users to repeatedly look up details or improvise routing.

Core Features & Use Cases

Agent Catalog Lookup: Quickly reference agent roles (e.g., architect, debugger, executor) with model intent and the correct prompt prefix.
Tooling and Skills Registry: Find state/project memory tools, team runtime commands, and built-in workflow skills by name for consistent orchestration.
Workflow Routing & Operational Context: Support correct routing and commit-protocol alignment when delegating to agents, running teams, or invoking workflows.

Quick Start

Ask for the exact OMC entry you need by saying: “Show me the available /oh-my-claudecode workflows and which tools I should use for team orchestration and state management.”

Frequently Asked Questions about omc-reference

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

FAQPage Schema

How do I look up the correct agent role for workflow routing in Claude Code?▼

Workflow routing in Claude Code requires referencing the correct agent role, such as architect or debugger, with the appropriate prompt prefix. A centralized agent catalog provides the exact model intent and routing identifiers needed for accurate delegation without improvising.

What is the best way to access the OMC agent catalog and tool registry during a session?▼

Accessing the OMC agent catalog and tool registry is done by loading a centralized reference that enumerates state management tools, team runtime commands, and built-in workflow skills by name, ensuring consistent orchestration without duplicating reference content in CLAUDE.md.

How do I find the right state management tools and command names for team orchestration?▼

Finding the right state management tools and command names for team orchestration involves querying a built-in skills registry that lists project memory tools, runtime commands, and workflow identifiers, ensuring correct commit-protocol alignment during execution.

Does agent delegation require commit-protocol context and specific workflow identifiers?▼

Agent delegation requires commit-protocol context and specific workflow identifiers to ensure correct routing. A centralized tool reference provides the necessary catalog prefixes and enumerates the state and memory operations needed for execution.

Can I avoid duplicating reference content in CLAUDE.md sessions when doing tool orchestration?▼

Avoiding duplicated reference content in CLAUDE.md sessions is possible by using an auto-loadable catalog reference that applies during delegation and tool orchestration, providing workflow and skill identifiers on demand instead of hardcoding them.

When do I need a centralized reference for workflow routing and state management operations?▼

A centralized reference for workflow routing and state management operations is needed when users must delegate to the correct agents, select orchestration workflows, or look up required command and tool names without manually maintaining reference content.