- name
- openclaw-guide
- description
- >
OpenClaw Guide
Use this skill for OpenClaw-specific guidance, not general coding or generic Linux/macOS support.
Scope
Good fits:
- OpenClaw config questions
- gateway restarts / health / logs
- channel routing issues (Telegram, Discord, iMessage, etc.)
- session / agent / cron behavior questions
- “why is OpenClaw doing X?” troubleshooting
Do not use this skill for:
- general shell/debug work unrelated to OpenClaw
- building new features unless the request is specifically about OpenClaw behavior
- security review of third-party code (use a review/audit flow instead)
Default workflow
- Clarify the lane
Identify whether the request is about: - docs / usage - config / schema - runtime health - channel routing - skill structure - cron behavior
- Check local docs first
Prefer local docs before web docs: - /Users/donzurbrick/.openclaw/workspace/docs - /Users/donzurbrick/.openclaw/workspace/AGENTS.md - /Users/donzurbrick/.openclaw/workspace/TOOLS.md - /Users/donzurbrick/.openclaw/workspace/MEMORY.md
- Inspect only the relevant config subtree
Before answering config-field questions or making config changes, inspect the targeted schema subtree. Examples: - channels.telegram - agents.defaults - gateway.auth - commands
- Prefer the smallest explanation or change
- answer with the specific field/path involved - avoid dumping unrelated config - prefer a minimal patch over a broad rewrite
- Verify after mutation
If a restart or config change happens: - run the pre-restart validator if relevant - verify after restart - report pass/fail/warn cleanly
Troubleshooting sequence
For runtime issues, use this order:
- Determine whether the issue is ingress, routing, authorization, model/provider, or delivery
- Check the most specific evidence source available
- Avoid guessing from stale sessions when live config/logs can answer it
- Separate:
- what is verified - what is inferred - what still needs a test
Skill structure rule
When asked to extend OpenClaw behavior, prefer:
- existing tools
- a skill with supporting files
- retrieval/progressive disclosure
- a specialist sub-agent
- a new first-class tool
Do not recommend a new primitive unless the Tool Addition Gate is satisfied.
Supporting references
Read these only if relevant:
references/triage-checklist.md— quick diagnostic flow for common OpenClaw failuresreferences/skill-design-notes.md— how to decide between skill vs tool vs subagent
Output style
- Lead with the diagnosis or answer
- Name the exact config path / command / failure mode
- Distinguish verified facts from best guesses
- Keep it tight unless the issue is architectural