Skill Finder (Find ClawHub skills + Search Skills.sh)

**Quick judgment:** This is a strong, well-structured meta-skill for discovering and selecting other skills. It is particularly valuable in installations where users frequently hit capability gaps or want to optimize their toolchain, and where both ClawHub and Skills.sh are available. **What it does well** - Searches **both ClawHub and Skills.sh** (by default) and compares results instead of treating them in isolation. - Focuses on **user needs and workflows** rather than raw name matching (e.g., “PDF edit” vs just “PDF”). - Applies **explicit evaluation criteria** (downloads, update recency, description clarity, reputation, install friction) before recommending. - Maintains **local memory** in `~/skill-finder/` for source mode, preferences, liked/passed skills, and optional search history, enabling more tailored suggestions over time. - Enforces **safe installation practices**: no auto-installs, no `-y` auto-confirmation, no force-install flags, and attention to scanner warnings. - Provides a **clear recommendation format** with a “best fit,” tradeoffs, and explicit install commands per source. **Key risks & limitations** - **External dependencies:** Requires `npx clawhub` and `npx skills` along with network access; breakage or schema changes in either ecosystem can reduce reliability. - **Environment assumptions:** Assumes a filesystem with `~/skill-finder/` available for memory; non-standard or restricted environments may need adaptation. - **Latency & performance:** Searches and inspections rely on external CLIs/registries, so responsiveness depends on network and registry performance. - **Complexity for novices:** Dual-registry explanation, source-mode choices, and evaluation criteria may feel heavy for very simple, one-off tasks. **Recommended scenarios** - Workspaces where users **frequently ask for new capabilities** (“Is there a skill for X?”, “Can we do this faster?”). - Teams actively **curating or evolving their skill stack**, needing structured comparisons (downloads, maintenance, safety). - Security- or reliability-conscious setups where **blind installs are not acceptable**, and each skill must be justified. - Environments that plan to **leverage both ClawHub and Skills.sh** rather than committing to a single registry.