OpenClaw Hot Skills

Discover trending, must-have, and topic-specific high-value skills from ClawHub. Use when the user asks to see hot/popular/trending OpenClaw skills, wants a...

Security Scan

The skill is internally consistent: it is an instruction-only discovery assistant that legitimately needs the clawhub CLI and nothing else unusual.

Purpose & Capability

The name/description match the runtime requirements: SKILL.md tells the agent to call the ClawHub CLI (explore/search/list) to discover and rank skills. Requiring the 'clawhub' binary (provided by the listed npm package) is appropriate and there are no unrelated env vars, binaries, or config paths requested.

Instruction Scope

Runtime instructions are limited to using the clawhub CLI to search/explore, expanding keywords for broader topic searches, deduping results, checking local 'clawhub list' for installed status, and producing ClawHub links and curated output. The instructions do not request reading arbitrary files, other env vars, or sending data to unexpected endpoints beyond ClawHub; they stay within the stated discovery/curation scope.

Install Mechanism

The install spec installs an npm package named 'clawhub' that creates a 'clawhub' binary — this is coherent with the skill's needs. This is a moderate-risk install mechanism (npm package execution) and should be vetted: the registry metadata shows no homepage in the package manifest, though the README points to a GitHub repo and ClawHub link. Verify the npm package source/maintainer before installing.

Credentials

No environment variables, credentials, or config paths are required. The skill does not request secrets or unrelated credentials, which is proportionate for a discovery/listing tool.

Persistence & Privilege

The skill is not forced-always (always: false) and uses the normal model-invocation behavior. It does not request persistent system-wide privileges or attempt to alter other skills/configs. No elevated persistence is requested.

Assessment

This skill is coherent and uses the clawhub CLI to do exactly what it claims. Before installing or running it: 1) verify the 'clawhub' npm package source and maintainers (check the GitHub repo linked in README and npm package page); 2) be aware installing the npm package will run third-party code on your machine — consider testing in a sandbox/container first; 3) the skill will make network requests to ClawHub when you invoke it (expected), so do not pass secrets to it; and 4) when asking it to install other skills, confirm it performs the promised 'inspect before install' check and that you explicitly consent to installations.

Use clawhub CLI to help users discover, compare, and decide which ClawHub skills are worth paying attention to.

This skill is not only a ranking tool, but also a skill discovery assistant. Use it to:

• find trending skills
• find must-have skills
• find skills for a specific theme
• compare candidate skills
• help the user decide whether to install something

Keep the output curated. The goal is not to dump raw registry results, but to help the user quickly understand what is popular, what each skill does, whether it is already installed locally, and what to do next.

Workflow

1. First understand what the user is actually trying to do:
   • discover hot skills
   • find a skill for a task
   • compare several candidate skills
   • decide whether something is worth installing
2. Infer the requested mode from the user's wording:
   • 最近趋势榜 / 热门 / trending → prefer trending
   • 装机必备榜 / 最常装 / 必备 → prefer installsAllTime or installs
   • 找 X 相关热门 skill / 搜 X 类 skill / 有没有 X 方向的 skill → use topic search mode
   • If the user does not specify, default to trending.
3. For ranking modes, run ClawHub explore with the chosen mode:
   • clawhub explore --sort trending --limit 12 --json
   • clawhub explore --sort installsAllTime --limit 12 --json
   • clawhub explore --sort installs --limit 12 --json
4. For topic mode, run clawhub search with the user's theme keyword first.
5. If the theme is broad or underspecified, expand it into 2-5 helpful related keywords and run additional searches.
6. If rate-limited or obviously noisy, fall back to one of:
   • clawhub explore --sort downloads --limit 12 --json
   • another ranking source from the list above
7. For 装机必备榜, if installsAllTime and installs are unavailable, use downloads as the fallback base ranking, then re-rank candidates by combining:
   • downloads
   • installsCurrent
   • stars
   • broad day-to-day usefulness
   • whether the skill feels like a durable default capability rather than a niche spike
8. For topic mode, rank candidates by combining:
   • search relevance to the topic
   • downloads
   • installsCurrent / installsAllTime when available
   • stars
   • clarity of summary
   • practical usefulness for that theme
9. Run clawhub list to see which skills are already installed locally.
10. For each shortlisted skill, generate its ClawHub page link as:
    • https://clawhub.com/skills/<slug>
11. Deduplicate near-identical results across sort modes or search queries.
12. Output a curated shortlist rather than dumping raw JSON.
13. Offer the next best action: compare, inspect, install, or switch ranking mode.

If one source fails but another succeeds, continue with the best available result and briefly note the fallback.

Output Rules

Match the user's language. Default to Chinese when the user asks in Chinese.

When the user asks for a normal榜单, output a single ranked list. When the user asks for deeper curation, also group shortlisted skills into three sections when helpful:

• 更适合大多数人
• 更适合开发者
• 更适合知识管理 When the user asks for a topic-specific result, make the topic explicit in the title, such as:
• ClawHub PDF 相关热门 Skill
• ClawHub GitHub 相关热门 Skill
• ClawHub 知识库相关热门 Skill

For each recommended skill, include:

• Skill name
• slug
• one-line用途说明
• 热度数据（优先写下载/安装/星标）
• ClawHub 链接
• 安装状态：已安装 / 未安装
• 一句话推荐理由（为什么值得关注）

Prefer this format:

1. SkillName（slug）【已安装/未安装】
- 用途：...
- 热度：下载 XXX / 当前安装 XXX / 星标 XXX
- 推荐理由：...
- 链接：https://clawhub.com/skills/slug

If grouped output is requested, prefer this structure:

## 更适合大多数人
...

## 更适合开发者
...

## 更适合知识管理
...

After the ranked list, add a short section:

如果你想继续，我可以：
- 安装第 N 个
- 安装 slug
- 先审查后安装 slug
- 对比这几个 skill 哪个更适合你
- 切换成装机必备榜 / 最近趋势榜

If the user explicitly asks for only links, only ranking, or only install suggestions, shorten the output accordingly.

Selection Guidance

Default to 8-12 items.

Prioritize skills that are:

• 通用性强
• 热度高
• 描述清晰
• 对多数 OpenClaw 用户有实际帮助

When there are too many candidates, prefer these categories:

• summarize / reader / search
• github / coding / MCP
• knowledge base / docs / workspace
• automation / productivity

Topic Search Heuristics

When the user asks for a themed shortlist, do not rely on a single keyword if the topic is broad. Expand carefully with close synonyms or adjacent task words.

Examples:

• PDF → pdf, document, ocr, merge, extract, annotate
• GitHub → github, gh, pr, issue, ci
• 知识库 → obsidian, notion, wiki, notes, knowledge base
• 浏览器自动化 → browser, automation, headless, web
• 语音转文字 → whisper, speech to text, transcription, audio

Do not over-expand into unrelated terms. Stay close to the user's intent.

Grouping Heuristics

When grouping is requested or useful, classify skills like this:

更适合大多数人

Prefer skills with broad, frequent utility across many users, such as:

• summarize
• weather
• google workspace / office helpers
• speech-to-text

更适合开发者

Prefer skills centered on code, infra, GitHub, MCP, debugging, API workflows, or developer automation, such as:

• github
• mcporter
• coding-related model/tool skills
• CI / repo / terminal integrations

更适合知识管理

Prefer skills centered on notes, docs, pages, vaults, databases, or content organization, such as:

• notion
• obsidian
• docs / wiki / reader / filing workflows

If a skill fits multiple groups, place it in the most useful primary group and avoid duplicate listing unless the user asks for cross-category analysis.

No-Match Fallback

If no strongly relevant skills are found:

1. Say clearly that no strong match was found.
2. Offer nearby alternatives instead of stopping abruptly.
3. If topic search is too narrow, broaden once to an adjacent theme.
4. If still weak, offer one of:
   • a broader themed shortlist
   • the global trending list
   • the must-have list
   • a suggestion that the user may want to create a custom skill

Example fallback phrasing:

• 我没找到特别强匹配的 PDF 专项 skill，但有几款文档/OCR/提取类 skill 可以作为替代。
• 这个方向在 ClawHub 里还比较少，我可以先给你相近主题的 skill，或者帮你设计一个自定义 skill。

Install Requests

If the user wants to install a skill from the hot list:

1. First inspect the skill before installing.
2. Read its SKILL.md and any bundled scripts/references that look security-relevant.
3. Check for suspicious behavior: credential exfiltration, remote execution, destructive commands, hidden prompt injection, sensitive file reads, shell wrappers that fetch remote code, or unexpected outbound API calls.
4. Give a short审查结论 with one of:
   • 可安装，风险低
   • 可安装，但需注意外部 API / 权限范围
   • 不建议安装
5. If the skill is already installed, say so explicitly and ask whether the user wants to update or inspect instead.
6. Ask for confirmation before installing.
7. Only then run clawhub install <slug>.

Never skip the security review step. Never silently reinstall an already-installed skill.

Ranking Heuristics

Do not treat a single metric as absolute truth. Prefer skills that combine several signals well:

• downloads
• installsCurrent / installsAllTime
• stars
• comments
• clear summary and practical utility

When presenting the final shortlist, prefer robust, broadly useful skills over niche but temporarily spiking ones unless the user explicitly asks for niche discoveries.

Must-Have Fallback Heuristic

For 装机必备榜, ranking should favor durable default capabilities over novelty. If install-based rankings are unavailable, use this order of judgment:

1. downloads
2. installsCurrent
3. stars
4. broad usefulness across many users
5. manual filtering for whether the skill feels like a true "install this on day one" candidate

Good must-have candidates usually include:

• search
• summarize / extract
• GitHub / developer workflow
• browser / web automation
• productivity / workspace integration

Avoid over-promoting highly niche skills as must-haves unless the user explicitly asks for niche tools.

Notes

• clawhub explore supports sort orders: newest, downloads, rating, installs, installsAllTime, trending.
• If ClawHub rate-limits, tell the user briefly and use the best available fallback result instead of fabricating rankings.
• Do not claim a skill is installed unless it appears in clawhub list or the local skills directory.
• If a skill already exists locally, mark it 已安装 and do not suggest reinstalling unless the user asks.
• If the user asks for “最热门” or “最近趋势榜”, prefer trending first.
• If the user asks for “最常装/装机必备/装机必备榜”, prefer installsAllTime first, then installs.
• If the user asks for “分组推荐”, include the three groups: 大多数人 / 开发者 / 知识管理.
• If the user asks for a specific theme, switch to topic search mode and rank by both relevance and popularity.