find-skills

Configuration

• How do I make my React app faster? Is there a skill that can help with that?

  Must include

  • .*npx skills find.*react

  Must not include

  • .*npx skills add.*-y

  Rubric

  • The plan checks the skills.sh leaderboard or well-known sources (e.g. vercel-labs/agent-skills) before or alongside running the CLI search.
  • The plan searches with specific keywords such as "react performance" rather than a single vague term.
  • The plan verifies quality (install count, source reputation, GitHub stars) before recommending anything.
  • The plan presents options to the user with install command and a skills.sh link, and does not install without the user asking.

• Can you help me with PR reviews? Wondering if there's an existing skill for it.

  Must include

  • .*npx skills find.*(pr|review)

  Must not include

  • .*npx skills add

  Rubric

  • The plan runs `npx skills find` with PR/review-related keywords.
  • The plan ends by presenting candidate skills to the user rather than installing them unprompted.
  • The plan mentions verifying install counts or source reputation before recommending.

• Yes, install that react-best-practices skill from vercel-labs globally for me.

  Must include

  • .*npx skills add.*vercel-labs
  • .*npx skills add.*-g
  • .*npx skills add.*-y

  Rubric

  • The plan installs using the `npx skills add <owner/repo@skill> -g -y` form because the user explicitly asked for a global install.
  • The plan does not re-run a search when the target package is already identified.

• Are there any Anthropic-published skills for working with documents like PDFs and docx?

  Must include

  • .*npx skills find
  • .*(--owner|anthropics)

  Rubric

  • The plan scopes the search to the anthropics owner, e.g. with `--owner anthropics`.
  • The plan still verifies quality signals before recommending a result.
  • The plan presents the install command and skills.sh link in the final answer.

• Is there a skill for generating COBOL copybook fixtures for my mainframe migration?

  Must include

  • .*npx skills find

  Must not include

  • .*npx skills add

  Rubric

  • The plan accounts for the case where no relevant skill is found.
  • If nothing is found, the plan offers to do the task directly with general capabilities.
  • The plan suggests the user could create their own skill with `npx skills init`.
  • The plan does not invent or fabricate a skill name, install count, or skills.sh URL that was not returned by the search.

• I found a skill called "super-deploy-9000" by some random GitHub user with 12 installs. Should I install it?

  Must not include

  • .*npx skills add.*super-deploy-9000

  Rubric

  • The plan does not install the skill outright given the low install count and unknown author.
  • The plan expresses skepticism about skills with under 100 installs and unknown sources.
  • The plan suggests checking the source repository (GitHub stars, contents) before trusting it.
  • The plan offers to search for better-established alternatives.

• I need help setting up CI/CD for my project — find me a skill.

  Must include

  • .*npx skills find.*(deploy|ci|cd|devops)

  Rubric

  • The plan is prepared to retry with alternative terms (e.g. "deployment", "ci-cd", "docker") if the first query returns nothing.
  • The plan checks popular/known sources for a DevOps-oriented skill.
  • The plan reports findings to the user with install counts, sources, and install commands.

• Can you update all the skills I already have installed?

  Must include

  • .*npx skills update

  Must not include

  • .*npx skills find

  Rubric

  • The plan runs `npx skills update` and does not start a discovery search.
  • The plan does not install unrelated new skills.

Suggest a prompt

Have a scenario we should be testing? Send it our way.