How do I install the Ocm Debugging skill?

Run npx skillmds@latest add mathaix/ocm-debugging in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ocm Debugging safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ocm Debugging?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ocm Debugging free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ocm Debugging?

mathaix (@mathaix) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ocm Debugging by mathaix — Agent Skill

Name: Ocm Debugging
Author: mathaix

File contents

OCM Debugging

Use this skill when behavior differs between local, operator, hosted-like, Worker, agent, guest VM, or KVM integration paths and the next move should be a debug signal rather than a guess.

Default Loop

State the suspected boundary:
- profile/config
- auth/cookie/session exchange
- Cloudflare Worker/KV routing
- host enrollment or heartbeat
- placement/capacity
- backend-to-agent API
- metadata server
- guest init/rootfs
- Firecracker network/storage
- runtime artifact/version selection
Add or enable the narrowest signal that proves that boundary.
Reproduce with the same profile, env, domain shape, host state, and runtime version. Do not switch profiles or providers unless that variable is under test.
Compare configured state with actual activated state.
Patch the root cause.
Rerun the exact failing probe, then broaden only if a shared contract needs it.

Useful Starting Points

Config/profile load: backend/internal/config.
Session cookies and auth: backend/internal/api/auth_handlers.go.
Worker route selection and resolve fallback: worker/worker.js.
Route provisioning and signing keys: backend/internal/routing.
Machine start/upgrade lifecycle: backend/internal/machines/runtime.go.
Host enrollment: backend/internal/api/enrollment.go.
Agent control API: backend/internal/agentapi.
Firecracker orchestration: backend/internal/orchestrator.
Guest metadata: backend/internal/metadata.
Guest init: scripts/init-openclaw.sh.
Local full-stack runbook: docs/local-firecracker-e2e.md.

Proof Choices

Single backend invariant: focused Go package test.
Worker route/auth bug: make test-worker.
Frontend/auth UI bug: focused frontend test plus make typecheck.
Local control-plane setup: make local-status or the relevant scripts/local-dev.sh command.
Firecracker/agent/rootfs/network bug: KVM integration or local scripts/local-e2e-firecracker.sh status, with exact blocker reported when unavailable.
Cloudflare/operator routing bug: local Worker test plus config/doc review; live Cloudflare proof only when credentials and operator approval are present.

Output Habit

Report:

boundary tested
command or probe used, with secrets redacted
observed signal
fix location
narrow proof
remaining risk

---name: ocm-debuggingdescription: Debug OpenClaw Machines profile, auth, Worker routing, host enrollment, agent API, Firecracker, rootfs, and VM runtime behavior by choosing the right boundary and proof before changing code.---# OCM DebuggingUse this skill when behavior differs between local, operator, hosted-like,Worker, agent, guest VM, or KVM integration paths and the next move should be adebug signal rather than a guess.## Default Loop1. State the suspected boundary: - profile/config - auth/cookie/session exchange - Cloudflare Worker/KV routing - host enrollment or heartbeat - placement/capacity - backend-to-agent API - metadata server - guest init/rootfs - Firecracker network/storage - runtime artifact/version selection2. Add or enable the narrowest signal that proves that boundary.3. Reproduce with the same profile, env, domain shape, host state, and runtime version. Do not switch profiles or providers unless that variable is under test.4. Compare configured state with actual activated state.5. Patch the root cause.6. Rerun the exact failing probe, then broaden only if a shared contract needs it.## Useful Starting Points- Config/profile load: `backend/internal/config`.- Session cookies and auth: `backend/internal/api/auth_handlers.go`.- Worker route selection and resolve fallback: `worker/worker.js`.- Route provisioning and signing keys: `backend/internal/routing`.- Machine start/upgrade lifecycle: `backend/internal/machines/runtime.go`.- Host enrollment: `backend/internal/api/enrollment.go`.- Agent control API: `backend/internal/agentapi`.- Firecracker orchestration: `backend/internal/orchestrator`.- Guest metadata: `backend/internal/metadata`.- Guest init: `scripts/init-openclaw.sh`.- Local full-stack runbook: `docs/local-firecracker-e2e.md`.## Proof Choices- Single backend invariant: focused Go package test.- Worker route/auth bug: `make test-worker`.- Frontend/auth UI bug: focused frontend test plus `make typecheck`.- Local control-plane setup: `make local-status` or the relevant `scripts/local-dev.sh` command.- Firecracker/agent/rootfs/network bug: KVM integration or local `scripts/local-e2e-firecracker.sh status`, with exact blocker reported when unavailable.- Cloudflare/operator routing bug: local Worker test plus config/doc review; live Cloudflare proof only when credentials and operator approval are present.## Output HabitReport:- boundary tested- command or probe used, with secrets redacted- observed signal- fix location- narrow proof- remaining risk

Frequently asked questions

Ocm Debugging