← Back to Skills Marketplace
rumengkai

find-slills

by rumengkai · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
823
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install find-slills
Description
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
README (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 \x3Cpackage> - 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 \x3Cowner/repo@skill>

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

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: Offer to Install

If the user wants to proceed, you can install the skill for them:

npx skills add \x3Cowner/repo@skill> -g -y

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

Common Skill Categories

When searching, consider these common categories:

Category Example Queries
Web Development react, nextjs, typescript, css, tailwind
Testing testing, jest, playwright, e2e
DevOps deploy, docker, kubernetes, ci-cd
Documentation docs, readme, changelog, api-docs
Code Quality review, lint, refactor, best-practices
Design ui, ux, design-system, accessibility
Productivity workflow, 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 no relevant skills exist:

  1. Acknowledge that no existing skill was found
  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" 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
Usage Guidance
This skill mostly does what it says (search and install skills), but it has some red flags you should consider before using it: (1) the SKILL.md assumes `npx`/Node is available but the skill doesn't declare that requirement — you may need to have Node installed. (2) It instructs use of `npx skills add ... -g -y`, which will download and install third‑party code globally and non‑interactively; only proceed after verifying the package owner and repository. (3) Ask the agent to always prompt you for explicit approval before running any `npx skills add` command (remove `-y`) and avoid global installs (`-g`) in shared environments. (4) Prefer installing skills from known, trusted sources and inspect their repo/package before installing. Finally, note the name mismatch (find-slills vs find-skills) — treat this as a small quality signal and verify links (skills.sh) before proceeding.
Capability Analysis
Type: OpenClaw Skill Name: find-slills Version: 1.0.0 The `find-skills` skill is designed to help an AI agent discover and install other skills using the `npx skills` CLI. It explicitly instructs the agent to execute commands like `npx skills find [query]` and `npx skills add <package> -g -y`. While aligned with its stated purpose, the `npx skills add` command allows the agent to download and execute arbitrary code from remote sources (e.g., GitHub repositories) without confirmation (`-y` flag). This creates a significant supply chain risk, as a malicious skill published in the ecosystem could be installed, leading to arbitrary code execution on the host system. The skill itself does not exhibit direct malicious intent (e.g., data exfiltration or backdoor installation), but its core functionality acts as a high-risk vector for potential attacks or vulnerabilities in the `npx skills` CLI or the broader skill ecosystem, classifying it as suspicious.
Capability Assessment
Purpose & Capability
The skill claims to discover and install agent skills and the instructions show exactly that workflow (using the Skills CLI). However the SKILL.md and registry metadata disagree on the name (find-slills vs find-skills) and the instructions assume the presence of `npx`/Node.js even though no required binaries are declared — a minor but meaningful incoherence.
Instruction Scope
Instructions explicitly direct the agent to run `npx skills find` and `npx skills add <...> -g -y`. That is within the stated purpose, but `npx skills add` downloads and runs third‑party packages; the SKILL.md does not require or recommend verifying package authors, nor does it caution about executing arbitrary install scripts. The use of `-y` plus `-g` encourages non-interactive, global installs which can install code without user-visible confirmation.
Install Mechanism
There is no install spec for the skill itself (instruction-only), which is low-risk. However, the runtime uses `npx` to obtain other skills. `npx`/npm can fetch arbitrary code from registries or GitHub; this is expected for a skill-discovery tool but increases exposure. The skill does not declare `npx`/Node as a required binary.
Credentials
The skill requests no environment variables or credentials, which matches its stated function. Note: skills it recommends or installs may themselves request credentials — the skill does not provide guidance about checking those downstream requirements.
Persistence & Privilege
always is false (good). But because model invocation is permitted, the agent could autonomously run the provided non-interactive install commands (`-g -y`) and perform global installs. Combined with the lack of verification guidance, this raises the risk of silent installation of untrusted code.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install find-slills
  3. After installation, invoke the skill by name or use /find-slills
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the find-skills skill. - Helps users discover and install relevant agent skills based on their questions or interest in new capabilities. - Guides users on using the Skills CLI (`npx skills`) to search, install, and manage agent skills. - Provides step-by-step instructions for identifying, finding, and presenting skills to users. - Includes tips for effective search and common skill categories for better discovery. - Offers fallback suggestions when no matching skills are found.
Metadata
Slug find-slills
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is find-slills?

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill. It is an AI Agent Skill for Claude Code / OpenClaw, with 823 downloads so far.

How do I install find-slills?

Run "/install find-slills" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is find-slills free?

Yes, find-slills is completely free (open-source). You can download, install and use it at no cost.

Which platforms does find-slills support?

find-slills is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created find-slills?

It is built and maintained by rumengkai (@rumengkai); the current version is v1.0.0.

💬 Comments