OXYGEN GTM

This is the fallback router, not a command encyclopedia. Prefer a narrower installed skill when the capability card names one.

Discover, then hydrate

Start from the outcome, not a product noun:

oxygen capabilities search "<goal>" --json
oxygen commands get "<recommended command>" --json

With MCP: oxygen_capabilities_search, then oxygen_capabilities_schema for the selected names. Provider operations are a separate catalog: bounded oxygen tools search "<intent>" --json, then oxygen tools get <tool_id> --json. Search selects; get/schema explains exact inputs, current cost, availability, and gates.

Ownership map