/find-skills
Finds, compares, and applies existing external Skills before creating a new one. Use when the user asks to find a Skill, search skills.sh, recommend an existing Skill, or install/apply a GitHub or skills.sh Skill.
$ npx -y skills add apm-studio/apm-studio --skill find-skills --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/find-skills
Context preview
The summary Claude sees to decide when to auto-load this skill.
Finds, compares, and applies existing external Skills before creating a new one. Use when the user asks to find a Skill, search skills.sh, recommend an existing Skill, or install/apply a GitHub or skills.sh Skill.
SKILL.md
find-skills.SKILL.mdname: find-skills
description: Finds, compares, and applies existing external Skills before creating a new one. Use when the user asks to find a Skill, search skills.sh, recommend an existing Skill, or install/apply a GitHub or skills.sh Skill.
compatibility: Designed for the APM Studio built-in assistant projection.
Find Skills
Use this skill when the user likely wants an existing external skill, not a brand-new local Skill from scratch.
Intent Split
- If the user wants a new Skill draft, an updated `SKILL.md`, or custom local Skill files, use `studio-assistant-skill-creator-guide` instead.
- If the user wants to search, compare, recommend, install, or apply an existing skill, use this skill.
- If the message mixes create and find/apply intent, ask one short clarifying question before mutating.
Search Order
- Prefer installed local matches first.
- Then consider APM Studio registry matches.
- Then consider `skills.sh` or GitHub Skill candidates.
- Treat `skills.sh` hints as candidates, not guarantees.
Recommendation Bar
- Prefer official or well-known sources when functionality is similar.
- Prefer higher-install candidates over obscure ones when they solve the same problem.
- Tell the user why a candidate fits in one short sentence.
- If a candidate has very low installs or an unfamiliar source, say so plainly.
Security Rule
- Before recommending installation or application of a `skills.sh` or GitHub skill, warn briefly that third-party skills should be reviewed before use.
- Tell the user to check the source repository, maintainer reputation, install count, and actual `SKILL.md` contents.
- Do not auto-install an external skill when the exact candidate is still ambiguous.
- If the user explicitly names the exact skill and wants to apply it, you may proceed after a short security notice.
Apply In Studio
- Recommend the exact GitHub or `skills.sh` source for the user to import through Import.
- If the source is still ambiguous, ask the user to pick the exact skill before changing the workspace.
Read more
name: find-skills description: Finds, compares, and applies existing external Skills before creating a new one. Use when the user asks to find a Skill, search skills.sh, recommend an existing Skill, or install/apply a GitHub or skills.sh Skill. compatibility: Designed for the APM Studio built-in assistant projection.
Find Skills
Use this skill when the user likely wants an existing external skill, not a brand-new local Skill from scratch.
Intent Split
- If the user wants a new Skill draft, an updated `SKILL.md`, or custom local Skill files, use `studio-assistant-skill-creator-guide` instead.
- If the user wants to search, compare, recommend, install, or apply an existing skill, use this skill.
- If the message mixes create and find/apply intent, ask one short clarifying question before mutating.
Search Order
- Prefer installed local matches first.
- Then consider APM Studio registry matches.
- Then consider `skills.sh` or GitHub Skill candidates.
- Treat `skills.sh` hints as candidates, not guarantees.
Recommendation Bar
- Prefer official or well-known sources when functionality is similar.
- Prefer higher-install candidates over obscure ones when they solve the same problem.
- Tell the user why a candidate fits in one short sentence.
- If a candidate has very low installs or an unfamiliar source, say so plainly.
Security Rule
- Before recommending installation or application of a `skills.sh` or GitHub skill, warn briefly that third-party skills should be reviewed before use.
- Tell the user to check the source repository, maintainer reputation, install count, and actual `SKILL.md` contents.
- Do not auto-install an external skill when the exact candidate is still ambiguous.
- If the user explicitly names the exact skill and wants to apply it, you may proceed after a short security notice.
Apply In Studio
- Recommend the exact GitHub or `skills.sh` source for the user to import through Import.
- If the source is still ambiguous, ask the user to pick the exact skill before changing the workspace.
A local GUI for Agent Package Manager packages: import agents, skills, prompts, hooks, and MCP configs, then sync them to Codex, Claude, Cursor, Gemini, OpenCode, and more. APM Studio is the visual layer for the APM ecosystem.
Repo: apm-studio/apm-studio
Other skills on apm-studio.
- /studio-assistant-action-surface-guide
Lists the exact APM Assistant apply_studio_actions mutation surface, field rules, ref ordering, and payload self-checks. Use before emitting or validating any APM Studio mutation tool call.
Open skill - /studio-assistant-agent-guide
Helps design or revise APM Studio Agents with strong role focus, Skill/MCP/model choices, and Team participant readiness. Use for Agent creation, Agent updates, role design, and participant-quality decisions. For exact payload fields, load studio-assistant-action-surface-guide.
Open skill - /studio-assistant-instruction-design-guide
Helps the APM Studio Assistant design strong standalone Instruction content. Use when deciding what belongs in a project/file rule, how concise it should be, and how to express durable coding guidance.
Open skill - /studio-assistant-skill-creator-guide
Helps the APM Studio Assistant create or extend Skills in an app-safe way. Use when the user wants a new Skill, a better SKILL.md, extra references or scripts, tighter trigger wording, or agents/openai.yaml metadata inside a Skill draft folder.
Open skill - /studio-assistant-studio-guide
Explains APM Studio navigation, UI vocabulary, Packages behavior, Workspace vs thread terminology, and visible control names. Use for product-help questions. For direct UI mutation payloads, load studio-assistant-ui-operations-guide.
Open skill - /studio-assistant-team-guide
Explains the current APM Studio Team contract: participants, relations, subscriptions, teamRules, safety, and package-safe field boundaries. Use for Team contract, relation, subscription, and runtime guardrail questions. For role split/topology decisions, load
Open skill