- name
Use Iron Proxy for external accounts and APIs, including GitHub through gh. Connect credentials through the operator console and diagnose blocked requests without exposing tokens or adding unnecessary
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nanocoai/nanoclaw --skill iron-proxy-gateway -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nanocoai/nanoclaw --skill iron-proxy-gateway -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nanocoai/nanoclaw --skill iron-proxy-gateway -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nanocoai/nanoclaw --skill iron-proxy-gateway -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/nanocoai/nanoclaw/tree/HEAD/.claude/skills/add-iron-proxy/payload/container/skills/iron-proxy-gatewayFrom the publisher
Your outbound HTTP and HTTPS requests pass through your session's Iron Proxy. A policy-selected credential request waits for human approval before the proxy inserts a credential. You receive only a useless placeholder.
A bare 403 does not prove which layer rejected the request. It may be the destination rule, credential grant, human approval, or upstream API. Respect the block, report the hostname and observed error, and request a host-side check instead of guessing that credentials were never injected.
Run the shared command for the API hostname requested by the user:
ncl groups connect --host <API hostname>
Return the exact connect_url and describe its action. An operator_console
handoff requires the operator to configure the credential, grant, and destination
in the gateway; it is not an OAuth link. Do not invent a connection flow when the
result is unsupported. The command does not grant access or change policy.
Use the user's requested CLI or a direct HTTP client. Do not add an MCP server
merely to connect an account. Clients requiring local authentication may use
gateway-managed as a non-secret placeholder (for example GH_TOKEN for gh).
Never use a real token in the client. Never run a local login to store credentials.
Request approval and account connection are separate. A 401 is not proof that injection did not happen: the stored token may itself be invalid. Report the observed result, follow the shared handoff, and verify with a credentialed request after the operator completes configuration. Never claim connected before success.
© 2026 Skills Rack.
---name: iron-proxy-gatewaydescription: Use Iron Proxy for external accounts and APIs, including GitHub through gh. Connect credentials through the…---# .claude/skills/add-iron-proxy/payload/container/skills/iron-proxy-gateway/SKILL.mdOverview
Use Iron Proxy for external accounts and APIs, including GitHub through gh. Connect credentials through the operator console and diagnose blocked requests without exposing tokens or adding unnecessary MCP servers.
FAQ
Download .claude/skills/add-iron-proxy/payload/container/skills/iron-proxy-gateway/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/nanocoai/nanoclaw.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.