2026 Must-Have OpenClaw Skills: The Most Complete List and Install Priority

2. What OpenClaw Skills actually are

Skills are not a casual plugin list. They are capability packs that tell the agent how to call external tools, services, browsers, files, and automation flows when a matching task appears. Each skill ships with SKILL.md (and optional manifest/install scripts) describing triggers, steps, and CLI/API dependencies. The gateway loads that guidance on demand instead of stuffing every tool manual into the system prompt.

• Sources: bundled built-ins, the ClawHub registry, git:owner/repo, or local ./path.
• Scope: default install target is the active agent workspace <workspace>/skills/; --global writes to the shared directory (default ~/.openclaw/skills) unless narrowed with agents.list[].skills.
• Load order (simplified): workspace /skills → project/personal agents dirs → ~/.openclaw/skills → bundled → skills.load.extraDirs (see Skills config).
• vs Channels / Cron: Channels are message ingress; Cron is scheduled triggers; Skills are “how to finish this kind of task with tools.”

Installing more skills does not automatically strengthen the gateway—disabled or allowlisted-out skills never reach the prompt. A misplaced high-permission skill in the wrong workspace can still read files, call outbound networks, or drive a logged-in browser when triggered.

3. Commands you need before installing anything

The table below follows the openclaw skills CLI reference (checked 2026-05-29). If subcommands change, run openclaw skills --help. Do not copy stale slugs—search, then verify/inspect, then install.

Note: the official CLI docs do not expose a dedicated uninstall subcommand. Uninstall = delete the install directory + set enabled: false + tighten agent allowlists. If a skill does not appear in chat after install, open a new Gateway session or confirm skills.load.watch refreshed the snapshot.

4. Bundled skills you should verify first

These are capability directions; exact bundled names on your machine come from openclaw skills list --verbose. On a new environment, step one is not “install more”—it is confirming these show ready in openclaw skills check:

If bundled skills are off via skills.allowBundled or entries.*.enabled: false, re-enable them before adding ClawHub extensions. Path/snapshot issues: see our Workspace Skills loading runbook.

5. External skills to prioritize on a new 2026 environment

ClawHub slugs, maintainers, and verify policies change—this table lists directions only. Workflow: openclaw skills search … → clawhub inspect / openclaw skills verify → install (confirm the current slug on install day; do not hard-code examples from this post).

6. Scene bundles: which group fits your work

7. Skills you should not install blindly

These belong in tier ④ by default—not banned, but requiring inspect, source review, and least privilege, and only for authorized, compliant use:

• High-privilege shell / DevOps / cloud: can run destructive commands or change production; use isolated agents and minimal IAM.
• Browser login state: cookies may persist in profiles; do not automate banking, mail, or social accounts without clear boundaries.
• Full mailbox / social APIs: fine for low-frequency personal assist—not for spam or bypassing platform limits.
• Payments / password managers / production repo write: avoid on a 24/7 primary gateway unless you have audit and review workflows.
• Third-party “one-click skill packs”: collections with hundreds or thousands of entries are for test environments—unpack and verify one by one, not for dumping into ~/.openclaw/skills on a production Mac.
• Offensive red-team / jailbreak kits: authorized test labs only; never point at third-party services without permission.

8. My 2026 Top 20 (capability directions, not fixed slugs)

Order balances beginner usability, developer throughput, content research, office automation, browser power, security boundaries, and long-term maintenance. Always search + verify before install—this is not an official ranking.

Reference numbers you can track: ClawHub’s public catalog grows with the community (check the site on install day); aim for ≤ 5 external ClawHub skills on a new gateway, expand after ~2 stable weeks; keep separate workspaces for production vs experiment agents.

9. Why “complete lists” mislead you

1. Constraint: bigger lists feel like “install everything.” Community READMEs treat GitHub stars as proof you need Obsidian or browser automation—even when your workflow does not.
2. Hidden cost: audit surface. Every skill that can read mail, post to channels, or drive a browser is another accidental trigger—worse on a 24/7 gateway.
3. Stability: install without maintenance. Skipping check / update, keeping dead high-permission skills, and never tightening allowlists leads to breakage after OpenClaw upgrades.

10. Seven-step path you can run today

1. Accept the gateway itself: if OpenClaw is not installed yet, follow our Mac install guide and clear fatal items in openclaw doctor.
2. List local skills: openclaw skills list and openclaw skills check against section 4.
3. Pick one scene row: from section 6—add only 2–3 external directions.
4. Review each candidate: openclaw skills search … → clawhub inspect <slug> --file SKILL.md → openclaw skills verify <slug> using the section 7 checklist.
5. Install and trial in isolation: openclaw skills install <slug> (skip --global unless you truly need sharing); use a test workspace, not production repos.
6. New session check: restart Gateway or start a new agent session; confirm visibility with check --agent.
7. Log maintenance: record slug, date, permission tier; weekly list, monthly update --all.

11. Post-install maintenance

• Update on a schedule: openclaw skills update --all (back up ~/.openclaw/openclaw.json and workspaces before major bumps).
• Disable before delete when unsure: skills.entries.<name>.enabled: false.
• Remove unused high-permission skills: delete skills/<slug>/ and trim agent allowlists.
• Ship your real workflows: use install ./my-skill or the official “Creating skills” flow instead of hoarding ClawHub trending items.