Recently listed SKILL.md agent skills ordered by publication date, newest first. Filtered addresses are excluded from the search index so that they do not duplicate this list.
Step-by-step agent workflow to configure the OpenAI Codex CLI on any machine (Linux, macOS, Windows) to use OmniRoute as an OpenAI-compatible backend. Detects OS and shell, writes config.toml and 7 named profiles, sets environment variables, and verifies the setup.
Start and stop tunnel connections (ngrok, Cloudflare, custom) from the CLI. Inspect active tunnel URLs, configure authentication, and test external reachability.
Detect installed CLI coding tools (Claude Code, Codex, Cursor, Copilot, Cline and more), search GitHub for matching agent skills, and install them to the detected tools via OmniRoute's built-in APIs.
Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart via the CLI setup and config commands.
Operate on Jira issues — read, create, comment, and transition — through a Jira Cloud site the user's team has bound to Nuphos via OAuth. Use whenever the user asks to open/track/close a Jira issue, file a ticket for an incident, comment on an issue, or check issue status. Nuphos backend hands the agent a short-lived Atlassian access token + cloudId; the agent calls api.atlassian.com/ex/jira/<cloudId>/rest/api/3 directly with curl.
Call Huawei Cloud (华为云) REST APIs from the sandbox with the bundled signer to inspect or change Huawei Cloud resources (CCE, ECS, ELB, VPC, OBS, RDS, etc.). Includes a script to load a Nuphos-bound Huawei Cloud account's short-lived federated credentials.
Run hcloud CLI commands from the sandbox to inspect or change Hetzner Cloud resources — servers, volumes, networks, firewalls, load balancers, floating IPs, and images. Includes a setup script for selected Nuphos-bound Hetzner accounts.
Connect the foreman's session to a builder in an Orca pane, Pi or Claude Code (any Claude model), and PROVE the link (a pane the foreman opened itself (or one the owner confirmed) + assigned session id, two-round handshake, Stop-log and session-file evidence), then send work-order pointers and wait on the builder's real turn-end signal. Use for /orca-pi-connect, "connect to pi", "connect to the claude builder", "set up the builder pane", or before a Topping Out job whose repo profile says builder delivery = pane link. Orca only (another pane host: hand-carry the pointers). Proves and uses the channel; never decides or approves anything for the owner. Also answers to its old name, /pi.
Topping Out's first step: turn a fuzzy ask into a decision-complete, codebase-grounded commission block by settling every open question first. Use when the owner runs /f-survey, says "survey this", "groom this" (the old name), "this is still vague", "tighten this before we build", "what am I missing", or hands over work whose scope or approach is not yet decided. Add --voice (or say "survey this out loud", "talk me through it") to run it aloud as a colleague conversation, one short turn at a time. Also answers to its old name, /f-groom. Next step: /f-blueprint. Not the site walk (the machine check at the start of a job, METHOD §2). Not for writing the plan (f-blueprint) or cutting it into tickets (f-schedule).
Catch the owner up in plain English on a Topping Out job: where we are, what got done, the state now, what's next. Reads ONLY the live session; no subagents, no git, no file reads, no writes. Use when the user runs /f-status, says "catch me up", "where are we", "I'm lost", "refresh me", or comes back after stepping away. Not the 5-line status block every reply ends with (templates/J-STATUS.md).
Start, stop, and restart the OmniRoute server from the CLI. Manage daemon mode, port configuration, auto-recovery, system tray integration, and the dashboard open shortcut.
Create, list, update, and delete routing combos from the CLI. Test routing strategies, inspect combo metrics, and configure fallback chains interactively.
Inspect and manage circuit-breaker states, connection cooldowns, quota limits, and backoff levels from the CLI. Reset stuck providers and configure resilience thresholds.
Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.
Install applications onto an Nuphos-managed Kubernetes cluster using the helm CLI from inside the sandbox. Use this for chart-based deploys ("install Inngest", "deploy ingress-nginx", "set up cert-manager"). Includes an install script for the helm binary.
Inspect and operate Grafana instances bound to an Nuphos team. All HTTP calls go through Nuphos backend's authenticated proxy — no SA token handling, no CORS, no extra setup. Covers dashboards, folders, datasources, queries (/api/ds/query), alerting, and Loki/Prometheus log + metric pulls.
Read and act on the message sender's own Gmail, Google Drive and Google Calendar — search, read, label, draft and send mail; search, read, upload, and share Drive files and Google Docs/Sheets; list, create and update calendar events — through the Gmail, Google Drive or Google Calendar Personal Credential the member connected in Nuphos Settings. Use whenever the user asks about their email or inbox, wants a reply drafted or sent, asks to find, read, or save a file in their Google Drive, or asks about their schedule or to set up a meeting. Nuphos hands the agent a short-lived Google access token; the agent calls the Gmail, Drive and Calendar REST APIs directly with curl.
Close a merged Topping Out job (one ticket): check the acceptance ledger is all PASS, reconcile planned-vs-built, fill and archive the job file, then hand over to the board close. Use when the user runs /f-signoff, says "close this job", "we're done, wrap it up", after the merge is verified. No deferrals, no close-anyway, never retires the blueprint. Not for committing or pushing (the owner's word). Also answers to its old name, /f-close.
Inspect audit logs, manage access policies, view telemetry data, and review request history from the CLI. Filter by event type, user, or time range for compliance workflows.
Query available AI models, list model aliases, and browse the full model catalog from the CLI. Filter by provider, search by capability, and resolve model name variants.
Operate on GitLab projects, merge requests, pipelines, and repository contents through a GitLab account the user's team has bound to Nuphos. Nuphos backend hands out the binding's short-lived OAuth token; the agent talks to the GitLab API and clones or pushes over HTTPS directly. Use whenever the user asks about their GitLab repos, MRs, CI pipelines, wants code read from a GitLab repo, or asks to open/update/comment on merge requests.
Sign a participant's local git commits and tags with their own SSH signing key in the agent sandbox, isolated per Nuphos participant. Use when someone asks for commits signed with their own key, or when a change needs a real git commit / git push (file modes, symlinks, submodules, several commits) that must be Verified.