portal-router — cross-agent capability resolution

When capabilities are spread across many agent ecosystems (Claude, Codex, Gemini, OpenCode, OpenClaw, a shared .agents pool, a skills distribution), the expensive question is no longer "how do I do X" but "which of my agents already has a skill for X, and how do I load it?" portal-router answers that from one place.

It treats every ecosystem as a capability source, normalizes their heterogeneous unit shapes into one record, ranks matches against an intent, and loads the chosen unit. It is the skill an orchestrator reaches for before authoring a new skill — to check whether the fleet already owns the capability.

When to use

• "Which agent has a skill for PDF extraction / k8s / data cleaning?"
• "Find me a capability that does Y" — across all agents, not just the current one.
• Before forging a new skill: confirm the fleet doesn't already have one.
• Routing a task to whichever agent owns the right tool.