In short:
ak-find-skillspicks one main skill from the AgentKit skills you have installed, or finds an outside skill with the Skills CLI (npx skills) and installs it when you agree. If it finds nothing, it says so plainly and carries on with your task using what is already available. It does not install anything you have not asked for, and it does not go skill hunting for ordinary work like writing a component or reviewing a PR.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you need a capability and do not know which skill covers it, when you want to find, compare or install a skill, or when you have confirmed that a capability is missing. You do not need it when the task is already clear, like writing a React component or reviewing a PR: just hand over the task and your installed skills will handle it.
flowchart LR
A["Need a new capability"] --> B["ak-find-skills"]
B --> C["Matching installed AgentKit skill"]
B --> D["Outside skill + install command"]
D --> E["Installed when you want it"]
B --> F["Nothing found, carry on with what is available"]Three things to know:
| Point | Question | Example |
|---|---|---|
| Installed or outside | Are you choosing among AgentKit skills you already have, or looking for a new one? | "Which skill do I use for a security audit?" takes the installed path. "Find a skill that writes changelogs" takes the Skills CLI path. |
| Do you really need to search | Did you clearly ask to find, compare or install a skill, or confirm a missing capability? | "Is there a skill for Playwright?" is worth a search. "Help me write a React component" gets done right away with the skills you have. |
| Install scope | Install for this project or for your whole machine? | By default it goes by your request and the current project. It only uses -g when you clearly say you want it machine-wide. |
Sample prompt to find an outside skill:
/ak-find-skills Find a skill that writes a changelog from commit history
for the <project name> project. Just list them, do not install yet.This skill has no flags.
Below is the detailed version: the run flow, 4 situations with prompts, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-find-skills: find the right skill, installed or new" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-find-skills". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-find-skills
