Agent skill

Find Skills

Discover available skills in the builtin library by keyword.

MITAuto-check passedTesting & QA

Install Find Skills

skills CLI

$ npx skills add HezaoHezao/poirot --skill find-skills -a claude-code

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

GitHub CLI

$ gh skill install HezaoHezao/poirot 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/HezaoHezao/poirot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/core/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/

Paste into Claude Code

Install the "find-skills" agent skill from https://github.com/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/core/find-skills into .claude/skills/find-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-skills", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/core/find-skills

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add HezaoHezao/poirot --skill find-skills -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install HezaoHezao/poirot find-skills --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HezaoHezao/poirot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/core/find-skills .agents/skills/find-skills && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "find-skills" agent skill from https://github.com/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/core/find-skills into .agents/skills/find-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-skills", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add HezaoHezao/poirot --skill find-skills -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install HezaoHezao/poirot find-skills --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HezaoHezao/poirot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/core/find-skills .cursor/skills/find-skills && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "find-skills" agent skill from https://github.com/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/core/find-skills into .cursor/skills/find-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-skills", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/HezaoHezao/poirot.git --path poirot/backend/agents/skill/builtin_skills/core/find-skills

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add HezaoHezao/poirot --skill find-skills -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install HezaoHezao/poirot find-skills --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HezaoHezao/poirot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/core/find-skills .gemini/skills/find-skills && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "find-skills" agent skill from https://github.com/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/core/find-skills into .gemini/skills/find-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-skills", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install HezaoHezao/poirot find-skills

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add HezaoHezao/poirot --skill find-skills -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/HezaoHezao/poirot.git skills-src && mkdir -p .github/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/core/find-skills .github/skills/find-skills && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "find-skills" agent skill from https://github.com/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/core/find-skills into .github/skills/find-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-skills", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add HezaoHezao/poirot --skill find-skills -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install HezaoHezao/poirot find-skills --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HezaoHezao/poirot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/poirot/backend/agents/skill/builtin_skills/core/find-skills .opencode/skills/find-skills && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "find-skills" agent skill from https://github.com/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/core/find-skills into .opencode/skills/find-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-skills", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: find-skills
GitHub stars: 249
Token cost: ~1.2k tokens
SKILL.md length: 476 words
Files: 1
Skills in repo: 23
Repo updated: Jul 28, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Discover available skills in the builtin library by keyword.

Works in 3 steps: List categories → Search by keyword → Activate a non-core skill
Testing & QA work in your project
SKILL.md covers When to Use (PROACTIVE — call…, Legacy When to Use (still valid), Builtin skill library and How to find a skill, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Find Skills is an agent skill from HezaoHezao/poirot. Discover available skills in the builtin library by keyword.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. It works with GitHub. The repository describes itself as: Poirot is a deep research agent kernel built for those who care about how agents are architected. The licence is MIT.

When your agent uses it

Testing & QA work in your project

Example prompts

“/find-skills”

Requirements

Pre-approved tools (allowed-tools): list_dir, read_file, bash

Workflow steps

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

List categories
Search by keyword
Activate a non-core skill

What it can do on your machine

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

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- list_dir
- read_file
- bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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.2k tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 476 words of instructions outside code blocks.

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

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 HezaoHezao/poirot at commit 86bf279, republished under its MIT licence (© HezaoHezao). 476 words, ~1,215 tokens.

Download SKILL.mdSave it as .claude/skills/find-skills/SKILL.md (or your agent's skills folder).

name: find-skills
description: Discover available skills in the builtin library by keyword.
allowed-tools: list_dir, read_file, bash
enabled: true
related-skills: skill-creator
license: MIT
author: Adapted from deer-flow (Bytedance, MIT)

Find Skills

This skill helps you discover skills available in Poirot's builtin library and install user-contributed skills.

When to Use (PROACTIVE — call before starting work)

Call this skill OR the skill_search tool when:

User asks for ANY specialized task (not just "find a skill")
You're about to start coding/research and haven't checked for relevant skills
Keywords in user message match skill categories: frontend/chart/diagram/github/debug/tdd/...

PROACTIVE CHECK (before starting work)

Identify task keywords (frontend, chart, github, debug, tdd, ...)
Call skill_search("<keywords>")
If matches found → read the SKILL.md → follow its workflow
If no matches → proceed with general capabilities

Common keywords → skill categories

Keyword	Likely skill
frontend / UI / React / Vue	frontend-design
chart / graph / visualization	chart-visualization
diagram / architecture	architecture-diagram
github / PR / code review	github-code-review / github-pr-workflow
debug / bug	systematic-debugging / python-debugpy
test / TDD	test-driven-development
plan / spike	plan / spike
simplify / refactor	simplify-code

Legacy When to Use (still valid)

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
Wants to search for tools, templates, or workflows
Mentions they wish they had help with a specific domain

Builtin skill library

Poirot ships a builtin library at:

poirot/backend/agents/skill/builtin_skills/
├── core/                    # meta-skills, loaded at agent startup
├── research/                # research & intelligence skills
├── software-development/    # coding & GitHub skills
├── creative/                # visualization & design skills
└── productivity/            # docs & office skills

Only core/ skills are auto-loaded at startup (registered as active). Skills under other categories are searchable but not auto-injected — use the skill_search tool or /skill search <query> command to find and load them on demand.

How to find a skill

bash

list_dir("poirot/backend/agents/skill/builtin_skills/")

Step 2: Search by keyword

Use bash with grep to find skills whose name or description matches:

bash

bash("grep -rl '<keyword>' poirot/backend/agents/skill/builtin_skills/ --include='SKILL.md'")

Or read a category directory and inspect each SKILL.md frontmatter:

bash

list_dir("poirot/backend/agents/skill/builtin_skills/research/")

Then read a candidate:

bash

read_file("poirot/backend/agents/skill/builtin_skills/research/deep-research/SKILL.md")

Show full SKILL.md (184 more words)Show less

Step 3: Activate a non-core skill

Non-core skills are not auto-loaded. To use one this turn:

Read its SKILL.md content
Follow its guidance for the current task
(Future: /skill search <query> will surface + inject matched skills automatically once the search tool is wired)

To permanently install a user skill from an external path:

/skill install <path> [name]

This copies it into skills/ (user skill storage, gitignored) and re-discovers.

Presenting options to the user

When you find relevant skills, present them with:

The skill name and what it does (from description frontmatter)
The category it lives in
Whether it needs explicit activation

Example:

I found a skill that might help. "deep-research" (research category) guides
multi-step web research with evidence cross-verification. It's not auto-loaded
— I'll follow its guidance for this task. Want me to proceed?

When no skills are found

If no builtin skill matches:

Acknowledge that no existing skill was found
Offer to help with the task directly using general capabilities
Suggest the user could create a new skill with /skill install or by authoring skills/<name>/SKILL.md (see the skill-creator skill)

Common categories

Category	Example keywords
research	arxiv, deep-research, literature, osint
software-development	debug, github, pr, codebase, subagent
creative	chart, diagram, frontend, visualization
productivity	docs, ppt, documentation
core	plan, debugging, tdd, review, skill

Files

Just SKILL.md in poirot/backend/agents/skill/builtin_skills/core/find-skills of HezaoHezao/poirot.

Open the folder on GitHubat commit 86bf279

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
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Find Skills this skillHezaoHezao/poirot	249	—	~1.2k	Automated safety check: Pass	MIT	2 mo ago
Triage IssuesClickHouse/clickhouse-java	1.6k	—	~904	Automated safety check: Pass	Apache-2.0	yesterday
Issue To Regression Testbrunosabot/streamline-card	269	—	~529	Automated safety check: Pass	MIT	4 mo ago
Nemoclaw Maintainer Analyze CI PerformanceNVIDIA/NemoClaw	23k	—	~644	Automated safety check: Pass	Apache-2.0	today
Reprovaadin/web-components	582	—	~1.3k	Automated safety check: Pass	None	yesterday
Fix Random CI Test Failuredotnet/macios	2.9k	—	~1.3k	Automated safety check: Pass	Custom licence	2 days ago

Similar skills

Triage Issues
ClickHouse/clickhouse-java
Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.
1.6k GitHub stars~904 tokensUpdated yesterday
Testing & QAAuto-check passed
Issue To Regression Test
brunosabot/streamline-card
A skill your agent uses when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix.
269 GitHub stars~529 tokensUpdated 4 mo ago
Testing & QAAuto-check passed
Nemoclaw Maintainer Analyze CI Performance
NVIDIA/NemoClaw
Official
Analyze retained NemoClaw CI timings for slow CLI tests, runner queues, or base-image publication.
23k GitHub stars~644 tokensUpdated today
Testing & QAAuto-check passed
Repro
vaadin/web-components
Reproduce a Vaadin web component bug from a GitHub issue in vaadin/web-components.
582 GitHub stars~1.3k tokensUpdated yesterday
Testing & QAAuto-check passed
Fix Random CI Test Failure
dotnet/macios
Official
Investigate and fix flaky/random CI test failures in dotnet/macios.
2.9k GitHub stars~1.3k tokensUpdated 2 days ago
Testing & QAAuto-check passed
Review
webern/cargo-readme
Reviews a GitHub pull request for correctness, architecture, security, backward compatibility, and test coverage.
385 GitHub stars~2k tokensUpdated 2 days ago
Testing & QAAuto-check: notes

Questions about Find Skills

What does Find Skills do?

Discover available skills in the builtin library by keyword. Find Skills is an agent skill from HezaoHezao/poirot. Discover available skills in the builtin library by keyword.

When should I use Find Skills?

Find Skills fits situations like: testing & QA work in your project.

How do I install Find Skills in Claude Code?

Run `npx skills add HezaoHezao/poirot --skill find-skills -a claude-code`. Or copy the skill folder (poirot/backend/agents/skill/builtin_skills/core/find-skills in HezaoHezao/poirot) 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 HezaoHezao/poirot --skill find-skills -a codex`. Or copy the skill folder (poirot/backend/agents/skill/builtin_skills/core/find-skills in HezaoHezao/poirot) 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 HezaoHezao/poirot --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?

SKILL.md names no scripts, command-line tools or credentials: Find Skills is instructions for the agent only. Its frontmatter pre-approves these tools: list_dir, read_file, bash.

Does Find Skills access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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 (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Find Skills use?

About 1.2k tokens (SKILL.md is roughly 4.9k 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: Triage Issues (ClickHouse/clickhouse-java, 1.6k stars), Issue To Regression Test (brunosabot/streamline-card, 269 stars), Nemoclaw Maintainer Analyze CI Performance (NVIDIA/NemoClaw, 23k stars) and Repro (vaadin/web-components, 582 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Find Skills?

HezaoHezao (a GitHub user) maintains it in HezaoHezao/poirot, which has 249 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on July 28, 2026.

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

Install Find Skills

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Find Skills

When to Use (PROACTIVE — call before starting work)

PROACTIVE CHECK (before starting work)

Common keywords → skill categories

Legacy When to Use (still valid)

Builtin skill library

How to find a skill

Step 1: List categories

Step 2: Search by keyword

Step 3: Activate a non-core skill

Presenting options to the user

When no skills are found

Common categories

Files

Compare with similar skills

Similar skills

More from HezaoHezao/poirot

Related

Questions about Find Skills