MoltBank Skill For AI Agents

Use MoltBank for:

• authentication pairing
• treasury balance reads
• pending approval reads
• payment drafting
• x402 discovery and one-shot auto-pay actions

Preferred Execution Order

1. If MCP tools are available, use MCP first.
2. If MCP tools are unavailable, discover exact CLI contract first:
   • moltbank tools list --json
   • moltbank schema --json
   • moltbank schema <command> --json
   • or command --help
3. Execute CLI commands with --json.

Hard Rule

Do not guess flags, argument names, or tool input shapes from memory. Always discover exact usage on demand from MCP tool schemas or CLI schema/help. When using moltbank schema --json, use command name for CLI execution. Do not execute id values (for example moltbank_*) as terminal commands.

When the user asks "what tools/functions can I use", run moltbank tools list --json and answer from that output.

Join / Bootstrap Sequence

When the user asks to "join MoltBank" or to follow setup instructions:

Runtime isolation rule:

• Do not use another runtime's skill manager (for example OpenClaw) to verify or install the skill for the current runtime. Each runtime is independent.

1. Use only the current runtime's native skill mechanism:
   • If current runtime is OpenClaw: run openclaw skills list
   • If current runtime is skills.sh-compatible (for example Claude Code, Codex, Hermes, or Manus when npx skills is available): run npx skills ls
   • If runtime capability is unclear, ask the user which runtime should be configured before running any skill-manager command.
2. Treat the skill as installed only when the current runtime reports it as ready/active.
3. If the skill is missing or not ready, and the user explicitly approves setup, use the current runtime's installer:
   • OpenClaw example: openclaw skills install moltbank, then confirm with openclaw skills list (moltbank must be ✓ ready)
   • skills.sh example (including Claude Code, Codex, Hermes, or Manus when compatible): npx skills add moltbankhq/moltbank-skill
4. Check CLI availability with moltbank --version.
5. If CLI is missing and the user explicitly approves setup, install the CLI:
   • npm install -g @moltbankhq/cli
6. Continue auth flow (moltbank auth begin --json then moltbank auth poll --json after user approval).
7. Verify final state with moltbank whoami --json.
8. If you run moltbank doctor --json and it fails, report exact failing checks; do not claim "all good".
9. During basic join/setup, do not run x402 signer initialization or wallet registration unless the user explicitly requests x402 setup or a requested command requires it.

Never claim "skill installed", "setup complete", or "everything is ready" without command evidence from the current session.

Authentication (Chat-Driven Flow)

If credentials are missing or unauthorized, prefer completing login through chat guidance.

Use this recommended chat flow: