onecli-gateway
OneCLI Gateway: transparent HTTPS proxy that injects stored credentials into outbound calls. You MUST use this skill when the user asks you to read emails, check calendar, access GitHub repos, create issues, check Stripe payments, or interact with ANY external service or API. Do NOT use browser extensions or OAuth CLI tools. Make HTTP requests directly; the gateway injects credentials automatically.
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
~/.claude/skills/(项目级 .claude/skills/)~/.codex/skills/npx oh-my-skill add nanocoai/nanoclaw/onecli-gatewaycurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- nanocoai/nanoclaw/onecli-gatewaynpx oh-my-skill verify nanocoai/nanoclaw/onecli-gateway怎么用
技能原文 SKILL.md
OneCLI Gateway
Your outbound HTTPS traffic is transparently proxied through the OneCLI gateway, which injects stored credentials at the proxy boundary. You never see or handle credential values directly.
How to Access External Services
You have direct HTTP access to external APIs. OAuth apps (Gmail, GitHub, Google Calendar, Google Drive, etc.) and API key services are all available through the gateway. Just make the request directly; the gateway injects credentials if the app is connected. If not, it returns an error with a connect URL you can present to the user.
Making Requests
Call the real API URL. The gateway intercepts the request and injects credentials automatically.
curl -s "https://gmail.googleapis.com/gmail/v1/users/me/messages?maxResults=5" curl -s "https://api.github.com/user/repos?per_page=10" curl -s "https://api.stripe.com/v1/charges?limit=5"
Standard HTTP clients (curl, fetch, requests, axios, Go net/http, git) all honor the HTTPS_PROXY environment variable automatically. You do not need to set any auth headers.
Credential Stubs for MCP Servers
Some MCP servers need local credential files to start. Stubs for connected apps are pre-written automatically. Files containing "onecli-managed" values are managed by OneCLI — do NOT modify or delete them.
If an MCP server won't start due to missing credentials, create stubs before starting it. Use "onecli-managed" as the placeholder for all secret values, with file permissions 0600. See the guide at: https://www.onecli.sh/docs/guides/credential-stubs/general-app
When a Request Fails
If you get a 401, 403, or a gateway error (e.g., app_not_connected):
Step 1 — Show the user a connect link. Use the connect_url from the error response:
To connect [service], open this link: [connect_url from the error response]
If there is no connect_url in the error, tell the user to open the OneCLI dashboard and connect the service there.
Step 2 — Retry after the user connects. Let the user know you will retry once they have connected. When they confirm, retry the original request. If the retry still fails, ask if they need help with the setup.
Rules
- Never say "I don't have access to X" without first making the HTTP request through the proxy.
- Never use browser extensions, gcloud, or manual auth flows. The gateway handles credentials for you.
- Never ask the user for API keys or tokens directly. Direct them to connect the service in the OneCLI dashboard.
- Never suggest the user open Gmail/Calendar/GitHub in their browser when they ask you to read or interact with those services. You have API access. Use it.
- If the gateway returns a policy error (403 with a JSON body), respect the block. Do not retry or circumvent it.