omc-reference

Catalog OMC agents, tools, routing decisions, and commit protocols.

5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill omc-reference-robinnorberg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-reference
Source: https://github.com/RobinNorberg/oh-my-copilot/tree/main/skills/omc-reference
Command: npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill omc-reference-robinnorberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This reference provides a centralized catalog of OMC agents, tools, routing decisions, commit protocols, and a skills registry, enabling consistent delegation and configuration across teams.

Core Features & Use Cases

  • Agent catalog and routing guidance to map tasks to the right Haiku/Sonnet/Opus agents.
  • Centralized tools and workflows registry that auto-loads during delegation to agents.
  • Team pipeline concepts (plan, exec, verify, fix) and standardized commit protocol guidance to maintain execution history.

Quick Start

Invoke the built-in OMC reference to explore available agents and workflows.

Frequently Asked Questions about omc-reference

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

FAQPage Schema
How do I centralize agent routing and workflow rules for cross-team coordination?

Centralized agent routing is provided through a reference catalog that maps tasks to the right Haiku, Sonnet, or Opus agents and auto-loads workflow rules during delegation to maintain consistent cross-team coordination.

What is the best way to orchestrate team pipelines using automated delegation?

Orchestrating team pipelines involves applying standardized plan, exec, verify, and fix concepts alongside a centralized tools registry that automatically loads when delegating tasks to agents to ensure consistent execution.

How does autoload behavior work when delegating tasks to agents?

Autoload behavior automatically loads the centralized tools and skills registry during agent delegation, supplying the necessary workflow rules and routing guidance without requiring manual configuration for each delegated task.

Do I need a centralized registry to maintain standardized commit protocols across agents?

A centralized registry is needed to maintain standardized commit protocol guidance and execution history, ensuring all agents follow consistent commit rules and governance during cross-agent coordination.

Can I use this reference to map tasks to specific Haiku, Sonnet, or Opus agents?

You can use the agent catalog to map tasks to specific Haiku, Sonnet, or Opus agents, as it provides explicit routing guidance and routing decisions to direct tasks to the appropriate model.

What limitations should I expect when applying cross-agent coordination workflows?

Cross-agent coordination limitations depend on the centralized reference load and the tools registry scope, meaning delegation workflows are constrained to the agents, commit protocols, and routing rules currently cataloged.