OpenClaw is installed and you want to add search, weather, docs, notifications and more? This guide is for beginners and advanced users who already have OpenClaw. It explains what the Skill marketplace (ClawHub) is and how it relates to plugins, how to install and update skills (openclaw skills / ClawHub), 10 common scenario setup tips, and notes and pitfalls when using Skills on a remote Mac, so you can avoid common issues and get up and running quickly.
What is the OpenClaw Skill marketplace? Relation to plugins
OpenClaw Skills are capability modules the AI can call: web search, run terminal commands, send notifications, check weather, read and write documents, and so on. The official skill marketplace is often called ClawHub; in 2026 it lists many skills for search, communication, productivity, and development. In most docs, "skills" and "plugins" mean the same thing: after installation they appear under ~/.openclaw/skills/ or the workspace skills directory, and OpenClaw loads them on demand during conversations.
Load order is usually: workspace skills first, then user-directory skills, then built-in skills. Knowing this helps when debugging "installed but not working" or "version conflict" issues.
Install and update skills: skill update, permissions and common failures
Install and update are done from the command line or the Dashboard. Common commands:
openclaw skills search <keyword>: search the marketplace.openclaw skills install <skill-id>: install a skill (e.g.openclaw skills install gmail).openclaw skills update --alloropenclaw skills update <skill-id>: update all or a single skill.openclaw skills list: list installed skills.
Common failure causes: network timeouts (configure mirror or proxy if needed), insufficient permissions (install directory not writable), Node or dependency version mismatch (check skill requirements). On a remote Mac over SSH, ensure ~/.openclaw/skills is writable; over VNC desktop, usage is the same as local and you can complete auth or config dialogs as prompted.
~/.openclaw/skills/<skill-id>/; some skills support --configure to complete setup during install.10 common skill scenarios: search, weather, calculator, docs, notifications and more
The table below summarizes 10 common 2026 use cases and their setup focus.
| Scenario | Example skills / direction | Setup notes |
|---|---|---|
| Web search | Brave Search, web search | API key or network access; some have free tiers. |
| Weather | Weather lookup | City or API; check units and region. |
| Calculator / tools | Calculator, unit conversion | Usually no extra config; install and use. |
| Docs / notes | Notion, doc read/write | OAuth or API token; follow skill docs in its directory. |
| Gmail, send/receive | Account auth or app password; check security scope. | |
| Calendar | Google Calendar etc. | Calendar API or OAuth; match account permissions. |
| Messaging | Telegram, Feishu, Slack, Discord | Bot token or app config; create app on platform and fill in. |
| Development | GitHub, terminal/shell | GitHub needs PAT; shell needs execution and sandbox awareness. |
| Schedule / reminders | Cron, Wake-style | System or gateway support for scheduling; check cron or scheduler. |
| Browser automation | Agent Browser etc. | Browser and permissions; on remote Mac needs GUI or headless. |
Using Skills on a remote Mac: notes and performance
When running OpenClaw on a remote Mac (e.g. VNC desktop), skills behave the same as local, but keep in mind:
- Network: Some skills need internet or specific APIs; if the remote node is restricted, allow outbound access at the node or gateway.
- GUI / browser skills: Skills that need a display or local browser work on a remote Mac with VNC; over pure SSH with no display they may not work for dialogs or browser actions.
- Paths and permissions:
~/.openclaw/skillsis the current user dir; in multi-user or container setups, distinguish users; when updating, ensure no other process is using that directory.
Pitfalls and FAQ: conflicts, dependencies, not taking effect after update
Skill installed but not working? Run openclaw skills list to confirm; check the skill docs for trigger or extra config; then check load order (workspace vs user directory).
Broken after update? Try disabling and re-enabling the skill, or reinstall a specific version: openclaw skills install <skill-id>@<version>. If Node or deps changed, upgrade the runtime accordingly.
Conflicts or duplicate implementations? Avoid installing multiple skills for the same capability; keep one and disable the rest; if conflicting, check logs or temporarily move skills out of the skills directory to isolate.
Conclusion: Once you extend OpenClaw with the skill marketplace, search, notifications, docs, and messaging can be done directly in chat. If you run OpenClaw on local Windows, Linux or your own VPS, you often hit dependency, permission, network or display limits, and skill install and debugging can be costly. Using a rented VNCMac remote Mac and running OpenClaw in the VNC desktop gives you a ready Mac for skill installs, OAuth flows and browser-based skills, with fewer environment surprises. For deployment and troubleshooting see our OpenClaw blog posts; for nodes and plans see the homepage or purchase page.