find-skills

Search the agent skills ecosystem to discover and install skills that extend AI coding agent capabilities. Use when user asks "how do I do X" (X being a common task), "find a skill for X", "is there a skill that can...", or expresses interest in extending agent capabilities. Triggers on "find a skill", "install a skill", "skill for [task]", "can you do X", "I need help with [domain]", "how do I [task]". Do NOT use when user has explicitly asked to proceed without a skill, or when the task is better handled by agent's built-in capabilities (file operations, git, basic coding).

Ir para a instalação

Repositório: EliasOulkadi/shokunin
Última atividade na origem: 19 de maio de 2026 às 16:05
Idioma detectado do SKILL.md: inglês
Estrelas: 110
Forks: 14

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/EliasOulkadi/shokunin --skill find-skills

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

I found a skill that might help! "react-best-practices" provides React/Next.js performance optimization guidelines from Vercel Engineering. (185K installs) To install: npx skills add vercel-labs/agent-skills@react-best-practices Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices

name	find-skills
description	Search the agent skills ecosystem to discover and install skills that extend AI coding agent capabilities. Use when user asks "how do I do X" (X being a common task), "find a skill for X", "is there a skill that can...", or expresses interest in extending agent capabilities. Triggers on "find a skill", "install a skill", "skill for [task]", "can you do X", "I need help with [domain]", "how do I [task]". Do NOT use when user has explicitly asked to proceed without a skill, or when the task is better handled by agent's built-in capabilities (file operations, git, basic coding).
triggers	["find a skill","install a skill","skill for","is there a skill","how do I","search skills","discover skills","skill ecosystem","available skills","list skills"]
negatives	["create a skill","write a skill","edit a skill","skill development"]
license	MIT
compatibility	opencode
metadata	{"workflow":"tooling","audience":"developers","version":"1.0.0"}

name	find-skills
description	Search the agent skills ecosystem to discover and install skills that extend AI coding agent capabilities. Use when user asks "how do I do X" (X being a common task), "find a skill for X", "is there a skill that can...", or expresses interest in extending agent capabilities. Triggers on "find a skill", "install a skill", "skill for [task]", "can you do X", "I need help with [domain]", "how do I [task]". Do NOT use when user has explicitly asked to proceed without a skill, or when the task is better handled by agent's built-in capabilities (file operations, git, basic coding).
triggers	["find a skill","install a skill","skill for","is there a skill","how do I","search skills","discover skills","skill ecosystem","available skills","list skills"]
negatives	["create a skill","write a skill","edit a skill","skill development"]
license	MIT
compatibility	opencode
metadata	{"workflow":"tooling","audience":"developers","version":"1.0.0"}

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

Dimension	What to check	Red flags
Maintenance	Last update < 6 months?	No updates in 1+ year
Depth	Has examples, not just description?	Single paragraph, no code
Compatibility	Supports your agent?	Only tested on one platform
Specificity	Solves your exact problem?	Generic content without actionable patterns

Cause	Fix
`npx skills find` returns zero results for a valid query	Query may be too specific or use jargon not in skill descriptions. Broaden to the domain term (e.g., "testing" instead of "jest snapshot serializers"). Try 2-3 synonym variations.
`npx skills add` fails with "package not found"	Verify the package spec format: `<owner>/<repo>@<skill-name>`. Check https://skills.sh/ for the exact package path. GitHub rate limits may apply — retry after 60s.
Installed skill does not activate (agent ignores it)	Skill description might not match the user's phrasing. Check the skill's `description` field in its SKILL.md frontmatter. It should use trigger phrases the user naturally says.
`npx skills check` reports updates but `add` re-installs same version	The CLI caches resolution metadata. Run `npx skills check --refresh` to force re-resolution. If still stuck, uninstall with `npx skills remove <package>` and re-add.
Skills website (skills.sh) is unreachable	GitHub Pages may be down or DNS blocked. Fall back to direct GitHub search: `gh search repos --topic agent-skill <query>`. Present results from the CLI search as primary alternative.
User requests a skill for a niche domain with no ecosystem coverage	No skill exists yet. Offer to help directly. Propose creating a custom skill with `npx skills init`. Show the skill-creator workflow if the user wants to build and publish it.
Skill install conflicts with an existing skill of the same name	Two skills share a namespace. The CLI will refuse to overwrite. Uninstall the old one first: `npx skills remove <old-package>`. Verify the old skill isn't needed before removing.

find-skills

Opções de instalação

Revise os arquivos de origem

What is the Skills CLI?

Workflow

Step 1: Understand what they need

Step 2: Check the leaderboard first

Step 3: Search

Step 4: Verify quality

Step 5: Present options

Step 6: Install (if user agrees)

What is the Skills CLI?

Workflow

Step 1: Understand what they need

Step 2: Check the leaderboard first

Step 3: Search

Step 4: Verify quality

Step 5: Present options

Step 6: Install (if user agrees)

Common Categories

Skill Quality Assessment

Fallback: When No Skills Found

Error Handling

Skill Discovery Methodology

Finding skills in the ecosystem

Quality Evaluation Framework

Installation Troubleshooting

Checklist

Sources

Anti-Patterns

Error	Cause	Fix
`SKILL.md not found`	Directory missing from registry	Check if skill exists at source repository
`permission denied`	Plugin directory not writable	`chmod 755 ~/.config/opencode/skills/`
`skill already installed`	Version conflict or duplicate	`npx skills remove <name>` then reinstall
`trigger not matching`	Description too generic or too narrow	Edit frontmatter `description:` field and re-test
`npm ERR!` during install	npm registry issue or network	Retry. If persistent, clone manually from GitHub

Pattern	Problem	Fix
Recommending a skill without checking install count or maintenance status	Abandoned skills with 0 installs waste the user's time and may contain broken or outdated instructions.	Check install count (>1K preferred), last update (<6 months), and source reputation before presenting.
Installing a skill the user didn't explicitly agree to install	Skills modify agent behavior. Installing without consent breaks trust.	Always present the skill first, wait for explicit confirmation, then install. Never auto-install.
Searching only once and giving up when zero results appear	First query may use the wrong terminology or be too narrow.	Try 2-3 synonym variations and broader domain terms before concluding no skill exists.
Suggesting a skill when the task is trivial and built-in capabilities suffice	Overhead of installing and loading a skill for a 30-second task wastes tokens and attention.	Only suggest skills for recurring patterns, complex domains, or tasks the user explicitly flagged as needing a skill.
Evaluating skill quality by description alone without reading the actual content	Descriptions are marketing. The SKILL.md content determines actual usefulness.	After identifying candidates, read the skill's SKILL.md on GitHub before presenting. Check for concrete patterns, code examples, and workflow steps.
Assuming a skill works on all platforms when it's only tested on one	A skill written for Claude Code may fail on OpenCode or Gemini CLI due to tool name differences.	Check the skill's `compatibility` metadata field. If missing, test the first step manually before recommending.

find-skills

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

What is the Skills CLI?

Workflow

Step 1: Understand what they need

Step 2: Check the leaderboard first

Step 3: Search

Step 4: Verify quality

Step 5: Present options

Step 6: Install (if user agrees)

What is the Skills CLI?

Workflow

Step 1: Understand what they need

Step 2: Check the leaderboard first

Step 3: Search

Step 4: Verify quality

Step 5: Present options

Step 6: Install (if user agrees)

Common Categories

Skill Quality Assessment

Fallback: When No Skills Found

Error Handling

Skill Discovery Methodology

Finding skills in the ecosystem

Quality Evaluation Framework

Installation Troubleshooting

Checklist

Sources

Anti-Patterns