Skill profile
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.
SkillsMP + verified GitHub source • Last reviewed 2026-03-11
A verified source command exists for direct skill installation inside an existing OpenClaw workspace.
openclaw skills install <skill-name>The upstream config skill documents this as the direct path for installing a skill into the OpenClaw workspace.
Operators maintaining an existing OpenClaw instance who need to change config safely or install additional skills without turning the workspace into guesswork.
This profile covers configuration and day-two administration: binding and port settings, workspace files, channel config, update channels, and the direct `openclaw skills install <skill-name>` path for adding a skill.
Operators maintaining an existing OpenClaw instance who need to change config safely or install additional skills without turning the workspace into guesswork.
Most OpenClaw friction appears after the first successful boot. A config-focused profile helps teams manage drift, review skill installs, and keep gateway behavior understandable.
Move back to the category or hub instead of jumping to the homepage and losing context.
Review methodology and manuals before treating a public profile or copied command like production-ready guidance.
When the profile belongs to OpenClaw operations, continue inside the OpenClaw cluster instead of starting over.
Generated from SkillsMP discovery and upstream GitHub SKILL.md verification. This profile uses the config skill as the main evidence source for workspace configuration and skill installation commands.
OpenClaw skills • OpenClaw security • OpenClaw skill category • Skills overview • Submit • Advertise
Use this profile when the main outcome is getting OpenClaw running with sane defaults, channel bindings, and a clear operator handoff.
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.
Use this profile when OpenClaw has to coordinate across messaging channels, browser actions, and everyday operator interventions.