OpenClaw skills compared means checking five free add-ons — QMD, GOG, Brave Search, Humanizer and Mission Control — against what they actually need and what they expose. The useful question is not which one is strongest, but which ones can coexist, which require your own credentials, and which only pay off on top of the others.
OpenClaw Skills Compared: What Each One Actually Adds
OpenClaw skills compared on role rather than popularity: QMD indexes your own files, GOG connects Google Workspace, Brave Search adds live web results, Humanizer rewrites AI-sounding drafts, and Mission Control combines what the other four produce. Each fills a different gap, and none of them substitutes for another.
In OpenClaw, a skill is a package of instructions that teaches the agent a new capability, and installed skills can be invoked automatically when the agent decides they are relevant. That automatic selection is the part most walkthroughs skip, because it means you are granting standing behaviour, not issuing a one-time command.
The comparison below uses only what each skill's own documentation states about requirements. It does not rank them by the download figures circulating in promotional videos, because marketplace counters change and are not verified here.
| Skill | Role | Setup requirement | Cost basis | Main limitation |
|---|---|---|---|---|
| QMD | Search across local files | Point it at folders to index | Self-hosted search | Only sees folders you add |
| GOG | Google Workspace access | Google OAuth consent | Free skill; Google account needed | Access scope you approve |
| Brave Search | Live web results | Brave Search API key | Vendor-reported free credit tier | Stops when credit is exhausted |
| Humanizer | Rewrites AI-sounding text | Install and set mode | Free skill | Editing aid, not a detector of truth |
| Mission Control | Daily briefing | Depends on the skills above | Free skill | Value depends on those integrations |
What QMD Does and Where It Runs
QMD turns a folder of notes, transcripts or documents into a searchable index the agent can query, and it is built around QMD, the local search tool that the skill wraps. The practical effect is that a question about a past meeting gets answered from your files instead of from general model knowledge.
The design is deliberately layered: keyword matching for exact terms, semantic matching for meaning, and a re-ranking stage that orders what the first two passes returned. Multi-stage retrieval of that shape is a standard pattern, and it is what makes a folder index more useful than a single similarity search.
Local execution is the part that matters for sensitive material. If the index, the embeddings and the search all run on your own machine, your documents are not sent to a third party for retrieval, which is a meaningfully different posture from uploading files to a hosted assistant.
That is a technical property, not a compliance certificate. Local indexing does not by itself make a workflow suitable for regulated data, because the agent, the model endpoint and the surrounding application still have their own trust boundaries that you have to examine separately.
How GOG Connects Gmail, Calendar and Drive
GOG is the skill that links an agent to Gmail, Google Calendar, Google Drive, Sheets and Docs through Google Workspace account authorisation, so inbox triage, file lookup and spreadsheet reads happen inside the agent rather than in five browser tabs. Setup is an OAuth consent flow rather than an API key paste.
Two workflows dominate descriptions of it. The first is inbox review, where the agent reports what needs a reply. The second is document retrieval, where you describe a file instead of remembering its name and the agent locates and summarises it.
A spreadsheet read-and-write example is worth reading carefully. Asking an agent to pull revenue figures from one sheet into another works, but any workflow that moves financial numbers between live documents deserves a human check before the result is trusted.
The scope you grant at consent time is the real boundary here. Broad Workspace access is convenient and also the reason this is the skill most worth reviewing before you install it on an account that holds anything you would not want summarised.
Brave Search Gives the Agent Live Web Results
Brave Search connects the agent to live web results through the Brave Search API, which is what separates an agent that answers from training data from one that can read current pages. Without a search integration, a question about this week's news typically produces a guess or a refusal.
Videos about this setup describe a free monthly credit sufficient for a large number of queries because each query costs a fraction of a cent. Treat that as vendor-reported pricing that changes; the Brave Search API pricing page is the only place where the current allowance and per-query rates should be read.
The account mechanics matter more than the credit amount. Signup has historically required card details, and the protective step is setting a hard usage cap in the account so requests stop when the free allowance is consumed rather than continuing on a billable basis.
Once credentials are in place, the agent can compare two products, read the top results and return a summary with source links. Verification still sits with you, because search results are inputs, not evidence that a claim is true.
Humanizer and What Burstiness Actually Measures
Humanizer rewrites text that reads as machine-generated by flagging repeated structures and offering a revision pass. It is an editing aid layered on top of your agent's writing, not part of retrieval or search, so it changes output quality rather than what the agent knows.
The mechanism described in walkthroughs is statistical: burstiness, meaning how much sentence length varies across a passage, plus vocabulary diversity and phrase repetition. Those are real properties of text, and uniform sentence rhythm is one of the most visible signatures of generated prose.
A before-and-after score is the usual demonstration, with a draft scoring high for AI-likeness and a revision landing in a human range. The score is an internal metric of that skill, so it should be described as such rather than as an independent verdict on authorship.
Style scoring is probabilistic and criticised on both sides: detectors over-flag formal human writing and miss lightly edited machine text. Use the rewrite pass to improve how a draft reads, and do not treat a number as proof of who or what wrote something.
Mission Control Is Only as Good as Its Inputs
Mission Control assembles tasks, calendar items and inbox highlights into one briefing, and regenerates it on request when the day changes. Its output depends entirely on the other integrations, which is why it is the last skill to install rather than the first.
The stacking argument is straightforward and easy to verify in practice. With GOG supplying inbox summaries, Brave supplying current news and Humanizer cleaning the drafted text, the briefing covers more ground and reads better than any single skill could produce alone.
The cost is dependency. A briefing that merges email, calendar and web results is only as current as the weakest integration, and a revoked token or expired search allowance degrades the whole output rather than one section of it.
A time-saving claim is also a personal measurement. Replacing a morning triage routine that took roughly half an hour is plausible for someone with a busy inbox, and it remains that person's own experience rather than a general result.
Setup Order, Cost and Safety Checks Before You Install
Install in dependency order and test each layer before adding the next, because a fault in an early integration is hard to isolate once a briefing combines five sources. This sequence is the one that keeps failures attributable:
- Install QMD and index one small folder first. Confirm a fact you know is in a specific file comes back with the right context before pointing it at everything you own.
- Connect GOG and review the consent screen. Approve the narrowest scope that still supports your workflow, then test one inbox query and one document lookup.
- Set up Brave Search with a usage cap before the first query. Creating the key and configuring the limit first prevents an accidental billable request.
- Install Humanizer and run it on one existing draft. Compare the revision to your own writing rather than trusting the score alone.
- Add Mission Control last, once the four inputs return correct results on their own.
Three checks belong outside the install flow. Read the publisher page for each skill rather than relying on download counts, since popularity is not a safety review. Once a skill is active, confirm it still returns the same result a week later, because expired credentials fail quietly. And use the GDELT Project or another independent index when you need to verify that a search-driven summary reflects what actually happened.
What This Stack Does Not Guarantee
Installing these skills does not produce a compliant, private or fully automated assistant. It produces an assistant with more reach, more dependencies and a wider surface you are responsible for securing.
Among the items the original walkthrough treats as settled are notes on contributor roles and download counts that are not confirmed by canonical sources here, so they are excluded rather than repeated. Device and integration assumptions fall in the same category.
Privacy claims need the same care. Local indexing keeps documents on your machine, but the agent still talks to whatever model endpoint you configured, and GOG hands Google-adjacent data to the agent's context. Those are separate trust decisions, not one promise.
A practical rule: adopt one skill, use it for a week, and keep it only if you can describe precisely what it accessed and what it changed. That standard is stricter than a marketplace filter and it holds up better.
FAQ: OpenClaw Skills Compared
- Are OpenClaw skills free to install?
The skills themselves are distributed at no cost on ClawHub, but two dependencies are not free in the sense people assume. Brave Search requires an API key with a vendor-reported free credit tier, and GOG requires a Google account and OAuth consent. Budgeting time for setup matters more than the price.
- Does QMD send my notes to a server?
QMD is built around local indexing, so search runs against files on your machine. That covers retrieval only. The agent still sends context to whatever model endpoint you have configured, so local indexing and end-to-end privacy are different claims.
- What is a community-sourced account of mission control?
Dev Doido do canal do youtube is the kind of community-sourced account worth checking alongside vendor documentation, since independent walkthroughs often surface setup friction that promotional videos skip.
- Do I need coding experience?
No. Installation is done through chat commands and account signups, and the configuration is pointing skills at folders or approving access. Debugging a failed integration does reward some willingness to read error output.
- How much time does setup take?
Each individual skill is described as taking a few minutes. Budget more for the whole sequence, because verification after each step is what prevents a combined briefing from hiding a broken link in the chain.
Fork this article
Start a new branch from the same video, shaped your way. You keep the credit; the original keeps the attribution.
A fork in another language is filed as a translation of this article, so the two pages point at each other. You can unlink it later from the editor.
0/240
You are creating
- Format
- For
- Language
- Source
- Your angle
You will be asked to sign in before it is generated.
Buy credits