onecli-gateway

Proxies outbound HTTPS requests and injects stored credentials into external API calls.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill onecli-gateway-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onecli-gateway
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/container/skills/onecli-gateway
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill onecli-gateway-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents often need to call external services like Gmail, GitHub, Google Calendar, or Stripe, but handling OAuth tokens and API keys directly is risky and cumbersome. This Skill routes all outbound HTTPS traffic through the OneCLI gateway, which injects stored credentials at the proxy boundary so the agent never sees or handles secret values. ## Core Features & Use Cases - Transparent Credential Injection: Call real API URLs directly with curl, fetch, requests, or any HTTP client; the gateway adds authentication automatically via the HTTPS_PROXY environment variable. - Guided Error Recovery: When a request returns 401, 403, or app_not_connected, surface the connect_url from the error response so the user can link the service, then retry. - MCP Credential Stubs: Create placeholder credential files with "onecli-managed" values so MCP servers that require local credentials can start, while the proxy supplies real secrets at request time. - Use Case: A user asks the agent to summarize their latest unread emails; the agent calls the Gmail API directly, the gateway injects the Google OAuth token, and results return without any manual key setup. ## Quick Start Ask the agent to read your latest Gmail messages or list your GitHub repositories, and it will make the API request through the gateway automatically.

Frequently Asked Questions about onecli-gateway

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

FAQPage Schema
How do I call external APIs like Gmail or GitHub from an agent?

Make HTTP requests directly to the real API URL using curl, fetch, requests, or any standard HTTP client. The OneCLI gateway intercepts the request via the HTTPS_PROXY environment variable and injects stored credentials automatically, so no auth headers are needed.

How does the OneCLI gateway inject credentials into API requests?

The gateway acts as a transparent HTTPS proxy at the network boundary. When a request passes through it for a connected app, it adds the stored OAuth token or API key before forwarding, so the agent never sees or handles credential values.

What should I do when an API request returns 401 or app_not_connected?

Show the user the connect_url from the error response as a bare URL on its own line so they can link the service. After the user confirms the connection, retry the original request; if it still fails, offer help with the setup.

Does the OneCLI gateway work with MCP servers that need local credentials?

Yes. Create credential stub files containing "onecli-managed" as the placeholder for all secret values with file permissions 0600 before starting the MCP server. The proxy replaces placeholders with real credentials at request time.

Can I use gcloud CLI or browser extensions instead of the gateway?

No. The Skill explicitly prohibits browser extensions, gcloud, and manual auth flows because the gateway already handles credentials. Direct HTTP requests through the proxy are the supported path for all connected services.