Best OpenClaw Skills to Install First (2026): Starter Packs by Workflow

The best OpenClaw skills to install first depend on the work you want finished. For long articles and PDFs, consider summarize. For Gmail and Calendar together, consider gog. For issues, pull requests, and CI status, consider github. Each is a concrete starting point with a different dependency and account setup—not a universal pack you need to install together.

For ordinary web research, first check the existing web_search and web_fetch tools. For interactive websites, check the browser plugin and its bundled browser-automation skill. Downloading a community skill named “web search” or “browser” is not automatically necessary. The official web documentation and browser documentation distinguish these capabilities.

Choose one recurring job, make its prerequisites work on the machine that actually runs it, and ask for one result you can verify. That gives you a useful starter pack without turning the first week into integration maintenance.

The Fast Answer: What Should You Install First?

Start with this table. “First choice” means a capability to inspect and prepare; a bundled skill may already be present in your installation.

These choices come from the official bundled skill sources and the tool documentation. They are workflow recommendations, not download rankings or performance measurements. The command syntax and prerequisites below were checked against official materials on October 8, 2026; your installed release may differ.

The Best OpenClaw Starter Bundles by Workflow

A good starter bundle has a reason for every component. Add the second component when it solves a specific remaining step, rather than because a list labels it essential.

Research: use the web tools, then add summarize when extraction is the bottleneck

For a short readable page, an agent with web_fetch may already have enough to answer your question. For discovering sources, it needs a working search route. The Control UI's Settings → Search shows the effective route for the selected agent and model. A provider marked Configured has setup information; that label does not prove a successful search. The documented Test search action exercises a managed provider and uses its normal account limits and billing. Source: Web search.

Add summarize when your recurring inputs are long URLs, PDFs, local files, or videos. Its bundled skill requires the summarize binary. Summary generation also needs the selected model provider's credentials; --extract prints extracted content without asking an LLM to summarize it. Video transcript extraction is best effort, and optional fallback services have their own requirements. Source: summarize skill.

For example, suppose you regularly compare two equipment manuals. Give the agent the two files and ask for differences in operating temperature, power requirements, and warranty exclusions, with a page reference for each answer. The first useful result is a source-backed comparison. If a PDF fails extraction, that is a reason to fix the input path—not to add an unrelated research skill. If both short documents are already readable, the extra CLI may provide little first-day value.

Assistant tasks: choose gog for Google Workspace, Himalaya for IMAP mail

gog is a sensible first choice when the job crosses Gmail, Calendar, Drive, Docs, or Sheets. It requires the gog binary and OAuth setup. It is the Google Workspace integration described by this particular skill; it should not be confused with a generic calendar skill or a different Google CLI. Source: gog skill.

Start with a limited read task such as locating correspondence for a project and its next scheduled appointment. Include the account, date range, and time zone. Check the returned message identifiers and event times against the originals before asking the agent to draft a response. Sending mail and creating events are separate actions with separate consequences.

One detail changes the result: gog gmail search returns threads, while gog gmail messages search returns individual emails. A report of every matching message needs the latter, plus any necessary pagination; a thread list alone does not prove complete message coverage. On a remote Gateway, the account must be usable from that execution environment. Completing an authorization page on your laptop does not by itself establish that the Gateway has a stored, usable token. Keep passwords, secrets, and authorization callback URLs out of chat. Source: gog authentication and search notes.

For an existing IMAP/SMTP mailbox outside that workflow, inspect himalaya instead. Its skill requires the himalaya binary and configured mail accounts. It supports reading as well as composing, moving, and deleting messages, so decide which actions the task actually needs. Installing both mail integrations usually adds setup work before it adds useful coverage. Source: Himalaya skill.

Developer workflows: start with repository state, then decide whether you need a coding agent

github is useful for issues, PR metadata, diffs, check logs, and repository queries through gh. It requires the gh binary; authenticated access to the right repository is an additional practical prerequisite. The official skill distinguishes GitHub operations from local git work and deeper code reading. Source: github skill.

For a first task, choose one existing PR and ask which checks prevent it from landing, with the check names and their URLs. Verify that the answer uses current status, identifies unfinished checks separately from failed checks, and refers to the intended PR. A plausible explanation without the actual checks is not a successful repository task.

If you need code changes rather than repository status, that is a different requirement. Current documentation describes the bundled coding-agent as opt-in and dependent on an installed, authenticated supported coding CLI. A ready github skill does not supply that runtime, and a skill called code-reviewer in someone else's starter list does not establish compatibility with your installation. Inspect the capability you actually intend to use before combining it with GitHub. Source: Skills configuration overrides.

Web scraping and product listings: inspect the browser before adding a scraping skill

For readable HTML, try web_fetch. For content rendered by JavaScript or a task requiring page interaction, use the browser capability. The current browser plugin includes a browser-automation skill when enabled; the skill teaches the agent how to use that browser. The managed openclaw profile is separate from your personal browser, while the built-in user profile attaches to real signed-in Chrome. Pick the profile that fits the authorized task. Sources: Web search, Browser profiles and capabilities.

Here is a small illustrative acceptance task for a product-listing workflow. Provide two public listing URLs and ask the agent to capture the first three visible products from each. Request these columns: source URL, product name, displayed price, currency, availability text, and retrieval time. Tell it to leave an absent field empty and to stop at a login or access challenge.

Then check the six rows against the pages. A useful result preserves the displayed currency, does not turn “from $20” into an exact $20 price, and does not count the same product twice because two page elements repeat it. If only two products are visible on one page, the answer should explain the smaller result instead of inventing a third. These are acceptance criteria for your trial, not results from a scraping test performed for this article.

Only seek a specialist skill after identifying the missing step—for example, a repeatable export format or a site-specific extraction procedure. Its instructions cannot create browser access, account authorization, or permission to ignore a website's restrictions.

Support, knowledge, and recurring updates: start with the sources you can actually read

A support workflow needs relevant source material before it needs ticket-writing access. Start by asking the agent to answer a sample question from an accessible policy document, quote the supporting passage, and identify what the document does not settle. Adding a generic kb-search or ticketing name from a list does not prove access to your knowledge base or help desk.

If your source material lives in Obsidian, the current bundled obsidian skill uses the official obsidian CLI. Its documented prerequisites include Obsidian 1.12.7 or later, the CLI enabled in Settings, the binary on PATH, and the app running. Plain Markdown vault files can also be handled with existing file tools when that is appropriate. A headless host without the app is therefore a materially different setup from a desktop vault. Source: Obsidian skill.

For recurring public-source updates, blogwatcher is a narrower choice. It tracks blogs and RSS/Atom feeds through its CLI, with commands to scan for entries and manage local read status. Use it to discover new entries, then add summarize if reviewing their full content is the next bottleneck. It is not a promise to extract every news site or paywalled article. Source: blogwatcher skill.

Check What Your Agent Can Use Before Installing More

OpenClaw skills are directories containing SKILL.md instructions, with optional supporting files. OpenClaw can discover a skill while still excluding it because of missing dependencies, configuration, platform requirements, or the selected agent's filters. A skill file does not grant account or tool access. Source: Skills.

On a working OpenClaw installation, use the current plural skills commands to inspect the setup:

openclaw skills list
openclaw skills list --eligible
openclaw skills list --verbose
openclaw skills info github
openclaw skills check

Replace github with the actual candidate you chose. For a particular agent, use openclaw skills check --agent <id>, replacing <id> with its configured identifier. The CLI reference separates three questions:

For a configured remote Gateway, these commands request that Gateway's inventory. A connection or authentication error does not silently become a check of your laptop's skills. Resolve the connection first. For dependencies, check the actual execution host or node: finding gh or gog on the operator's laptop is insufficient if the work runs elsewhere. Sandbox execution can also require dependencies inside the sandbox. Sources: Skills CLI, Skills gating.

If the skill is present but disabled, the relevant setting is skills.entries.<name>.enabled; false disables it. An operator can set the intended entry to true in the existing configuration after reviewing the skill. Use its documented metadata key if it defines one. That toggle does not install its binary or authenticate its account. If an agent filter excludes it, review that filter with the operator rather than removing all restrictions. The skills.allowBundled setting applies only to bundled skills. Source: Configuration overrides.

After preparing a dependency, start a new session to recheck prerequisites. Ordinary skill-file changes can refresh through the watcher and take effect on the next turn; an existing session's dependency snapshot should not be assumed to update merely because a binary appeared. You can use the Control UI's $ picker to reference a skill available to the current agent explicitly. Source: Skill references and snapshots.

Install a Missing Skill with the Current Native CLI

If the needed bundled skill is already present, solve its reported prerequisites instead of installing another copy with the same name. Workspace and project skills take precedence over bundled skills, so a same-named install can change which instructions the agent reads. Confirm the winning source through the inventory and skill information. Source: Loading order.

For a genuinely missing community skill, the current documented route is search, inspect, and install an owner-qualified ClawHub reference. The following is a command pattern, not a recommendation for an existing publisher. Replace every placeholder with the exact skill and version you selected:

openclaw skills search "your task"
openclaw skills verify @owner/<slug> --version <version>
openclaw skills install @owner/<slug> --version <version>
openclaw skills info <name>
openclaw skills check --agent <id>

The default installation target is the active workspace's skills/ directory. --agent <id> targets one configured agent workspace; --global targets the shared managed skills directory and cannot be combined with --agent. Inspection commands report the selected Gateway's inventory, so confirm both the installation target and the agent you will use. Source: Skills CLI.

Git and local-directory installs are also supported, with a loadable SKILL.md at the source root. --version applies to ClawHub releases, not Git references, and openclaw skills update tracks ClawHub installs rather than unmanaged Git or local copies. The current native skill installer does not accept npm package specifications or zip paths. A dependency such as gog may have its own installation method; installing that binary and installing skill instructions are different steps. Source: Installation details.

If installation hits a 429 response, pause the installation and follow the documented retry behavior rather than repeating the command rapidly. Our OpenClaw 429 recovery guide distinguishes ClawHub installation limits from model-provider limits.

What Makes a Skill Worth Installing

Keep a skill when it closes a specific gap and you can verify its output. Before installing or updating a third-party candidate, read its actual instructions and supporting scripts, identify the publisher and release, and match its dependencies and requested actions to your job. A popularity count alone cannot answer those questions.

ClawHub verification is useful evidence with a defined limit: openclaw skills verify reads stored verification and scan information; it does not initiate a new scan. Full scanner reports may be unavailable or omitted. Community installation and updates check release trust, while official publishers and bundled sources bypass that particular check. A successful check therefore should not be described as proof that every skill is scanned, safe, or compatible with your environment. Source: Verification and release trust.

For your first task, keep the input small enough to inspect manually. Name the intended source, account or repository, time range, and output. Check whether the result came from those sources and whether the agent took any action beyond the request. If something fails, classify it: missing binary, inaccessible account, hidden skill, unavailable tool, or incorrect output. Add another skill only when it addresses that specific failure.

What You Should Not Install First

Skip broad packs whose components have no role in the task you picked. Also skip automatic improvement or workshop flows when your immediate need is a dependable first integration: changing instructions is another workflow to evaluate, not a prerequisite for reading a document or checking a PR.

Do not use force-install options to make an unresolved scan or policy problem disappear. Choose a release you can review, wait for the pending process, or select a different candidate. Likewise, do not enable every shell or account permission merely to turn a readiness report green. A declared prerequisite check and a useful, authorized result are separate milestones. Sources: Release trust, Skills security.

Your first pack is complete when it finishes the recurring job with an output you can check. Keep the working combination and expand from the next real limitation.

Frequently Asked Questions

What is the single best OpenClaw skill?

Choose summarize for recurring long-source reading, gog for Google Workspace tasks, or github for GitHub state. If your immediate job is ordinary web research, check existing web_search and web_fetch first; a new search skill may be unnecessary. The choice depends on the task and usable prerequisites, not a universal ranking. Sources: Bundled skills, Web tools.

How many skills should I install at the beginning?

Start with one recurring workflow. It might need one skill, a small combination, or no new installation if the necessary tools are already available. Add a component when you can name the step it solves and verify the resulting output.

Are skills and plugins the same thing?

No. A skill provides instructions for using capabilities; a plugin can provide capabilities and ship its own skills. For example, the browser plugin includes browser-automation when enabled. Installing skill instructions alone does not supply a missing browser tool. Source: Plugins and skills.

Why is an installed skill still missing from my agent?

Check openclaw skills check --agent <id> for the intended agent. The skill may lack a declared binary or configuration requirement, be disabled, be excluded by that agent's filter, or remain absent from an existing session snapshot. Check the selected Gateway and actual execution environment before reinstalling it. Sources: Skills CLI, Snapshots and refresh.

What is a low-setup skill for trying OpenClaw?

For a lightweight public-information task, consider the bundled weather skill. Its current instructions prefer web_fetch and use curl as a fallback, without requiring a separate weather API key. Ask for a forecast for a named city and check the location, date, and units. Network access still has to work, and this skill is not the right source for severe-weather alerts, aviation, marine decisions, or historical climate data. Source: weather skill.

Does a ready or verified skill mean the workflow works?

No. Readiness checks declared prerequisites; verification reports ClawHub's stored assessment. Neither proves that your account can access a resource or that the agent produced a correct result. Confirm the workflow with a small task and its original sources before increasing its scope. Source: Skills CLI.