Non-negotiable rules:
- Verify
agentshq availability before relying on it.
- Be explicit about scope: project vs global, specific IDEs vs auto-detect.
- Do not install or remove agents the user did not ask for.
- Confirm ambiguous install targets before making changes.
- Report exactly what was added, removed, or updated.
Find Agents
Inputs
$request: Search terms, repo source, or management intent such as list, remove, or update
Goal
Use agentshq to help the user:
- discover relevant agents
- install agents into one or more CLIs or IDEs
- list current inventory
- remove or update installed agents
- scaffold a new agent when asked
Step 0: Verify runtime prerequisites
Check:
- Node.js availability
npx agentshq --version
If the CLI is unavailable, explain the blocker and stop.
Success criteria: agentshq can be invoked from the current environment.
Step 1: Resolve the user's intent
Determine whether the user wants to:
- search
- install
- list
- remove
- update
- scaffold
Also resolve:
- project vs global scope
- target IDEs/CLIs if specified
- source repo, URL, or local path if installing
If those details are ambiguous, ask before mutating anything.
Success criteria: The exact agentshq action is clear before execution.
Step 2: Run the narrowest relevant command
Command Reference
| Action |
Command |
Key Flags |
| Search |
npx agentshq find [query] |
interactive picker when no query given |
| Install from repo |
npx agentshq add <owner>/<repo> |
@<agent-name> for specific agent |
| Install from URL |
npx agentshq add <url> |
also works with local paths |
| Install scope |
|
-g for global, --ide <name> ... for specific IDEs |
| Install options |
|
--all for all agents to all IDEs, --list to preview |
| List installed |
npx agentshq list |
-g for global, --ide <name>, --json |
| Remove |
npx agentshq remove [name] |
-g for global, --all for all agents |
| Check updates |
npx agentshq check |
|
| Apply updates |
npx agentshq update |
|
| Scaffold new |
npx agentshq init [name] |
|
When installing, respect:
- explicit
--ide ... choices when the user gave them
-g only when the user asked for global scope
--list when the user wants to inspect a source before installing
Supported IDEs
The CLI supports 43+ IDEs. Common ones:
| IDE |
Format |
| Claude Code |
.md with YAML frontmatter |
| Cursor |
AGENTS.md sections |
| GitHub Copilot |
.agent.md |
| Windsurf |
AGENTS.md sections |
| Codex |
AGENTS.md sections |
| Gemini CLI |
.md with YAML frontmatter |
| Kiro |
.json |
| Amp |
AGENTS.md sections |
| Roo Code |
AGENTS.md sections |
Agents are automatically translated to each IDE's native format on install.
Success criteria: The command matches the user's intent and scope exactly.
Step 3: Report the result clearly
After execution, report:
- what command ran
- which agents matched or changed
- which clients/IDEs were targeted
- any next steps such as authentication, reload, or restart
When searching, present the most relevant results instead of dumping raw output.
Success criteria: The user can immediately decide what to do next.
Guardrails
- Do not run this skill proactively.
- Do not install globally unless the user asked for global scope.
- Do not remove or update agents without explicit user intent.
- Do not guess target IDE names when the user clearly cares about a specific client.
- Remember that
agentshq can translate one source agent into multiple client formats; report that clearly.
Output Contract
Report:
- the resolved action
- project/global scope
- target IDEs or CLIs
- the agents found or changed
- any follow-up steps the user should know about
1---
2name: find-agents
3version: 2.0.0
4description: |
5 Discover, install, and manage AI agents across 43+ coding CLIs and IDEs from ONE source —
6 auto-translated to each client's native format, not hand-ported — with the `agentshq` CLI: `find`,
7 `add`, `list`, `remove`, `check`/`update`, and `init` scaffolding, scoped by `-g` (global) and
8 `--ide` targets. Explicit-user-only and precise: it never installs, removes, or updates agents the
9 user didn't ask for. Use to find agents or manage an existing agent catalog.
10allowed-tools:
11 - AskUserQuestion
12 - Bash
13 - Read
14disable-model-invocation: true
15user-invocable: true
16argument-hint: "[search query, source repo, or management action]"
17arguments:
18 - request
19when_to_use: |
20 Use only when the user explicitly asks to find, install, list, remove, update, or scaffold agents.
21 Examples: "/find-agents react reviewer", "install agents from owner/repo", "list my installed
22 agents", "update all agents". Do NOT use proactively, do NOT install globally unless global scope was
23 requested, and do NOT guess target IDEs when the user named a specific client; confirm scope and
24 target before mutating the agent inventory.
25effort: high
26metadata:
27 source: https://skillmd.com/skills/ulpi-io/find-agents
28---
29
30<EXTREMELY-IMPORTANT>
31This skill changes the user's agent inventory and must stay explicit-user-only.
32
33Non-negotiable rules:
341. Verify `agentshq` availability before relying on it.
352. Be explicit about scope: project vs global, specific IDEs vs auto-detect.
363. Do not install or remove agents the user did not ask for.
374. Confirm ambiguous install targets before making changes.
385. Report exactly what was added, removed, or updated.
39</EXTREMELY-IMPORTANT>
40
41# Find Agents
42
43## Inputs
44
45- `$request`: Search terms, repo source, or management intent such as `list`, `remove`, or `update`
46
47## Goal
48
49Use `agentshq` to help the user:
50
51- discover relevant agents
52- install agents into one or more CLIs or IDEs
53- list current inventory
54- remove or update installed agents
55- scaffold a new agent when asked
56
57## Step 0: Verify runtime prerequisites
58
59Check:
60
61- Node.js availability
62- `npx agentshq --version`
63
64If the CLI is unavailable, explain the blocker and stop.
65
66**Success criteria**: `agentshq` can be invoked from the current environment.
67
68## Step 1: Resolve the user's intent
69
70Determine whether the user wants to:
71
72- search
73- install
74- list
75- remove
76- update
77- scaffold
78
79Also resolve:
80
81- project vs global scope
82- target IDEs/CLIs if specified
83- source repo, URL, or local path if installing
84
85If those details are ambiguous, ask before mutating anything.
86
87**Success criteria**: The exact `agentshq` action is clear before execution.
88
89## Step 2: Run the narrowest relevant command
90
91### Command Reference
92
93| Action | Command | Key Flags |
94|--------|---------|-----------|
95| Search | `npx agentshq find [query]` | interactive picker when no query given |
96| Install from repo | `npx agentshq add <owner>/<repo>` | `@<agent-name>` for specific agent |
97| Install from URL | `npx agentshq add <url>` | also works with local paths |
98| Install scope | | `-g` for global, `--ide <name> ...` for specific IDEs |
99| Install options | | `--all` for all agents to all IDEs, `--list` to preview |
100| List installed | `npx agentshq list` | `-g` for global, `--ide <name>`, `--json` |
101| Remove | `npx agentshq remove [name]` | `-g` for global, `--all` for all agents |
102| Check updates | `npx agentshq check` | |
103| Apply updates | `npx agentshq update` | |
104| Scaffold new | `npx agentshq init [name]` | |
105
106When installing, respect:
107
108- explicit `--ide ...` choices when the user gave them
109- `-g` only when the user asked for global scope
110- `--list` when the user wants to inspect a source before installing
111
112### Supported IDEs
113
114The CLI supports 43+ IDEs. Common ones:
115
116| IDE | Format |
117|-----|--------|
118| Claude Code | `.md` with YAML frontmatter |
119| Cursor | `AGENTS.md` sections |
120| GitHub Copilot | `.agent.md` |
121| Windsurf | `AGENTS.md` sections |
122| Codex | `AGENTS.md` sections |
123| Gemini CLI | `.md` with YAML frontmatter |
124| Kiro | `.json` |
125| Amp | `AGENTS.md` sections |
126| Roo Code | `AGENTS.md` sections |
127
128Agents are automatically translated to each IDE's native format on install.
129
130**Success criteria**: The command matches the user's intent and scope exactly.
131
132## Step 3: Report the result clearly
133
134After execution, report:
135
136- what command ran
137- which agents matched or changed
138- which clients/IDEs were targeted
139- any next steps such as authentication, reload, or restart
140
141When searching, present the most relevant results instead of dumping raw output.
142
143**Success criteria**: The user can immediately decide what to do next.
144
145## Guardrails
146
147- Do not run this skill proactively.
148- Do not install globally unless the user asked for global scope.
149- Do not remove or update agents without explicit user intent.
150- Do not guess target IDE names when the user clearly cares about a specific client.
151- Remember that `agentshq` can translate one source agent into multiple client formats; report that clearly.
152
153## Output Contract
154
155Report:
156
1571. the resolved action
1582. project/global scope
1593. target IDEs or CLIs
1604. the agents found or changed
1615. any follow-up steps the user should know about