Skill category
Use this category when the main job is getting OpenClaw deployed safely and keeping it usable in everyday channels.
Profiles for setup, rollout, and daily operating patterns around OpenClaw.
Use the hub when you need a wider choice set, review methodology, or a different workflow path. Return to the skills overview
Use this profile when the main outcome is getting OpenClaw running with sane defaults, channel bindings, and a clear operator handoff.
curl -fsSL https://openclaw.ai/install.sh | bash2 source signals • Last reviewed 2026-03-11
Do not expose management or gateway surfaces directly to the public internet.
Use this profile when OpenClaw has to coordinate across messaging channels, browser actions, and everyday operator interventions.
npm install -g openclaw@latest2 source signals • Last reviewed 2026-03-11
Keep channel-specific failure handling visible to humans.
Use this profile when OpenClaw is already installed and the next job is connecting model auth, Telegram, WhatsApp, Slack, Discord, or other channel credentials cleanly.
openclaw onboard1 source signals • Last reviewed 2026-03-11
Do not reuse one credential across every channel when scoped tokens are available.
Use this profile when OpenClaw is already running and the next job is editing `openclaw.json`, adjusting gateway behavior, or installing a skill into the workspace.
openclaw skills install <skill-name>1 source signals • Last reviewed 2026-03-11
Review any third-party skill before running `openclaw skills install` against a trusted workspace.
Use this profile when OpenClaw is moving beyond local experiments and you need clear isolation, credential, and review controls.
2 source signals • Last reviewed 2026-03-11
Default to private network access and authenticated operator paths.
Need broader discovery? Skills overview
Need OpenClaw context? OpenClaw workflow