nanocoai/nanoclaw / .claude/skills/add-atomic-chat-tool
add-atomic-chat-tool
VerifiedAdd Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.
| File | Kind | Size |
|---|---|---|
| REMOVE.md | markdown | 1.6 KB |
| SKILL.md | skill md | 10.2 KB |
| atomic-chat-env.ts | script | 1.0 KB |
| atomic-chat-mcp-stdio.ts | script | 6.8 KB |
| atomic-chat-registration.test.ts | script | 2.3 KB |
| atomic-chat-wiring.test.ts | script | 2.1 KB |
atomic-chat-env.ts
View on GitHub/**
* Host-side env forwarding for the Atomic Chat MCP tool: any `ATOMIC_CHAT_*`
* host overrides, as spec-shaped env (a record) — argv never crosses
* composition anymore.
*
* The reach-in spreads this into the CONTRIBUTED env lane
* (`ContainerSpec.contributedEnv`), not the composed literal:
* `ATOMIC_CHAT_API_KEY` is credential-NAMED, and the composed lane's key-name
* check would refuse it and deny the spawn. The contributed lane exempts the
* name and still refuses credential-shaped VALUES — which is the right rule
* for a local service token.
*
* Lives in its own file so the reach-in in `container-runner.ts` is a single
* spread and this logic is behavior-testable in isolation.
*/
export function atomicChatEnv(): Record<string, string> {
const env: Record<string, string> = {};
if (process.env.ATOMIC_CHAT_HOST) {
env.ATOMIC_CHAT_HOST = process.env.ATOMIC_CHAT_HOST;
}
if (process.env.ATOMIC_CHAT_API_KEY) {
env.ATOMIC_CHAT_API_KEY = process.env.ATOMIC_CHAT_API_KEY;
}
return env;
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |