Practical Review: 3 Essential Clawhub Skills and 3 to Avoid

This review comes from a developer who tested Clawhub skills individually over several weeks, installing each one, monitoring token usage, reading source code, and deciding whether to keep them. Most skills weren't worth keeping due to unreliability, silent token burning, or redundancy with existing agent capabilities.

Skills Worth Installing

1. web-search (Brave)

This skill is considered essential because without it, agents can only answer from memory, leading to confidently wrong answers about recent information. It works well because the actual search happens outside the model—Brave's API performs the lookup, and only results are fed back into context, keeping token costs minimal per search.

Setup requires getting a Brave API key (free tier suffices for personal use), then installing the skill. The only noted issue is occasional garbage results for very specific or niche queries, which is attributed to Brave rather than the skill itself.

2. daily-brief

This skill transforms OpenClaw from a chatbot into an actual assistant by providing a morning summary of calendar, weather, tasks, or other configured items. It runs once daily via cron, making one API call and one response, resulting in low token costs for a single focused task.

The key recommendation is to customize it heavily during the first week, as default output tends to be too verbose. Adding a SOUL.md line like "morning briefings should be under 200 words. bullet points. no preamble." makes a significant difference.

3. memory-search

This skill becomes essential after the first month as memory files grow. Without it, agents read memory files top-to-bottom and miss information buried in the middle. Memory-search adds semantic search capability to find relevant context instead of relying on positional luck.

It solves a problem that worsens over time—long-term users eventually encounter "my agent forgot everything," which actually means "my agent can't find anything in 50 pages of memory." Installation is recommended around weeks 3-4, once enough memory has accumulated for it to matter.

Skills Not Worth Installing

1. food-order

Despite being a popular demo skill, it fails on most delivery sites due to Cloudflare, dynamic JavaScript, CAPTCHAs, or login walls. Even when it works once, it breaks with subsequent site UI updates. Testing over four days resulted in zero successful orders, with two close attempts failing at checkout.

It burns tokens on every failed attempt as it tries different approaches. The practical alternative: opening the food app directly takes about 30 seconds and doesn't waste tokens.

2. multi-agent orchestrator skills

Three different orchestrator skills were tested, all adding a management layer where one agent reads messages, decides which worker agent should handle tasks, passes tasks, reads results, and summarizes back. This requires four LLM calls for what a single agent handles in one.

The token math: a simple question costing $0.002 with one agent costs $0.008+ with an orchestrator. Multiplied across daily messages and monthly usage, this adds significant cost for a middleman that increases latency and complexity without improving quality for most tasks. The recommendation: if you can't explain why agents need separate memory and permissions, you don't need an orchestrator—just message the right agent directly.

3. humanizer

This skill injects personality instructions into agent behavior but causes problems like agents responding to "set a reminder for 3pm" with overly casual language like "yooo absolutely fam, got you locked in, that reminder is SET no cap." One user described it as "talking to a teenager that just learned new slang and needed to overuse it."

The issue is that it overrides SOUL.md personality settings globally, adding filler and flavor even when straightforward answers are desired, while charging tokens for every extra word. The free alternative: write five lines in your SOUL.md like "be direct, match my tone, no filler," which takes two minutes, costs zero tokens per message, and provides complete control.

The Pattern

Good skills do one specific thing cheaply and stay out of the way. Bad skills add layers between users and agents—orchestrator layers, personality layers, or browser automation layers for tasks that don't need them. Each added layer means paying tokens on every message. The best setups run 3-5 skills total, with each one earning its place through demonstrated utility.