Explore
A task outside your usual toolkit
You need help with a deployment, design audit, or document format you rarely handle. Search by the actual task instead of guessing a repository name.
01 / The skill · Meta-skill · Skill discovery
Find Skills helps an agent turn a task into a focused skills search, compare candidates, and present an install path. It is a discovery workflow, not a guarantee that every result is safe or suitable.
Published by Vercel Labs · Type: Meta-skill for discovering other skills
Independent guide. Vercel Labs has not endorsed Floatboat.
Upstream installation
npx skills add vercel-labs/skills --skill find-skillsThis installs the publisher's skill through the open Skills CLI; it is not a Floatboat installation command.
This Vercel Labs skill is useful when you know the job but not the name of the agent capability you need. Its instructions call for identifying the domain and task, checking the skills.sh leaderboard, then searching more narrowly and presenting a shortlist for the user to choose from.
Ask the agent
“Find a skill for reviewing a Next.js application's accessibility. Show me the source, what it covers, and the install command; do not install it yet.”
A useful result
A useful response is a small set of candidates with source links and trade-offs—not an automatic installation or a claim that the top-ranked result is always best.
Use it when the task is clear but the right Skill is not. It helps narrow candidates before you inspect their source or install anything.
Explore
You need help with a deployment, design audit, or document format you rarely handle. Search by the actual task instead of guessing a repository name.
Compare
Use a shortlist to compare source, scope, and adoption before opening the original SKILL.md and deciding whether to install.
Repeat
Keep the discovery step consistent across projects, while making the final installation decision for each workspace separately.
The skill guides an agent from a specific task to a shortlist for your review; it does not make the installation decision for you.
Identify the domain and a specific action, such as reviewing accessibility rather than simply ‘web development’.
Check known skills and narrow the query; compare the publisher, described scope, and original instructions.
Open the candidate's repository and SKILL.md, check any scripts or permissions, and install only after choosing a trusted fit.
02 / Practical guide
Discovery is only the first decision. Search, compare, and review a candidate before it changes your agent environment.
It turns a task into a narrower search: identify the domain, name the action, check established options, then use the Skills CLI to look for candidates. The result is a shortlist to inspect, not an automatic choice of the first hit.
Start with task fit and the original publisher. Open each candidate's SKILL.md and any bundled scripts, then check required tools, permissions, maintenance, and installation scope. Install counts or repository stars can inform discovery, but do not prove quality or safety.
Finding, reviewing, and installing are separate steps. The skill can surface commands and recommend candidates, but you should choose the source and authorize installation only after reviewing what the package will add to your agent environment.
These are upstream commands, not Floatboat features.
npx skills find [query]Search by the specific task, not a broad category.
npx skills add <package>Use the original package path after reviewing its source.
npx skills updateReview upstream changes before applying updates.
Read another Skill guide and check its original source before using it.
03 / Put it to work · From discovery to work
Review the candidate's original instructions first. Then keep the task, files, and review together in Floatboat.