find-agents
Search, install, list, remove, update, or scaffold AI agents with the `agentshq` CLI across many coding CLIs and IDEs. Use when the user wants to discover agents, install them into specific clients, or manage an existing agent catalog.
What this skill does
<EXTREMELY-IMPORTANT> This skill changes the user's agent inventory and must stay explicit-user-only. Non-negotiable rules: 1. Verify `agentshq` availability before relying on it. 2. Be explicit about scope: project vs global, specific IDEs vs auto-detect. 3. Do not install or remove agents the user did not ask for. 4. Confirm ambiguous install targets before making changes. 5. Report exactly what was added, removed, or updated. </EXTREMELY-IMPORTANT> # 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: 1. the resolved action 2. project/global scope 3. target IDEs or CLIs 4. the agents found or changed 5. any follow-up steps the user should know about
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.