# Send Skill Finder to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text 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. ``` ### Upgrade existing ```text 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. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "skill-finder", "name": "Skill Finder", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/ivangdavila/skill-finder", "canonicalUrl": "https://clawhub.ai/ivangdavila/skill-finder", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/skill-finder", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=skill-finder", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "categories.md", "evaluate.md", "memory-template.md", "migration.md", "search.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "skill-finder", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-09T00:10:05.539Z", "expiresAt": "2026-05-16T00:10:05.539Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=skill-finder", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=skill-finder", "contentDisposition": "attachment; filename=\"skill-finder-1.1.5.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "skill-finder" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/skill-finder" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/skill-finder", "downloadUrl": "https://openagent3.xyz/downloads/skill-finder", "agentUrl": "https://openagent3.xyz/skills/skill-finder/agent", "manifestUrl": "https://openagent3.xyz/skills/skill-finder/agent.json", "briefUrl": "https://openagent3.xyz/skills/skill-finder/agent.md" } } ``` ## Documentation ### When to Use 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. ### Architecture 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) ### Migration If upgrading from a previous version, see migration.md for data migration steps. The agent MUST check for legacy memory structure before proceeding. ### Quick Reference TopicFileSetupsetup.mdMemory templatememory-template.mdSearch strategiessearch.mdEvaluation criteriaevaluate.mdSkill categoriescategories.mdEdge casestroubleshooting.md ### Activation Signals 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. ### Search Sources This skill can search two ecosystems: SourceSearchInstallBest forClawHubnpx clawhub search "query"npx clawhub install Curated registry search with built-in inspectionSkills.shnpx skills find [query]npx skills add 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. ### Security Note 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. ### Data Storage 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 ### 1. Search Both Sources by Default 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. ### 2. Trigger on Capability Gaps, Not Just Explicit Search Requests 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. ### 3. Search by Need, Not Name 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 ### 4. Evaluate Before Recommending 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. ### 5. Present a Decision, Not a Dump 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. ### 6. Learn Preferences and Source Mode 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. ### 7. Check Memory First 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 ### 8. Respect Installation and Security Boundaries 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 ### 9. Fallback Gracefully 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 ### Search Commands # ClawHub search and inspect npx clawhub search "query" npx clawhub inspect npx clawhub install npx clawhub list # Skills.sh ecosystem npx skills find [query] npx skills add 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 ### Workflow 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 ### Recommendation Format When presenting results, prefer this structure: Best fit: Source: Why it wins: <1-2 lines> Install: Tradeoffs: Alternatives: , Next step: Install now or continue without installing ### Common Traps 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 ### Security & Privacy 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/ ### Related Skills Install with npx clawhub install if user confirms: skill-manager — manages installed skills, suggests updates skill-builder — creates new skills from scratch skill-update — updates existing skills ### Feedback If useful: clawhub star skill-finder Stay updated: clawhub sync ## Trust - Source: tencent - Verification: Indexed source record - Publisher: ivangdavila - Version: 1.1.5 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-05-09T00:10:05.539Z - Expires at: 2026-05-16T00:10:05.539Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/skill-finder) - [Send to Agent page](https://openagent3.xyz/skills/skill-finder/agent) - [JSON manifest](https://openagent3.xyz/skills/skill-finder/agent.json) - [Markdown brief](https://openagent3.xyz/skills/skill-finder/agent.md) - [Download page](https://openagent3.xyz/downloads/skill-finder)