use-native-credential-proxy

Replace the OneCLI gateway with NauggieClaw's native credential proxy.

1|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jboothomas/nauggieclaw --skill use-native-credential-proxy-jboothomas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-native-credential-proxy
Source: https://github.com/jboothomas/nauggieclaw/tree/main/.claude/skills/use-native-credential-proxy
Command: npx skills add https://github.com/jboothomas/nauggieclaw --skill use-native-credential-proxy-jboothomas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the fragile OneCLI credential path by reintroducing NauggieClaw's native proxy and ensuring containers receive credentials from the local environment.

Core Features & Use Cases

  • Native credential proxy merge: merges the skill branch, restores credential-proxy imports, and removes @onecli-sh/sdk so containers talk to a local proxy.
  • Config and setup guidance: updates configuration files, clarifies README references, and instructs users to seed API tokens or Claude subscriptions into .env for injection.
  • Verification and recovery: validates with npm build and tests, checks logs for proxy startup, and provides troubleshooting and rollback steps so services stay operational.

Quick Start

Request Auggie to enable the native credential proxy skill and load your credential environment file before restarting the container.

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 local environment credentials into isolated containers?

A native credential proxy allows isolated containers to receive credentials directly from the local environment via .env variables, eliminating fragile external SDK gateway dependencies and ensuring agents operate securely.

What is the best way to replace an external SDK gateway with a local credential proxy?

Merging a native credential proxy module restores local proxy imports, removes the external SDK dependency, and configures containers to use environment variables for authentication, replacing the gateway path entirely.

How do I configure environment variables to control ports and auth tokens for a container proxy?

Seed API tokens or Claude subscriptions into a .env file to control container ports and authentication tokens, allowing the credential proxy to inject these variables securely during container startup.

Does removing an external SDK break container builds when switching to environment-driven credentials?

Removing the external SDK will not break builds if you merge the credential proxy correctly, restore imports, and verify the setup with npm build and tests to ensure environment-driven credentials function.

Why does my container fail to start after switching to a native credential proxy?

Containers may fail to start if the credential proxy file is not merged correctly or .env variables are missing, requiring you to check startup logs, validate the build, and ensure all auth tokens are seeded.