What problem does it solve?
When working with OPL's multiple catalogs (agent, capability, tool-card, source, owner, etc.), conflicting, stale, or ambiguous entries can lead to incorrect reference selection and unintended authority overreach. This Skill eliminates that risk by providing a structured routing workflow that strictly respects catalog authority boundaries.
Core Features & Use Cases
- Cross-Catalog Ref Routing: Selects the correct owner, source, skill, connector, tool-card, and capability references from OPL Atlas catalogs based on current lifecycle status and refs graph evidence.
- Ambiguity Diagnosis: Identifies conflicting active owners, stale lifecycle states, missing edges, and other catalog inconsistencies to prevent incorrect routing decisions.
- Refs-Only Packet Generation: Produces structured route packets with selected refs, rejected alternatives, and ambiguity notes for program owners, without making unauthorized authority claims.
- Use Case: OPL platform developers building a new medical research agent use this Skill to verify the correct, current capability and tool-card references from the catalog, avoiding integration with deprecated or misattributed entries.
Quick Start
Use the opl-atlas-capability-router skill to generate a refs-only route packet for the new book-writing agent's capability and source catalog entries, including all ambiguity notes and recommended next owner actions.