These ten choices help you configure and use an OpenClaw personal assistant. They include owner tools, daily tasks, app integrations, and two community options whose SKILL.md files were source-checked.
Do not treat this list as a blanket installation checklist. Bundled skills may already be present in your existing OpenClaw setup. App and operating system integrations often require separate command-line tools, local permissions, or OAuth credentials. Third-party skills should always be inspected before enabling hooks or automated tasks.
Personal assistant focus. Covers daily tasks alongside the owner tools used to configure and maintain an OpenClaw personal assistant.
Bundled versus external boundaries. Separates skills in OpenClaw's repository from the external tools they may need and from community-maintained skills.
No blanket install advice. Every card highlights prerequisites. Check whether a bundled capability is already available on your machine before adding a duplicate copy, and verify required external CLI setup.
Third-party options. We checked the linked SKILL.md bodies, not every script or dependency. ClawSec's optional hook and scheduled checks require a separate review and decision.
Top 10 OpenClaw Skills at a glance
A comparative index of the top picks. Click any card to navigate directly to its detailed review.
Install counts approximate skills.sh detail-page snapshots from September 2026. First-party skills may already exist in your OpenClaw installation.
Bundled OpenClaw skills
These first-party skills ship in the OpenClaw repository. They are useful guidance for their named tasks, but do not assume every skill needs a separate install: check which skills and dependencies your OpenClaw setup already provides.
healthcheck
5.4K installs OpenClawBundled · OpenClaw health and security checks
Best for: Auditing an existing OpenClaw installation, its configuration, and host security posture
healthcheck starts with read-only inspection of the OpenClaw setup, configuration, and host security posture. Use that pass to understand the current state before making changes.
The documented `doctor` repair path can migrate state as well as fix configuration. Review proposed changes and back up important state before choosing repairs; this is not a blanket authorization to modify the host.
Best for: Creating or revising an OpenClaw skill with a focused scope and usable instructions
skill-creator guides authoring a skill directory and its SKILL.md: identify the task, keep instructions focused, and include supporting files only when they serve that workflow.
Validate the result with the source's `quick_validate.py` utility and test the skill against representative requests. Check whether this bundled skill is already present before adding a separate copy.
Best for: Discovering or managing skills through ClawHub as part of an OpenClaw workflow
clawhub guides use of the ClawHub registry to search for and inspect skills. Treat registry metadata as a starting point: review the selected skill's instructions and files before installing it.
Installing a registry skill adds third-party instructions or code to the agent environment. Check its publisher, contents, and requested capabilities first, and verify whether the ClawHub skill is already available in your OpenClaw setup.
Best for: Weather questions when the OpenClaw runtime has the needed network or service access
weather looks up current conditions from wttr.in using `web_fetch` and requests its `format=j2` JSON response. If `web_fetch` is unavailable or fails, the instructions use `curl` as a fallback.
For official severe-weather alerts, consult the relevant national or local meteorological authority: wttr.in is not an official alert service. Network access is required for live results.
These first-party skills target specific apps or operating systems. Pick them only when the relevant environment is present; using one may require a separate CLI, operating-system permission, OAuth flow, or API credentials.
Best for: Visual computer interaction on a configured macOS host with Peekaboo available
peekaboo connects OpenClaw to the Peekaboo CLI for visual interaction with macOS applications. It requires a macOS host, the separate `peekaboo` tool, and the relevant screen or accessibility permissions.
Only manipulate the UI when the user has explicitly permitted the requested action. Screen actions can affect accounts and local data; confirm the intended target and consequential changes rather than treating access as authorization.
Requires macOS and the separate `peekaboo` CLI
Configure the required screen and accessibility permissions
8.3K installs OpenClawConditional · Google Workspace via gog
Best for: Google account workflows in an environment where gog and its authorization are configured
gog documents workflows for the `gog` CLI across Google services including Gmail, Calendar, and Drive. Install and configure the CLI separately, then authorize the intended Google account with OAuth; this skill does not supply account access.
Mail, calendar, and Drive operations can read private information or make changes. Verify the active account and review the exact operation before sending, deleting, or modifying user data.
Gmail, Calendar, Drive, and other supported services
26.7K installs OpenClawConditional · Media and URL summarization
Best for: Summarizing URLs or supported media when the required extraction tools are installed
summarize uses the `summarize` CLI to process URLs, YouTube links, PDFs, and local files. Which inputs work depends on the installed extraction tools and the selected provider.
Provider use requires its API key to be configured separately. Submitting a URL, document, or local file to a remote provider sends that content to the provider; check the destination and data sensitivity first, and consult the original for important details.
CLI supports URLs, YouTube, PDFs, and local files
Input support depends on installed extraction tools
5.9K installs OpenClawConditional · Apple Reminders on macOS
Best for: Working with Apple Reminders on a configured macOS system
apple-reminders uses the separate `remindctl` command-line tool to work with Apple Reminders on macOS. It depends on macOS and the tool's access to Reminders; it is not a cross-platform task manager integration.
This integration works with reminders, not OpenClaw's own cron scheduler or cron alerts. Set up `remindctl` and grant the necessary macOS permission separately; confirm the target list and changes before modifying personal reminders.
Apple Reminders through `remindctl`
Requires macOS, separate CLI setup, and app permission
These entries are third-party projects, not bundled OpenClaw skills. Review the source and permissions before installing; ClawSec's optional hook and cron features are distinct from the workspace skill.
Best for: Users who have reviewed and chosen the win4r OpenClaw workspace conventions
openclaw-workspace is a community skill from win4r for working with OpenClaw workspace files, including instruction and memory files. Those files can contain sensitive, persistent guidance; inspect the repository's editing conventions and the target content before applying changes.
The source includes a bootstrap example that deletes itself after setup. Treat that as an explicit destructive file operation: understand the example and its target before running it.
Third-party workspace-file conventions
Instruction and memory files may contain sensitive content
Bootstrap example deletes itself after setup
Review file targets before applying workspace changes
858 installs Prompt SecurityThird-party · ClawSec security suite
Best for: Evaluating ClawSec security workflows after reviewing the third-party project source
clawsec-suite is a third-party security skill from Prompt Security, not part of OpenClaw's first-party bundle. Its workflow includes signed remote advisories and describes an optional hook installed under `~/.openclaw/hooks`; it also offers optional cron-based checks.
The setup uses a mutable `npx` package invocation. Installing or enabling it can execute third-party code in the OpenClaw host context; review the package, source, permissions, and current instructions, then explicitly approve any hook or cron setup. Do not assume every script has been audited or is safe.
Signed remote security advisories
Optional hook installed under `~/.openclaw/hooks`
Optional cron-based checks
Mutable `npx` package; inspect and explicitly approve execution
OpenClaw provides a versatile personal assistant foundation, but skills should be introduced deliberately based on what your environment actually supports.
1.Inspect your bundled tools first. Check whether healthcheck, skill-creator, clawhub, or weather are already available before installing additional copies.
2.Verify external CLI tools and permissions. Skills like peekaboo and apple-reminders require macOS and specific command-line utilities. Similarly, gog requires separate Google OAuth authorization, and summarize requires its separate CLI and a configured model provider.
3.Review third-party source and permissions. For community extensions like openclaw-workspace or clawsec-suite, inspect repository files and review workspace edits. ClawSec's optional hook and cron schedule need separate approval.
Bundled capabilities vs conditional integrations
These skills live in OpenClaw's repository and may already be in your installation. Health checks, skill authoring, ClawHub discovery, and weather lookups have different purposes; choose the one that matches your task and check its runtime requirements first.
In contrast, conditional integrations bridge OpenClaw into specific desktop apps, operating systems, or third-party web services. They rely on external CLI tools such as Peekaboo or remindctl, or require secure OAuth authentication to access personal mail and calendars. Only enable these integrations in environments where the underlying tools and permissions are already configured.
Managing community extensions safely
These community skills cover workspace guidance and security advisories. Their SKILL.md files were checked, but their scripts and dependencies were not audited. Treat any code they run according to the permissions of your OpenClaw host.
Review instruction files and workspace changes before acting. For ClawSec, also inspect its setup scripts and decide separately whether to enable the persistent hook or optional scheduled checks.
Manage your assistant skills with LazySkills
LazySkills scans installed skills, shows which agents can see them, diagnoses broken configurations, and searches the skills.sh registry used for this guide. Check what OpenClaw already provides before adding another skill.
No. The first eight entries link to SKILL.md files in the openclaw/openclaw repository; the final two are community projects from win4r and Prompt Security. Even for first-party skills, check your OpenClaw installation before installing separately because some may already be available.
Do these skills install their required tools or credentials?
Do not assume so. App-specific entries can require a separate CLI, OS permissions, OAuth authorization, API credentials, or provider configuration. Check each linked SKILL.md and your host setup; the install command adds the skill, not necessarily its external dependencies or account access.
Which entries are community extensions?
openclaw-workspace is from win4r/openclaw-workspace, and clawsec-suite is from prompt-security/clawsec. They are third-party projects, not first-party OpenClaw bundle entries. Review their source and any optional hooks or scheduled tasks before enabling them.
What do the install counts represent?
They are approximate skills.sh snapshot observations, not guarantees of current popularity or quality. The UI rounds the counts, and registry totals can change over time.
svgdiagram.ai 
