iii-engine-config — Claude Code skill: what it does, how to install
Configures the iii engine via worker-compose.yaml or config.yaml. Sets up engine ports, observers, RBAC proxy, and configuration storage.
npx skills add iii-hq/iii --skill iii-engine-config -a claude-codeWhat iii-engine-config does
The skill provides schema rules for running the iii engine in one of two distinct modes. In managed mode, Compose owns the process through worker-compose.yaml with a default WebSocket listener at ws://127.0.0.1:49134. Directly supervised mode relies on a list-format config.yaml designed for process managers like systemd or Kubernetes. Mixing the two modes will break startup.
Engine declarations only accept five specific core workers, including configuration and iii-worker-manager. Auxiliary workers like iii-telemetry are injected automatically and will fail validation if declared manually. Any updates to engine: or observers: settings demand a full process restart to take effect.
Production deployments keep the raw engine port bound strictly to localhost. Any public or untrusted traffic routes through rbac-proxy, which handles authentication hooks and limits callable functions.
What it helps with
- configure managed engine settings in worker-compose.yaml
- prepare supervised config.yaml for systemd or Kubernetes
- secure public engine access with the rbac-proxy worker
- set queue limits and depth controls in the observers block
Example prompts for the agent
- Configure worker-compose.yaml for the iii engine with local storage in ./config
- Add an observers block to config.yaml with custom queue limits and timeouts
- Set up rbac-proxy in front of the engine port with an auth function
How to install iii-engine-config
1Skills CLI (Vercel)
npx skills add iii-hq/iii --skill iii-engine-config -a claude-code2Manually: put the files in place
~/.claude/skills/iii-engine-config/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/iii-engine-config/
1Skills CLI (Vercel)
npx skills add iii-hq/iii --skill iii-engine-config -a codex2Manually: put the files in place
.agents/skills/iii-engine-config/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add iii-hq/iii --skill iii-engine-config -a cursor2Manually: put the files in place
.cursor/skills/iii-engine-config/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install iii-hq/iii iii-engine-config2Manually: put the files in place
.github/skills/iii-engine-config/SKILL.md1Skills CLI (Vercel)
npx skills add iii-hq/iii --skill iii-engine-config -a gemini-cli2Platform CLI
gemini skills install https://github.com/iii-hq/iii --path skills/iii-engine-configManually: put the files in place
.devin/skills/iii-engine-config/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add iii-hq/iii --skill iii-engine-config -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set4
The whole set →Similar
Questions about iii-engine-config
How to install iii-engine-config in Claude Code?
Run npx skills add iii-hq/iii --skill iii-engine-config -a claude-code.
What does iii-engine-config do?
It guides configuration of the iii engine across Compose and standalone supervisor setups, covering ports, observer limits, and access controls.
Can application workers be placed under engine workers?
No. Application, HTTP, and database workers must sit under containers:, as the engine worker list only permits five internal core workers.
