name: find-skills description: Discover and install skills from the open agent skills ecosystem version: 1.1.0 author: vercel-labs (adapted for Pulse Coder)
Find Skills
This skill helps discover and install skills for common tasks.
When to Use
Use this skill when the user:
- Asks how to do a task that may already have a community skill
- Asks to find a skill for a domain (testing, deployment, UI, docs, etc.)
- Asks for specialized capability extensions
- Wants templates, workflows, or reusable automation
Skills CLI Overview
The Skills CLI is commonly used as a package manager for open agent skills.
Common commands:
npx skills find [query]- search skills by keywordnpx skills add <owner/repo@skill>- install a specific skillnpx skills check- check for updatesnpx skills update- update installed skills
Default Install Scope
Default to project scope in .agents/skills when installing via npx skills add.
Use these defaults unless the user explicitly asks otherwise:
- Project install:
npx skills add <owner/repo@skill> -y - Global install:
npx skills add <owner/repo@skill> -g -y
Notes:
npx skillsinstalls to.agents/skillsby default for project scope.- Our engine also scans
.pulse-coder/skills,.agents/skills,.coder/skills, and.claude/skills. - If a newly installed skill does not appear, run a list/status check and verify the skill directory exists under
.agents/skills/<skill-name>.
Workflow
1) Clarify the need
Identify:
- Domain (react, testing, design, deployment, docs, etc.)
- Specific outcome (optimize, review PR, generate changelog, etc.)
- Whether a reusable skill is likely available
2) Search
Use a specific query:
npx skills find react performancenpx skills find pr reviewnpx skills find changelog
3) Present options
When results are found, provide:
- Skill name
- What it does
- Install command
- Marketplace/reference link (for example
https://skills.sh)
4) Install on request
Install with project scope by default:
npx skills add <owner/repo@skill> -y
Use global install only when requested:
npx skills add <owner/repo@skill> -g -y
If your runtime expects Pulse Coder local skills, place skill files under:
- Project scope:
.pulse-coder/skills/<skill-name>/SKILL.md - User scope:
~/.pulse-coder/skills/<skill-name>/SKILL.md
Search Tips
- Prefer specific multi-word queries over single generic terms
- Try alternate terms when needed (
deploy->deployment/ci-cd) - Check popular publishers and curated registries
If No Skill Is Found
- State that no suitable skill was found
- Offer to handle the task directly
- Optionally offer to scaffold a new local skill