find-skills

Find and install relevant skills from skillhub with clawhub fallback.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/ViewWay/openclaw-skills --skill find-skills-viewway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-skills
Source: https://github.com/ViewWay/openclaw-skills/tree/main/find-skills
Command: npx skills add https://github.com/ViewWay/openclaw-skills --skill find-skills-viewway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps users find, compare, and install relevant skills quickly, reducing the friction of capability discovery.

Core Features & Use Cases

  • Priority-based discovery: Ensures the most relevant skills are surfaced first for user intents to find or install skills.
  • Source-first workflow: Uses skillhub primarily and clawhub as a fallback to maximize coverage and speed.
  • Guided install flow: Presents clear install options and rationale to users, with fallback messaging when no matches exist.

Quick Start

Ask me to find or install a skill, and I will search skillhub first, then clawhub if needed, and present install options.

Frequently Asked Questions about find-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find and install relevant skills for a specific task?

To find and install relevant skills, you can use a guided discovery workflow that searches skillhub first and falls back to clawhub, presenting priority-based install options for your task.

What is priority-based skill discovery and how does it work?

Priority-based skill discovery surfaces the most relevant skills first for your search intent. It queries skillhub primarily, uses clawhub as a fallback source, and presents comparison options to install.

Can I use skillhub and clawhub together for skill discovery?

Yes, skill discovery uses skillhub as the primary source and clawhub as a fallback to maximize coverage and speed, ensuring you find relevant skills across both platforms during the install workflow.

What happens when no matching skills are found during a search?

When no matching skills are found, the discovery workflow provides clear fallback messaging to the user, ensuring transparency about the search results across both skillhub and clawhub sources.

What's the best way to compare skills before installing them?

The best way to compare skills is using a guided discovery workflow that prioritizes relevant matches first, enabling side-by-side comparison and presenting clear install options with rationale across skillhub and clawhub.