Connect OpenClaw to SkilzVolt

Run both commands in the terminal that runs OpenClaw:

openclaw mcp add skilzvolt --url https://app.skilzvolt.com/mcp --transport streamable-http
openclaw mcp login skilzvolt

1. Complete the SkilzVolt sign-in and consent flow in the browser opened by OpenClaw.
2. Return to OpenClaw and verify the connection with a workspace list and a skill read.

Use OAuth for OpenClaw. Do not ask a person for a connection key, screenshot, or redacted credential.

1. Call workspaces_list — List the workspaces available to this connection.
2. Call skills_search — Search for a relevant skill in an available workspace.
3. Call skills_get — Open one search result and read its current content.

Confirm success only after both a workspace list and a skill read succeed.

The signed-in SkilzVolt user's live workspace memberships determine which workspaces are available. Skill writes create proposals and continue to follow each workspace's review policy.

The MCP connection makes SkilzVolt tools and current skill content available to OpenClaw. It does not automatically install SkilzVolt skills into OpenClaw's local runtime or guarantee that OpenClaw will consult them for every task.

Dynamic MCP retrieval — OpenClaw searches and reads the current approved skill through SkilzVolt MCP tools when organisation-specific work begins.

Do not create or maintain a local runtime mirror for organisation-specific skills. SkilzVolt is the only canonical source; a local copy would create a competing source of truth and must not be edited or treated as approved.

Do not retire another canonical skill publisher until dynamic MCP retrieval has been tested with an approved skill, a proposed change, a review decision, an export, and a rollback.

• Machine-readable connection manifest
• Plain-text connection contract
• OpenClaw migration runbook (plain text)
• AI discovery document (llms.txt)