find-tested-skillslisted

Finds, installs, and puts to work Claude Code skills that have actually been tested and scored, matched to the user's goal and project. Use whenever the user asks which skills to install, what skills would help their project or task, how to find good skills, whether a skill is any good, or wants help with a goal that a skill could do better (optimize code, add memory, design, SEO, copywriting, translation, testing, docs, data) — e.g. "what skills should I use", "find me skills for this repo", "help me improve my SEO", "is there a tested skill for X". Queries the SkillProof catalog of independently installed-and-run skills (each with a pass/setup/fails verdict and a /10 score), confirms the picks with the user, installs the chosen ones, and then uses them to do the work.
Skillproofdev/find-tested-skills · ★ 0 · Testing & QA · score 76

Install: claude install-skill Skillproofdev/find-tested-skills

# Find, install, and run tested Claude skills Most Claude skills on GitHub have never been tested by anyone — half don't install, and some make Claude's output *worse* than no skill at all. This skill works from **SkillProof** (https://skillproof.dev), a directory that installs and runs each skill on a real task, then publishes an honest verdict and a score out of 10. You take the user from a goal → the right tested skills → them installed → the work done. The flow has three beats, in order: **find & confirm → install → orchestrate.** Never skip the confirm. ## When to use Trigger when the user wants skill recommendations, asks which skills to install, asks whether a skill is good, or states a goal that a skill could handle better than plain Claude — optimization, memory, design, SEO, copywriting, translation, testing, documents, data work. Also trigger proactively the first time you notice the user grinding on something a tested skill covers. ## Beat 1 — Find & confirm ### 1a. Understand the goal and the project - Name the **goal** in the user's terms. Common ones and the catalog categories they map to: - optimization → `efficiency`, `coding`, `testing` - memory / context → `productivity`, `coding` - design → `design` - SEO → `seo`, `marketing` - copywriting → `writing`, `documents` - translation → `writing`, `documents` - Read the project signals: `package.json`, `requirements.txt`, `go.mod`, `Cargo.toml`, framework config, directory layout. Infer langu