agentsclimarketplace

Skill finder

Skill yfge/skill-finder

Search, discover, and install OpenClaw agent skills from multiple registries. Use when: user asks "find a skill for X", "is there a skill that can...", "how do I do X" (where X might have an existing skill), wants to browse available skills, or asks to install/add a skill. Also triggers on "search skills", "explore skills", "what skills exist for...", or "extend capabilities".From its SKILL.md

Install
npx -y skills add yfge/skill-finder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 8 commands, including `npx clawhub search "<query>" --limit 10` and 7 more.
  • fetches URLsInstructs the agent to fetch 5 URLs, including https://agentskill.work/api/skills?q=<query>&limit=10&sort=stars and 4 more.

SKILL.md

5.1 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

Skill Finder

Discover and install agent skills from two complementary sources:

SourceCoverageSearchInstall
ClawHub (clawhub.com)Curated registry, versioned packagesVector semantic searchnpx clawhub install <slug>
AgentSkill.work330+ GitHub repos, enriched metadataREST API keyword + filtersnpx clawhub install or git clone

Always search both sources — they overlap but each has unique skills.

Workflow

1. Search

ClawHub — semantic search understands intent ("manage my tasks" finds todo skills):

npx clawhub search "<query>" --limit 10

AgentSkill.work — keyword search with filters:

# By keyword
curl -s "https://agentskill.work/api/skills?q=<query>&limit=10&sort=stars"

# By topic (GitHub topic tag)
curl -s "https://agentskill.work/api/skills?topic=<topic>&limit=10&sort=stars"

# By language
curl -s "https://agentskill.work/api/skills?language=Python&limit=10&sort=stars"

# Combined filters
curl -s "https://agentskill.work/api/skills?q=<query>&topic=<topic>&language=<lang>&limit=10&sort=stars"

Parse results with:

curl -s "<url>" | python3 -c "
import sys, json
data = json.load(sys.stdin)
print(f'Found {data[\"total\"]} skills:')
for s in data['items']:
    desc = s.get('description') or ''
    print(f'  {s[\"full_name\"]}  ★{s[\"stars\"]}  {desc[:80]}')
"

AgentSkill.work API Reference

EndpointDescription
GET /api/skillsList/search skills
GET /api/skills/{owner}/{repo}Skill detail
GET /api/skills/{owner}/{repo}/relatedRelated skills
GET /api/facets/topics?limit=20Available topics
GET /api/facets/languages?limit=20Available languages

Query parameters for /api/skills:

ParamTypeDefaultDescription
qstring—Keyword search
topicstring—Filter by GitHub topic
languagestring—Filter by programming language
ownerstring—Filter by GitHub owner
sortstars | neweststarsSort order
limit1-10020Results per page
offsetint0Pagination offset

2. Present Results

Merge results from both sources into a single list. For each skill show:

  • Name — slug (ClawHub) or owner/repo (AgentSkill.work)
  • Description — one line
  • Stars / Downloads — when available
  • Source — ClawHub / AgentSkill.work / both
  • Install command

Use a numbered list or compact table. If the user speaks Chinese, prefer description_zh or summary_zh from AgentSkill.work.

3. Inspect Before Installing

Get details on a skill before committing:

# ClawHub — metadata, stats, owner
npx clawhub inspect <slug> --json

# ClawHub — see what files are included
npx clawhub inspect <slug> --files

# ClawHub — read a specific file
npx clawhub inspect <slug> --file SKILL.md

# AgentSkill.work — full detail with features, use cases
curl -s "https://agentskill.work/api/skills/<owner>/<repo>"

4. Install

From ClawHub (preferred — versioned, validated):

npx clawhub install <slug>

Add --force to overwrite an existing installation.

From GitHub (when only on AgentSkill.work):

cd skills/
git clone <html_url> <skill-name>

After cloning, verify SKILL.md exists. If missing, the repo may not be a proper agent skill.

5. Verify

openclaw skills list 2>&1 | grep -i "<skill-name>"
openclaw skills check  # shows ready vs missing requirements

New skills are picked up on the next session — no restart needed.

Browse & Explore

# ClawHub trending / most downloaded
npx clawhub explore --sort trending --limit 10
npx clawhub explore --sort downloads --limit 10

# AgentSkill.work — discover topics
curl -s "https://agentskill.work/api/facets/topics?limit=20"

# AgentSkill.work — browse a topic
curl -s "https://agentskill.work/api/skills?topic=mcp&sort=stars&limit=10"

Tips

  • ClawHub search is semantic — "send notifications to my phone" finds push-notification skills even if those words aren't in the name.
  • AgentSkill.work has bilingual metadata — description_zh, summary_zh, key_features_zh for Chinese descriptions.
  • Many skills exist in both — when a skill appears on both ClawHub and AgentSkill.work, prefer installing from ClawHub (versioned, cleaner packaging).
  • Related skills — after finding one skill, check /api/skills/{owner}/{repo}/related to discover similar ones.
  • No skill found? Help the user directly, then suggest creating a skill with npx clawhub publish or the skill-creator skill.

What ships with it: 4 files

5.8 KB alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.