onecli-gateway

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

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/RADHA0-max/selfhealbackend --skill onecli-gateway-radha0-max
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onecli-gateway
Source: https://github.com/RADHA0-max/selfhealbackend/tree/main/nanoclaw/container/skills/onecli-gateway
Command: npx skills add https://github.com/RADHA0-max/selfhealbackend --skill onecli-gateway-radha0-max

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Accessing external services like Gmail, GitHub, Google Calendar, or Stripe normally requires managing OAuth tokens and API keys manually. This Skill routes outbound HTTPS traffic through the OneCLI gateway, which injects stored credentials automatically so you never handle secrets directly. ## Core Features & Use Cases - Transparent Credential Injection: Call any external API directly with curl, fetch, requests, or git; the gateway adds authentication at the proxy boundary. - Guided Error Recovery: When a request returns 401, 403, or app_not_connected, the error includes a connect_url you present to the user so they can link the service. - MCP Credential Stubs: Pre-written placeholder credential files let MCP servers start locally while real secrets stay managed by OneCLI. - Use Case: A user asks you to check their latest Stripe payments. You call the Stripe API directly, the gateway injects the stored API key, and you return the charge list without ever seeing a credential. ## Quick Start Ask the assistant to read your latest Gmail messages or list your GitHub repositories, and it will call the API directly through the gateway.

Frequently Asked Questions about onecli-gateway

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

FAQPage Schema
How do I access Gmail or GitHub APIs without managing OAuth tokens?

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

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

The error response contains a connect_url field. Show that URL to the user so they can connect the service in the OneCLI dashboard, then retry the original request once they confirm the connection.

Does the OneCLI gateway work with standard HTTP clients and git?

Yes. Any client that honors the HTTPS_PROXY environment variable works, including curl, Python requests, Node fetch, axios, Go net/http, and git. The variable is set automatically when launched via onecli run.

Why won't my MCP server start due to missing credentials?

Some MCP servers require local credential files to boot. Create stub files using onecli-managed as the placeholder value for all secrets with 0600 permissions before starting the server; the proxy replaces placeholders with real credentials at request time.

Can I see or modify the credentials the gateway injects?

No. Credentials are injected at the proxy boundary and never exposed to the agent or user. Files containing onecli-managed values are managed by OneCLI and must not be modified or deleted.