Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Imported from openclaw/openclaw (skills/gemini/SKILL.md) via skills.sh. Install upstream with npx skills add openclaw/openclaw --skill gemini. Copyright stays with the author.
Gemini CLI
Use Gemini in headless one-shot mode. Positional text starts interactive mode; use -p/--prompt.
Quick start
gemini -p "Answer this question..."
gemini -m <model> -p "Prompt..."
gemini -p "Return JSON" --output-format json
stdin appends to -p: cat notes.md | gemini -p "Summarize"
Extensions
List: gemini --list-extensions
Manage: gemini extensions <command>
Skills: gemini skills <command>
Hooks: gemini hooks <command>
MCP: gemini mcp <command>
Notes
If auth is required, run gemini once interactively and follow the login flow.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install gemini and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
