opl-atlas-capability-router

Resolve ambiguous OPL Atlas catalog references and generate refs-only route packets.

8|5|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/gaofeng21cn/one-person-lab --skill opl-atlas-capability-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opl-atlas-capability-router
Source: https://github.com/gaofeng21cn/one-person-lab/tree/main/plugins/opl-foundation-skills/skills/opl-atlas-capability-router
Command: npx skills add https://github.com/gaofeng21cn/one-person-lab --skill opl-atlas-capability-router

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about opl-atlas-capability-router

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

FAQPage Schema
How do I resolve catalog routing ambiguity when selecting OPL Atlas references?

To resolve catalog routing ambiguity for OPL Atlas references, use a structured routing workflow that identifies conflicting active owners, stale lifecycle states, and missing edges to prevent incorrect reference selection and authority overreach across agent, capability, and tool-card catalogs.

What is a refs-only route packet in OPL catalog governance?

A refs-only route packet in OPL catalog governance is a structured output containing selected references, rejected alternatives, ambiguity flags, and recommended next legal owner actions, generated without making unauthorized authority claims over catalog boundaries.

How do I diagnose stale lifecycle states and conflicting owners in OPL Atlas catalogs?

You diagnose stale lifecycle states and conflicting owners in OPL Atlas catalogs by applying an ambiguity diagnosis workflow that analyzes refs graph evidence to detect missing edges, misattributed entries, and inconsistencies across source and owner catalogs.

Can I use catalog routing to verify current capability references for a new OPL platform agent?

Yes, you can use cross-catalog ref routing to verify current capability and tool-card references for a new OPL platform agent, ensuring accurate integration by avoiding deprecated or misattributed catalog entries based on lifecycle status.

What are the limitations of cross-catalog reference selection in OPL Atlas?

The limitation of cross-catalog reference selection in OPL Atlas is that it strictly respects catalog authority boundaries, meaning it produces refs-only route packets with ambiguity notes and next owner actions without enforcing authority overreach or making unauthorized claims.

Why does incorrect reference selection happen across multiple OPL Atlas catalogs?

Incorrect reference selection across OPL Atlas catalogs happens because conflicting, stale, or ambiguous entries in agent, capability, tool-card, source, and owner catalogs lead to unintended authority overreach during routing decisions.