Agent skill

Find Skills

by Peiiii in Peiiii/nextclaw

A skill your agent uses when the user wants to discover, evaluate, and install external agent skills from the open skills ecosystem, especially through the Vercel Skills CLI.

MITAuto-check passed

Install Find Skills

skills CLI
$ npx skills add Peiiii/nextclaw --skill find-skills -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Peiiii/nextclaw find-skills --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/find-skills .claude/skills/find-skills && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
find-skills
GitHub stars
260
Token cost
~1.4k tokens
SKILL.md length
752 words
Files
2
Skills in repo
70
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user wants to discover, evaluate, and install external agent skills from the open skills ecosystem, especially through the Vercel Skills CLI.

  • Works in 6 steps: Understand the need → Check the directory or leaderboard first → Search with specific terms → …
  • The user wants to discover
  • SKILL.md covers Overview, Platform Notes, When To Use This Skill and What The Skills CLI Is, plus 7 more sections
  • Calls npx; reaches skills.sh

What it does

Find Skills is an agent skill from Peiiii/nextclaw. Use when the user wants to discover, evaluate, and install external agent skills from the open skills ecosystem, especially through the Vercel Skills CLI.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `marketplace.json`).

It works with Vercel. The repository describes itself as: A human-centered long-term AI partner—not a task-centered assistant. The licence is MIT.

When your agent uses it

  • The user wants to discover
  • Install external agent skills from the open skills ecosystem
  • Especially through the Vercel Skills CLI

Example prompts

  • “/find-skills”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Understand the need
  2. Check the directory or leaderboard first
  3. Search with specific terms
  4. Verify quality before recommending
  5. Present the best option clearly
  6. Offer installation

What it can do on your machine

Read from SKILL.md and the folder at commit 4d9d500. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • skills.sh

    Also links to:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Find Skills loads about 1.4k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 752 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Peiiii/nextclaw at commit 4d9d500, republished under its MIT licence (© Peiiii). 752 words, ~1,450 tokens.

Download SKILL.mdSave it as .claude/skills/find-skills/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
find-skills
description
Use when the user wants to discover, evaluate, and install external agent skills from the open skills ecosystem, especially through the Vercel Skills CLI.

Find Skills

Overview

Use this skill when the user is asking for a capability that might already exist as an installable skill in the open agent skills ecosystem.

This skill wraps the upstream Vercel-style Skills CLI workflow for NextClaw users.

Be explicit about the boundary:

  • This marketplace skill helps the AI search, evaluate, and explain external skills.
  • The upstream Skills CLI (npx skills) owns actual discovery and installation in its supported agent ecosystems.
  • NextClaw marketplace is a separate channel and should be checked first when the user specifically wants a NextClaw-native skill.

Do not blur those ecosystems together.

Platform Notes

This discovery flow should be presented as cross-platform.

  • npx skills ... is a Node/npm-based workflow and is generally suitable for macOS, Linux, and Windows.
  • On Windows, avoid assuming symlink-friendly behavior.
  • If installation method matters on Windows, prefer the upstream --copy option instead of implying symlinks will always work.

Example Windows-friendly pattern:

bash
npx skills add vercel-labs/agent-skills --skill frontend-design --copy -y

When To Use This Skill

Use this skill when the user:

  • asks "is there a skill for X",
  • wants to extend agent capabilities beyond what is already installed,
  • asks for a domain workflow that is commonly packaged as a reusable skill,
  • wants help exploring skills.sh,
  • or wants to install a skill from the open agent skills ecosystem.

Do not use this skill when the user already knows the exact NextClaw marketplace skill they want and only needs nextclaw skills install.

What The Skills CLI Is

The upstream Skills CLI is a package manager for the open agent skills ecosystem.

Useful commands:

bash
npx skills find [query]
npx skills add <package>
npx skills check
npx skills update

Browse skills at:

text
https://skills.sh/

Decision Order

When the user asks for a skill, follow this order:

  1. Check whether the user wants a NextClaw-native marketplace skill or a broader external skill.
  2. If a NextClaw-native match is likely, prefer NextClaw marketplace first.
  3. If the user wants the broader open ecosystem, use the Skills CLI flow below.

Do not send the user to an external ecosystem when a NextClaw-native option already solves the problem cleanly.

External Skill Discovery Flow

1. Understand the need

Identify:

  • the domain,
  • the concrete task,
  • and whether it sounds like a reusable skill rather than a one-off request.

Examples:

  • "How do I review PRs better?" -> code review skill
  • "How do I speed up React apps?" -> React or performance skill
  • "Is there a skill for changelogs?" -> docs or release skill
2. Check the directory or leaderboard first

Before searching randomly, look at:

text
https://skills.sh/

Prefer established sources when possible.

Examples of higher-trust sources include:

  • vercel-labs
  • anthropics
  • microsoft
3. Search with specific terms

Run:

bash
npx skills find [query]

Examples:

bash
npx skills find react performance
npx skills find pr review
npx skills find changelog

Prefer specific multi-word searches over vague single words.

4. Verify quality before recommending

Do not recommend a skill from search results alone.

Always verify:

  • install count if the directory shows it,
  • source reputation,
  • repository quality and maintenance signals,
  • and whether the skill description actually matches the user's task.

Be cautious with low-signal or unknown sources.

Show full SKILL.md (282 more words)Show less
5. Present the best option clearly

When you find a good match, present:

  • the skill name,
  • what it helps with,
  • who publishes it,
  • the install command,
  • and the link for the user to inspect it.
6. Offer installation

If the user wants to proceed, use an explicit install command such as:

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

Use the exact upstream command shape that matches the selected skill source. On Windows, consider --copy when symlink behavior is undesirable or unsupported.

Important Boundary For NextClaw Users

Do not imply that npx skills add installs a NextClaw marketplace skill.

Treat these as separate paths:

  • NextClaw marketplace install: nextclaw skills install <slug>
  • Open skills ecosystem install: npx skills add <package-or-source>

An open-ecosystem global install can appear in NextClaw under the Global skills group when it materializes at ~/.agents/skills/. It remains separate from the NextClaw marketplace and workspace-managed lifecycle, so say which source and update path the user is choosing.

Search Tips

  • Use specific keywords such as react testing instead of testing.
  • Try alternative terms if the first search is weak.
  • Prefer official or widely used publishers when possible.
  • If the user only has a vague idea, start by narrowing the domain before recommending any install.

When No Good Skill Exists

If no relevant external skill is found:

  • say so clearly,
  • offer to handle the task directly,
  • and, if useful, suggest creating a custom skill instead of forcing a weak recommendation.

Success Criteria

This skill is working correctly when:

  • the user learns whether they need NextClaw marketplace or the broader open skills ecosystem,
  • search happens with explicit queries,
  • quality is checked before recommendation,
  • install commands are shown accurately,
  • and ecosystem boundaries stay truthful.

Resources

© Peiiii, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/find-skills of Peiiii/nextclaw.

  • SKILL.md
  • marketplace.json

Open the folder on GitHubat commit 4d9d500

Compare with similar skills

Find Skills next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Find Skills compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Find Skills this skillPeiiii/nextclaw260—~1.4kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Agent Browser CLIvercel-labs/agent-browser44k24 repos~864Automated safety check: PassApache-2.0
Vercel Deploybytedance/deer-flow84k10 repos~797Automated safety check: PassMIT
Sandbox Benchvercel/next.js143k—~4.1kAutomated safety check: PassMIT
Vercel Optimize Auditvercel-labs/agent-skills32k8 repos~4.3kAutomated safety check: PassNone

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed
  • Agent Browser CLI

    vercel-labs/agent-browser

    Official

    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…

    44k GitHub starsUsed in 24 repos~864 tokens
    Productivity & AutomationAuto-check passed
  • Vercel Deploy

    bytedance/deer-flow

    Deploys a project to Vercel with one script and no login, then returns a live preview URL and a claim link for moving the deployment into your own Vercel account.

    84k GitHub starsUsed in 10 repos~797 tokens
    DevOps & CloudAuto-check passed
  • Sandbox Bench

    vercel/next.js

    Official

    Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app…

    143k GitHub stars~4.1k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • Vercel Optimize Audit

    vercel-labs/agent-skills

    Official

    Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.

    32k GitHub starsUsed in 8 repos~4.3k tokens
    DevOps & CloudAuto-check passed
  • AI SDK

    vercel-labs/ai-facts

    Official

    Answer questions about the AI SDK and help build AI-powered features.

    168 GitHub starsUsed in 20 repos~1.2k tokens
    AI & LLM EngineeringAuto-check passed

More from Peiiii/nextclaw

All 70 skills in this repo
  • Nextclaw Skin Studio

    Peiiii/nextclaw

    A skill your agent uses when a user wants to browse, apply, inspect, create, refine, switch, or remove a NextClaw skin; wants a personal skin with arbitrary CSS, JavaScript, images, SVG, DOM…

    260 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard…

    260 GitHub stars~802 tokensUpdated yesterday
    Auto-check passed
  • 当 NextClaw 产品更新后需要生成、替换、挑毛病或检查官网、GitHub README、用户文档或社交传播中的真实截图、AI 宣传视觉、整页 HTML 宣传预览、社区二维码等对外视觉资产时使用;也用于“更新截图”“重新截一批图”“做宣传页”“生成 campaign 页面”“视觉审稿”“五星挑刺法”或发布前检查视觉资产。普通站点布局开发或只写文章不触发。

    260 GitHub stars~801 tokensUpdated yesterday
    Auto-check passed
  • UI UX Pro Max

    Peiiii/nextclaw

    A skill your agent uses when the user wants professional UI/UX design guidance, design-system generation, UX review, or stack-specific frontend guidance through a bundled local UI/UX Pro Max dataset…

    260 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Impeccable

    Peiiii/nextclaw

    A skill your agent uses when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable…

    260 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Curate NextClaw skill resources, including OpenClaw and community sources.

    260 GitHub stars~479 tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Find Skills

What does Find Skills do?

A skill your agent uses when the user wants to discover, evaluate, and install external agent skills from the open skills ecosystem, especially through the Vercel Skills CLI. Find Skills is an agent skill from Peiiii/nextclaw. Use when the user wants to discover, evaluate, and install external agent skills from the open skills ecosystem, especially through the Vercel Skills CLI.

When should I use Find Skills?

Find Skills fits situations like: the user wants to discover; install external agent skills from the open skills ecosystem; especially through the Vercel Skills CLI.

How do I install Find Skills in Claude Code?

Run `npx skills add Peiiii/nextclaw --skill find-skills -a claude-code`. Or copy the skill folder (skills/find-skills in Peiiii/nextclaw) into .claude/skills/find-skills in your project. Claude Code loads it when a task matches its description.

How do I install Find Skills in Codex?

Run `npx skills add Peiiii/nextclaw --skill find-skills -a codex`. Or copy the skill folder (skills/find-skills in Peiiii/nextclaw) into .agents/skills/find-skills in your project. Codex loads it when a task matches its description.

Can I use Find Skills in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Peiiii/nextclaw --skill find-skills -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/find-skills, .gemini/skills/find-skills, .github/skills/find-skills and .opencode/skills/find-skills in your project.

What does Find Skills need to run?

Going by SKILL.md and its folder, Find Skills needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Find Skills access the network?

SKILL.md names 2 domains. In commands or code: skills.sh; the agent is likely to contact it when it follows the instructions. As links in the text: github.com. This is read from the text; nothing was executed.

Is Find Skills safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Find Skills use?

Find Skills is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Find Skills use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Find Skills?

Skills that share tags, products or a category with Find Skills: Vercel Composition Patterns (supabase/supabase, 111k stars), Agent Browser CLI (vercel-labs/agent-browser, 44k stars), Vercel Deploy (bytedance/deer-flow, 84k stars) and Sandbox Bench (vercel/next.js, 143k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Find Skills?

Peiiii (a GitHub user) maintains it in Peiiii/nextclaw, which has 260 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 9, 2026.

Source: Peiiii/nextclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.