onecli-gateway

Inject stored authentication into external API requests via an HTTPS proxy.

5|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill onecli-gateway-chiptoe-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onecli-gateway
Source: https://github.com/chiptoe-svg/nanoclaw_gccourse/tree/main/container/skills/onecli-gateway
Command: npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill onecli-gateway-chiptoe-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually handling OAuth flows, API keys, and authentication headers for every external service (Gmail, GitHub, Google Calendar, Stripe etc.) is tedious, time-consuming, and risky, as it requires directly handling sensitive credential values.

Core Features & Use Cases

  • Transparent Credential Injection: The OneCLI Gateway HTTPS proxy automatically adds stored authentication to all outbound API requests, so you never need to manually add auth headers or handle credential values directly.
  • Universal Service Support: Works with all connected OAuth and API key-based services including Gmail, Google Workspace, GitHub, Stripe, and Slack, with no per-service configuration needed.
  • Use Case: When a user asks you to check their unread GitHub notifications or retrieve their latest calendar events, you can call the relevant API directly without worrying about authentication, as the proxy handles it automatically.

Quick Start

Ask the AI to retrieve your latest 5 Gmail messages or list your recent GitHub repositories, and it will make the direct API call with all credentials automatically injected via the proxy.

Frequently Asked Questions about onecli-gateway

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

FAQPage Schema
How do I automate OAuth credential injection for external API requests?

A transparent HTTPS proxy automatically injects stored OAuth credentials and API keys into outbound requests, eliminating the need to manually configure authentication headers for external services like Gmail, GitHub, or Stripe.

What is the best way to access Gmail and GitHub APIs without managing API keys manually?

Route requests through a transparent HTTPS proxy that auto-injects stored OAuth tokens and API keys. This removes the need for manual auth header configuration, OAuth CLI tools, or browser extensions when accessing Gmail, GitHub, or Stripe.

Do I need per-service configuration to connect to multiple OAuth platforms like Stripe and Slack?

No, you do not need per-service configuration. The gateway provides universal support for connected OAuth and API key-based platforms like Stripe, Slack, and Google Workspace, automatically applying the correct stored authentication without individual setup.

Can I use this proxy to retrieve my latest GitHub notifications without handling auth headers?

Yes, you can retrieve unread GitHub notifications or calendar events by asking the AI to make the direct API call. The proxy automatically intercepts the request and injects the required authentication headers at the boundary.

Why does manual OAuth flow management pose risks for external API access?

Manual OAuth flow management is risky because it requires directly handling sensitive credential values and configuring authentication headers for every external service, which is tedious and increases the risk of exposing secrets during API access.