Advanced skill-only compatibility

Boomkin's complete onboarding flow uses native Hermes; start with the getting-started guide. The adapters below install portable skills in other harnesses. Models, credentials, tools and hosting remain with your selected harness.

Examples use the installed boomkin command. From a source checkout, replace it with bun run boomkin.

Choose a harness

Boomkin supplies the crypto skill catalog and setup/update commands. The upstream harness owns models, authentication, tools, chat, memory, permissions, and hosting. Install the runtime from its official source; Boomkin does not vendor it.

Hermes

For a complete Boomkin profile, use native onboarding:

boomkin onboard --directory "$HOME/boomkin-hermes"
boomkin start --directory "$HOME/boomkin-hermes"

To add only the skills to an existing Hermes home:

boomkin setup --harness hermes --directory "$HOME/your-hermes-profile"

Boomkin passes that directory as HERMES_HOME to the skill installer, which writes to its skills/ directory. Use your existing native Hermes launch configuration for that profile. Follow Hermes gateway documentation for persistent operation.

Eve

Create an upstream Eve project:

bunx eve@latest init "$HOME/boomkin-eve"
boomkin setup --harness eve --directory "$HOME/boomkin-eve"
cd "$HOME/boomkin-eve"
bunx eve dev
# When ready to deploy using your Vercel account:
bunx eve deploy

Skills are copied into agent/skills/, including their references and scripts. Existing agent/instructions.md is preserved: merge the Boomkin identity into it. Update skills before building/deploying; an existing cloud deployment does not change when local files change. Redeploy through Eve after reviewing updates.

OpenClaw

Install and onboard OpenClaw. Use the actual workspace selected during onboarding:

openclaw onboard
# Change the path if your selected workspace differs:
boomkin setup --harness openclaw --directory "$HOME/.openclaw/workspace"
openclaw skills list

Boomkin uses workspace skills/, not shared global skills. Preserve your existing AGENTS.md; merge the identity if wanted. Follow upstream guidance for a gateway or remote deployment. Skills alone do not configure an exchange connection.

Codex, Claude Code, and OpenCode

Install/sign in using the native upstream installer, then:

boomkin setup --harness codex --directory "$HOME/boomkin-codex"
boomkin setup --harness claude --directory "$HOME/boomkin-claude"
boomkin setup --harness opencode --directory "$HOME/boomkin-opencode"

Launch the corresponding agent from its directory. Codex and OpenCode use .agents/skills/; Claude Code uses .claude/skills/.

Support contract

These adapters install the same upstream Agent Skills files in each harness's documented discovery location. They do not promise identical tool availability, wallet support, or model behaviour. A successful setup proves file installation, not authenticated model execution or deployment. Ask your agent to use the installed infrastructure/data or protocol setup skill and perform the first read-only task before adding tools or credentials. Choose only the needed packs with repeated --pack flags; saved selections remain unchanged when the reviewed catalog grows.

To support another harness, add its upstream installer agent ID and documented skill path in src/core.ts, then verify a clean install and discovery. Prefer the existing Agent Skills installer over a custom installation implementation.