skills.rest
LIMITLESS-LONGEVITY
LIMITLESS-LONGEVITYOFFICIAL
Explore all skills by this author →
WebsiteGitHub

use-native-credential-proxy

Replace the OneCLI gateway with a local .env-based credential proxy for container API requests.

Updated Apr 2, 2026
Search Tags:#claude#containers#anthropic#nanoclaw#credential-proxy#env-credentials#onecli
One-click install
npx skills add https://github.com/LIMITLESS-LONGEVITY/limitless --skill use-native-credential-proxy-limitless-longevity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: use-native-credential-proxy
Source: https://github.com/LIMITLESS-LONGEVITY/limitless/tree/main/apps/nanoclaw/.claude/skills/use-native-credential-proxy
Command: npx skills add https://github.com/LIMITLESS-LONGEVITY/limitless --skill use-native-credential-proxy-limitless-longevity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replace an external credential gateway with a local, built-in credential proxy so containers receive API keys or OAuth tokens directly from a machine-managed .env file, eliminating the need to install and configure OneCLI for credential delivery.

Core Features & Use Cases

  • Local .env-based credential injection: Reads ANTHROPIC_API_KEY or CLAUDE_CODE_OAUTH_TOKEN from .env and exposes them to containers via a local HTTP proxy.
  • Claude and Anthropic support: Works with Claude subscription tokens obtained via claude setup-token or standard Anthropic API keys.
  • Minimal infrastructure: Uses a platform-aware bind address and default proxy port 3001, suitable for local Docker, WSL, and systemd-managed environments.
  • Developer workflow integration: Provides git merge instructions to apply the skill branch, test steps to validate proxy startup, and explicit rollback steps to revert to OneCLI if needed.
  • Use case: Ideal for developers who want a simple, self-hosted credential flow for Nanoclaw agents without adding external CLIs or services.

Quick Start

Merge the native-credential-proxy branch, add your Anthropic API key or Claude OAuth token to .env, and restart Nanoclaw so the local proxy injects credentials into running containers.

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 .env credentials into Docker containers for Anthropic API requests?▼

You can inject .env credentials by deploying a native credential proxy that reads ANTHROPIC_API_KEY or CLAUDE_CODE_OAUTH_TOKEN and exposes them to containers via a local HTTP proxy on port 3001.

Can I use a Claude OAuth token instead of an Anthropic API key for container integrations?▼

Yes, the native credential proxy supports Claude OAuth tokens obtained via claude setup-token as well as standard Anthropic API keys read directly from your local .env file.

How do I replace OneCLI with a local credential proxy for NanoClaw deployments?▼

Merge the skill/native-credential-proxy branch, restore credential-proxy files, remove the @onecli-sh/sdk dependency, and add your credentials to .env to replace the OneCLI gateway with local proxy injection.

Does the native credential proxy work with WSL and systemd-managed environments?▼

Yes, the credential proxy uses a platform-aware bind address and default port 3001, making it suitable for local Docker, WSL, and systemd-managed NanoClaw environments.

What's the best way to roll back to OneCLI if the local credential proxy fails?▼

The skill provides explicit rollback steps to revert your NanoClaw deployment back to the OneCLI gateway if the native credential proxy encounters startup or configuration issues.

Why do I need to remove the @onecli-sh/sdk dependency when switching to a local credential proxy?▼

Removing the @onecli-sh/sdk dependency eliminates the external CLI requirement, allowing the built-in local HTTP proxy to handle credential delivery entirely from your machine-managed .env file.

Related Skills

Explore More Software Engineering Skills→
E01NE01N

use-native-credential-proxy

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

Community
Advanced
chiptoe-svgchiptoe-svg

use-native-credential-proxy

Replace the OneCLI gateway with a local HTTP credential proxy reading .env files.

Community
Intermediate
stevengonsalvezstevengonsalvez

use-native-credential-proxy

Replace OneCLI gateway with NanoClaw's built-in credential proxy for .env-based credential injection.

Community
Intermediate
OfirGavishOfirGavish
3

init-onecli

Migrate .env credentials to the OneCLI Agent Vault and configure the gateway.

Community
Advanced