find-skills

bytedance/deer-flow · Agent Skill

Helps users find and install new AI agent skills when they are looking for solutions to specific tasks or want to expand the agent's capabilities.

Jump to install ↓

Overview

PublisherbytedanceOrganization
Repositorybytedance/deer-flow ↗
Skill folderfind-skills
Stars82,309
Bundled files1
LicenseMIT
Last updatedJanuary 31, 2026
LinksSkill source ↗ · Repository ↗

Mozgi check

What we found in the skill files. Details come with a subscription.

Security
medium risk · 1 point needs attention
Compatibility
needs extra software
Similar skills
51 similar skills found
Also with subscription

Installation

A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.

Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.

Install the “find-skills” skill from mozgi.io (https://mozgi.io/skills/find-skills/) for me.

1. Download the archive: https://mozgi.io/skills/find-skills/download
   If it fails, take the skill folder from the source: https://github.com/bytedance/deer-flow/tree/main/skills/public/find-skills
2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me.
3. Put the “find-skills” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.).
4. Make sure <skills folder>/find-skills/SKILL.md exists.
5. Briefly tell me what this skill does and offer to try it on my task.

If you cannot do a step yourself, tell me what to click or type.

Review the source files

1 file Download Zip

Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.

SKILL.md contents

Original author text · read-only

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 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 bash /path/to/skill/scripts/install-skill.sh vercel-labs/agent-skills@vercel-react-best-practices

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:
bash /path/to/skill/scripts/install-skill.sh vercel-labs/agent-skills@vercel-react-best-practices

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

Step 4: Install the Skill

If the user wants to proceed, use the install-skill.sh script to install the skill and automatically link it to the project:

bash /path/to/skill/scripts/install-skill.sh <owner/repo@skill-name>

For example, if the user wants to install vercel-react-best-practices:

bash /path/to/skill/scripts/install-skill.sh vercel-labs/agent-skills@vercel-react-best-practices

The script will install the skill globally to skills/custom/

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

Frequently asked questions

What does the find-skills skill do?

Helps users find and install new AI agent skills when they are looking for solutions to specific tasks or want to expand the agent's capabilities.

How do I install find-skills?

Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.

Which AI models work with find-skills?

Skills are plain Markdown instructions (the Agent Skills format), so find-skills works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.

Is find-skills free?

The skill is published openly by bytedance under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.

Is it safe to install skills?

A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.

How is a skill different from an MCP server or a plugin?

An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.

Related skills

All skills →