use-native-credential-proxy

Replace OneCLI gateway with a local credential proxy reading .env files for NanoClaw containers.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/E01N/ClawOutreach --skill use-native-credential-proxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-native-credential-proxy
Source: https://github.com/E01N/ClawOutreach/tree/main/nanoclaw/.claude/skills/use-native-credential-proxy
Command: npx skills add https://github.com/E01N/ClawOutreach --skill use-native-credential-proxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces OneCLI gateway with NanoClaw's built-in credential proxy, enabling simple .env-based credential management and seamless injection into container API requests.

Core Features & Use Cases

  • Reads credentials from a local .env file and injects them into container API calls without relying on external services.
  • Phase-guided deployment: pre-flight checks, code changes, and setup steps to switch to the native proxy.
  • Cross-platform support with built-in verification and troubleshooting guidance.

Quick Start

Apply Phase 2 changes to replace OneCLI with the native proxy, then place your credentials in a .env file and restart the service.

Frequently Asked Questions about use-native-credential-proxy

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

FAQPage Schema
How do I inject credentials from a .env file into container API requests?

A native credential proxy reads environment tokens from a local .env file and directly injects them into your container API requests. This removes the need for external gateway dependencies.

What is the best way to replace the OneCLI gateway with local credential management?

Replacing the OneCLI gateway is best achieved by deploying NanoClaw's built-in native credential proxy. It reads credentials from a .env file and manages seamless injection into container API requests locally.

Can I use a .env credential proxy for local and remote container environments?

Yes, the native credential proxy supports developers operating NanoClaw in both local and remote container environments. It includes cross-platform verification and troubleshooting guidance for setup.

How do I set up a native credential proxy for phase-driven deployment?

Set up the native credential proxy by applying phase-guided deployment steps including pre-flight checks and code changes. Place your credentials in a .env file, then restart the service to complete the switch.

Why is my credential proxy not working after switching from an external gateway?

If your credential proxy is not working after switching from an external gateway, use the built-in troubleshooting and verification steps to validate your .env file setup and confirm the service restarted correctly.