agentleFS
Elong-svgElong-svg/business-plan-factory/skills/find-skills/SKILL.md

find-skills

Skill2 starsChanged 6 months agoMITView on GitHub

Helps users discover and install agent skills when they ask

184 other projects use a version of this, 153 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • stophobiaSkill

    surprise-me

    Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for "something interesting".

    Also in 4 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • HK-hubSkill

    ppt-generation

    Use this skill when the user requests to generate, create, or make presentations (PPT/PPTX). Creates visually rich slides by generating images for each slide and composing them into a PowerPoint file.

    Also in 4 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • +6 more from nicepkg

The file

Show its rules and text

We split this skill into the rules it gives an agent

22 rules. 5 are common, 9 are distinctive, and 8 are very specific to this project.

  • 5

    Common

    Most of the 177 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this skill when the user:

    line 20
  2. Common:

    When a user asks for help with something, identify:

    line 46
  3. Distinctive:

    Run the find command with a relevant query:

    line 54
  4. Distinctive:

    If no relevant results are found, try ClawHub as a fallback (see "ClawHub Fallback" section below).

    line 75
  5. Common:

    When you find relevant skills, present them to the user with:

    line 79
  6. Very specific:

    Before installing, detect which client is running by checking the __CFBundleIdentifier environment variable:

    line 99
  7. Very specific:

    Default to WorkBuddy: If the variable is empty, unset, or contains any value other than codebuddy, treat the current client as WorkBuddy.

    line 112
  8. Very specific:

    Before installing from the network (npx skills add, ClawHub, etc.), you must look in WorkBuddy’s official on-disk skills marketplace:

    line 116
  9. Distinctive:

    If a match exists, copy the entire skill folder into the target skills directory from Step 4 (do not remove the original marketplace copy).

    line 121
  10. Distinctive:

    If no suitable skill exists locally, continue with Step 6 (remote install).

    line 131
  11. Distinctive:

    Always confirm the copied skill is present under the target directory before reporting success.

    line 133
  12. Distinctive:

    If Step 5 did not yield a local match and the user still wants to proceed, install from the registry:

    line 137
  13. Very specific:

    After a remote install (Step 6), if the current client is WorkBuddy (detected in Step 4), verify the skill exists at …

    line 147
  14. Very specific:

    If the skill is missing from ~/.workbuddy/skills/, check ~/.agents/skills/<skill-name>/ and create a symlink:

    line 154
  15. Very specific:

    If the skill is not in ~/.agents/skills/ either, find where it was actually installed (e.g., ~/.codebuddy/skills/<skill-name>) and copy it:

    line 161
  16. Distinctive:

    Always confirm the skill is accessible at the target directory before reporting success to the user.

    line 167
  17. Very specific:

    If npx skills find returns no relevant results, try ClawHub (the OpenClaw skill registry) as a secondary source:

    line 171
  18. Distinctive:

    If a match is found, install it directly to the target directory (detected in Step 4):

    line 177
  19. Very specific:

    Before npx clawhub install, complete Step 5 (local marketplace check).

    line 187
  20. Common:

    When searching, consider these common categories:

    line 193
  21. Common:

    Try alternative terms: If "deploy" doesn't work, try "deployment" or "ci-cd"

    line 208
  22. Distinctive:

    If neither Vercel Skills nor ClawHub has relevant results:

    line 213

“Common” is measured: kept by at least 6 in 10 of the 177 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Find Skills

This skill helps you discover and install skills from the open agent skills ecosystem.

When to Use This Skill

Use this skill when the user:

  • Asks "how do I do X" where X might be a common task with an existing skill
  • Says "find a skill for X" or "is there a skill for X"
  • Asks "can you do X" where X is a specialized capability
  • Expresses interest in extending agent capabilities
  • Wants to search for tools, templates, or workflows
  • Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)

What is the Skills CLI?

The Skills CLI (npx skills) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.

Key commands:

  • npx skills find [query] - Search for skills interactively or by keyword
  • npx skills add <package> - Install a skill from GitHub or other sources
  • npx skills check - Check for skill updates
  • npx skills update - Update all installed skills

Browse skills at: https://skills.sh/

How to Help Users Find Skills

Step 1: Understand What They Need

When a user asks for help with something, identify:

  1. The domain (e.g., React, testing, design, deployment)
  2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
  3. Whether this is a common enough task that a skill likely exists

Step 2: Search for Skills

Run the find command with a relevant query:

npx skills find [query]

For example:

  • User asks "how do I make my React app faster?" → npx skills find react performance
  • User asks "can you help me with PR reviews?" → npx skills find pr review
  • User asks "I need to create a changelog" → npx skills find changelog

The command will return results like:

Install with npx skills add <owner/repo@skill>

vercel-labs/agent-skills@vercel-react-best-practices
└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices

If no relevant results are found, try ClawHub as a fallback (see "ClawHub Fallback" section below).

Step 3: Present Options to the User

When you find relevant skills, present them to the user with:

  1. The skill name and what it does
  2. The install command they can run
  3. A link to learn more at skills.sh

Example response:

I found a skill that might help! The "vercel-react-best-practices" skill provides
React and Next.js performance optimization guidelines from Vercel Engineering.

To install it:
npx skills add vercel-labs/agent-skills@vercel-react-best-practices

Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices

Step 4: Detect Current Client

Before installing, detect which client is running by checking the __CFBundleIdentifier environment variable:

echo $__CFBundleIdentifier

Determine the target skills directory based on the result:

__CFBundleIdentifier containsClientTarget skills dir
codebuddyCodeBuddy~/.codebuddy/skills/
anything else / empty / unsetWorkBuddy~/.workbuddy/skills/

Default to WorkBuddy: If the variable is empty, unset, or contains any value other than codebuddy, treat the current client as WorkBuddy.

Step 5: Check the Local WorkBuddy Skills Marketplace First (Required)

Before installing from the network (npx skills add, ClawHub, etc.), you must look in WorkBuddy’s official on-disk skills marketplace:

Local marketplace folder: ~/.workbuddy/skills-marketplace/skills

  1. List or inspect that directory and identify a skill subfolder that matches the user’s need (by folder name, SKILL.md, or metadata).
  2. If a match exists, copy the entire skill folder into the target skills directory from Step 4 (do not remove the original marketplace copy).
ls ~/.workbuddy/skills-marketplace/skills
# WorkBuddy target:
cp -r ~/.workbuddy/skills-marketplace/skills/<skill-folder-name> ~/.workbuddy/skills/<skill-folder-name>
# CodeBuddy target:
cp -r ~/.workbuddy/skills-marketplace/skills/<skill-folder-name> ~/.codebuddy/skills/<skill-folder-name>
  1. If no suitable skill exists locally, continue with Step 6 (remote install).

Always confirm the copied skill is present under the target directory before reporting success. If the user already has that skill name in the target dir, resolve the conflict (skip, replace, or rename) explicitly.

Step 6: Install the Skill (Remote)

If Step 5 did not yield a local match and the user still wants to proceed, install from the registry:

npx skills add <owner/repo@skill> -g -y

The -g flag installs globally (user-level) and -y skips confirmation prompts.

Step 7: Ensure Skill Is in the Correct Directory

After a remote install (Step 6), if the current client is WorkBuddy (detected in Step 4), verify the skill exists at ~/.workbuddy/skills/<skill-name>. The CLI typically installs to ~/.agents/skills/<skill-name>/ and may not automatically link to WorkBuddy’s directory.

# Check if skill already exists in WorkBuddy's directory
ls -la ~/.workbuddy/skills/<skill-name>

If the skill is missing from ~/.workbuddy/skills/, check ~/.agents/skills/<skill-name>/ and create a symlink:

# If installed at ~/.agents/skills/<skill-name>, create symlink
ln -s ../../.agents/skills/<skill-name> ~/.workbuddy/skills/<skill-name>

If the skill is not in ~/.agents/skills/ either, find where it was actually installed (e.g., ~/.codebuddy/skills/<skill-name>) and copy it:

cp -r <installed-path> ~/.workbuddy/skills/<skill-name>

Always confirm the skill is accessible at the target directory before reporting success to the user.

ClawHub Fallback

If npx skills find returns no relevant results, try ClawHub (the OpenClaw skill registry) as a secondary source:

npx clawhub search [query]

If a match is found, install it directly to the target directory (detected in Step 4):

# For WorkBuddy (default):
npx clawhub install <slug> --workdir ~ --dir .workbuddy/skills

# For CodeBuddy:
npx clawhub install <slug> --workdir ~ --dir .codebuddy/skills

Before npx clawhub install, complete Step 5 (local marketplace check). After installation, verify the skill is in the target directory (same as Step 7).

Browse ClawHub skills at: https://clawhub.com/

Common Skill Categories

When searching, consider these common categories:

CategoryExample Queries
Web Developmentreact, nextjs, typescript, css, tailwind
Testingtesting, jest, playwright, e2e
DevOpsdeploy, docker, kubernetes, ci-cd
Documentationdocs, readme, changelog, api-docs
Code Qualityreview, lint, refactor, best-practices
Designui, ux, design-system, accessibility
Productivityworkflow, automation, git

Tips for Effective Searches

  1. Use specific keywords: "react testing" is better than just "testing"
  2. Try alternative terms: If "deploy" doesn't work, try "deployment" or "ci-cd"
  3. Check popular sources: Many skills come from vercel-labs/agent-skills or ComposioHQ/awesome-claude-skills

When No Skills Are Found

If neither Vercel Skills nor ClawHub has relevant results:

  1. Acknowledge that no existing skill was found in either registry
  2. Offer to help with the task directly using your general capabilities
  3. Suggest the user could create their own skill with npx skills init

Example:

I searched for skills related to "xyz" in both Vercel Skills and ClawHub
but didn't find any matches.
I can still help you with this task directly! Would you like me to proceed?

If this is something you do often, you could create your own skill:
npx skills init my-xyz-skill

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.