Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Find, evaluate, and recommend ClawHub skills by need with quality filtering and preference learning.
Find, evaluate, and recommend ClawHub skills by need with quality filtering and preference learning.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
User asks how to do something, wonders whether a skill exists, wants a new capability, or asks for the best skill for a job. Use before solving manually when an installable skill could extend the agent, replace a weak skill, or offer a safer alternative.
Memory lives in ~/skill-finder/. If ~/skill-finder/ does not exist or is empty, run setup.md. ~/skill-finder/ โโโ memory.md # Source mode + preferences + liked/passed skills โโโ searches.md # Recent search history (optional)
If upgrading from a previous version, see migration.md for data migration steps. The agent MUST check for legacy memory structure before proceeding.
TopicFileSetupsetup.mdMemory templatememory-template.mdSearch strategiessearch.mdEvaluation criteriaevaluate.mdSkill categoriescategories.mdEdge casestroubleshooting.md
Activate when the user says things like: "How do I do X?" "Is there a skill for this?" "Can you do this better?" "Find a skill for X" "I need a safer or more maintained option" "What should I install for this task?" Also activate when the user describes a missing capability, a repetitive workflow, or frustration with a current skill.
This skill can search two ecosystems: SourceSearchInstallBest forClawHubnpx clawhub search "query"npx clawhub install <slug>Curated registry search with built-in inspectionSkills.shnpx skills find [query]npx skills add <owner/repo@skill>Broad open ecosystem from the skills CLI Default mode: search both sources, then compare results together. Configurable modes: both โ recommended default clawhub โ only search ClawHub skills.sh โ only search the Skills.sh ecosystem Store the current mode in ~/skill-finder/memory.md. If the user has no saved preference yet, explain the two sources once, recommend both, and save the explicit choice.
This skill uses npx clawhub and npx skills to discover and install skills from two different ecosystems. Review candidates before installation, keep installs opt-in, and keep the source attached to every recommendation.
This skill stores local preference data in ~/skill-finder/: Source mode, explicit preferences, liked skills, and passed skills in the local memory file inside ~/skill-finder/ Optional recent search history in a local search log inside ~/skill-finder/ Create on first use: mkdir -p ~/skill-finder
Unless the user has explicitly chosen otherwise, search ClawHub and Skills.sh for the same need, then compare the strongest results together. Never assume a Skills.sh result can be installed with clawhub, or the reverse. Keep the source and install command attached to every recommendation.
Do not wait only for "find a skill." Activate when the user describes missing functionality, asks how to do a task faster, or wants a better tool for a job.
User says "help with PDFs" - think about what they actually need: Edit? -> npx clawhub search "pdf edit" and npx skills find pdf edit Create? -> npx clawhub search "pdf generate" and npx skills find pdf generate Extract? -> npx clawhub search "pdf parse" and npx skills find pdf parse
Never recommend blindly. Inspect strong candidates and check evaluate.md criteria: Description clarity Download count (popularity = maintenance) Last update (recent = active) Author or repository reputation Install scope and friction For Skills.sh candidates, pay attention to the package source and install string the CLI returns.
Don't just list skills. Explain why each fits, who it is best for, and why the winner wins: "Best fit: pdf-editor from ClawHub โ handles form filling and annotations, 2.3k downloads, updated last week. Matches your need for editing contracts better than the Skills.sh options." When there are multiple good fits, rank the top 1-3 and call out tradeoffs clearly.
When user explicitly states what they value, confirm and update ~/skill-finder/memory.md: "Search both by default" -> set source mode to both "Only use Skills.sh for this workspace" -> set source mode to skills.sh "Only check ClawHub" -> set source mode to clawhub "I prefer minimal skills" -> add to Preferences "This one is great" -> add to Liked with reason "Too verbose" -> add to Passed with reason Do not infer hidden preferences from behavior-only signals.
Before recommending, read memory.md: Respect saved source mode unless the user overrides it Skip skills similar to Passed ones Favor qualities from Liked ones Apply stated Preferences
If a candidate skill is marked risky by scanner output, or the install path is unclear: Explain the warning or ambiguity first Prefer a safer alternative Do not run force-install flags for the user Do not auto-accept install prompts with -y Do not choose global install scope unless the user explicitly wants it Install only with explicit user consent
If nothing is strong enough: Say what was searched Say which source mode was used Explain why the matches are weak Help directly or suggest creating a purpose-built skill
# ClawHub search and inspect npx clawhub search "query" npx clawhub inspect <slug> npx clawhub install <slug> npx clawhub list # Skills.sh ecosystem npx skills find [query] npx skills add <owner/repo@skill> npx skills list npx skills check npx skills update # Example install string returned by `npx skills find` npx skills add vercel-labs/agent-skills@vercel-react-best-practices
Detect - Is the user describing a capability gap or installable need? Load memory - Read ~/skill-finder/memory.md for source mode and preferences Understand - What does user actually need? Search - Use both by default, or the saved single-source mode Evaluate - Check quality signals (see evaluate.md) Compare - Rank results across both sources by fit + quality Recommend - Top 1-3 with clear reasoning and a winner Install or fallback - Install only with consent, otherwise help directly Learn - Store explicit feedback in memory
When presenting results, prefer this structure: Best fit: <slug or owner/repo@skill> Source: <ClawHub or Skills.sh> Why it wins: <1-2 lines> Install: <exact command> Tradeoffs: <what it does not cover or where alternative is stronger> Alternatives: <slug>, <slug> Next step: Install now or continue without installing
Waiting for the exact phrase "find a skill" -> misses proactive discovery moments Searching generic terms -> gets noise. Be specific: "react testing" not "testing" Searching only one ecosystem when the saved mode is both Recommending by name match only -> misses better alternatives with different names Mixing install commands between ClawHub and Skills.sh Ignoring download counts -> low downloads often means abandoned Not checking last update -> outdated skills cause problems
Data that leaves your machine: Search queries sent to ClawHub registry (public search) Search queries sent through the skills CLI / Skills.sh ecosystem Data that stays local: All preferences in ~/skill-finder/memory.md Search history (if enabled) This skill does NOT: Install skills without user consent Use force-install flags to skip scanner warnings Auto-confirm npx skills add with -y Switch to global install scope silently Collect hidden behavior data Access files outside ~/skill-finder/
Install with npx clawhub install <slug> if user confirms: skill-manager โ manages installed skills, suggests updates skill-builder โ creates new skills from scratch skill-update โ updates existing skills
If useful: clawhub star skill-finder Stay updated: clawhub sync
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.