agentleFS
ulpi-ioulpi-io/browse/.agents/skills/find-agents/SKILL.md

find-agents

Skill15 starsChanged 8 months agoApache-2.0View on GitHub

Find, install, and manage AI agents across 43+ coding IDEs. Search the agentshq registry, install agents from GitHub repos or URLs, list/remove/update installed agents. Invoke via /find-agents or when user says "find an agent", "install agent", "search agents", "list agents", "remove agent", "update agents".

  • Reads credentials

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user asks to find agents, run the search and present results.

    line 42
  2. Very specific:

    Run npx agentshq find <query> with the user's keywords

    line 128
  3. Distinctive:

    Ask which agent(s) to install

    line 130
  4. Distinctive:

    Run the install command with appropriate flags

    line 131
  5. Very specific:

    Run npx agentshq add <source> with the appropriate source

    line 135
  6. Distinctive:

    If the user doesn't specify IDEs, the CLI will auto-detect installed IDEs and prompt

    line 136
  7. Distinctive:

    After install, confirm what was installed and where

    line 138
  8. Distinctive:

    Ask what kind of task they're working on (React, Laravel, testing, DevOps, etc.)

    line 142
  9. Very specific:

    Search with relevant keywords: npx agentshq find <keyword>

    line 143
  10. Very specific:

    If npx agentshq fails, check if Node.js >= 18 is available

    line 153
  11. Distinctive:

    If a git clone fails, check network connectivity and repo access

    line 154
  12. Distinctive:

    If no agents are found in a repo, suggest checking the repo has AGENT.md files

    line 155
  13. Very specific:

    If IDE detection finds nothing, suggest --ide <name> to specify manually

    line 156

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Find Agents

Full CLI wrapper for agentshq -- the package manager for AI coding agents.

When to Use

Activate this skill when the user:

  • Wants to find or search for agents ("find me a React agent", "search for testing agents")
  • Wants to install agents ("install the laravel expert agent", "add agents from owner/repo")
  • Wants to manage agents ("list my agents", "remove web-design", "update all agents", "check for updates")
  • Mentions agentshq, agent definitions, or AGENT.md files
  • Asks what agents are available or installed

Prerequisites

The agentshq CLI must be available. If it's not installed globally, use npx agentshq to run commands on-the-fly (no install needed).

Check availability:

npx agentshq --version

Commands Reference

Search for agents

# Interactive search (opens fzf-style picker)
npx agentshq find

# Search by keyword
npx agentshq find <query>

When the user asks to find agents, run the search and present results. If they pick one, install it.

Install agents

# From a GitHub repo (discovers all agents in the repo)
npx agentshq add <owner>/<repo>

# Install a specific agent from a repo
npx agentshq add <owner>/<repo>@<agent-name>

# From any git URL
npx agentshq add https://github.com/owner/repo

# From a local directory
npx agentshq add ./path/to/agents

# Install globally (user-level, available in all projects)
npx agentshq add <source> -g

# Install to specific IDEs
npx agentshq add <source> --ide claude-code cursor windsurf

# Install all agents to all IDEs without prompts
npx agentshq add <source> --all

# List available agents in a repo without installing
npx agentshq add <source> --list

List installed agents

# List project-level agents
npx agentshq list

# List global agents
npx agentshq list -g

# Filter by IDE
npx agentshq list --ide claude-code

# Machine-readable output
npx agentshq list --json

Remove agents

# Interactive removal (shows picker)
npx agentshq remove

# Remove specific agent
npx agentshq remove <agent-name>

# Remove from global scope
npx agentshq remove <agent-name> -g

# Remove all agents
npx agentshq remove --all

Check for updates

# Check which agents have updates available
npx agentshq check

# Update all agents to latest versions
npx agentshq update

Create a new agent

# Scaffold a new AGENT.md
npx agentshq init <name>

# Create in current directory
npx agentshq init

Behavior Guidelines

When searching for agents

  1. Run npx agentshq find <query> with the user's keywords
  2. Present the results clearly -- name, description, source
  3. Ask which agent(s) to install
  4. Run the install command with appropriate flags

When installing agents

  1. Run npx agentshq add <source> with the appropriate source
  2. If the user doesn't specify IDEs, the CLI will auto-detect installed IDEs and prompt
  3. For non-interactive installs (CI, scripts), suggest -y or --all flags
  4. After install, confirm what was installed and where

When the user is unsure what they need

  1. Ask what kind of task they're working on (React, Laravel, testing, DevOps, etc.)
  2. Search with relevant keywords: npx agentshq find <keyword>
  3. Recommend agents based on the results
  4. Offer to install their picks

Private repos

The CLI works with private repos using the same syntax. Privacy is automatic -- no telemetry or audit data is sent for private repos. The user just needs git access (SSH keys or GITHUB_TOKEN).

Error handling

  • If npx agentshq fails, check if Node.js >= 18 is available
  • If a git clone fails, check network connectivity and repo access
  • If no agents are found in a repo, suggest checking the repo has AGENT.md files
  • If IDE detection finds nothing, suggest --ide <name> to specify manually

Supported IDEs

The CLI supports 43+ IDEs. The most common ones:

IDEFormat
Claude Code.md with YAML frontmatter
CursorAGENTS.md sections
GitHub Copilot.agent.md
WindsurfAGENTS.md sections
CodexAGENTS.md sections
Gemini CLI.md with YAML frontmatter
Kiro.json
AmpAGENTS.md sections
Roo CodeAGENTS.md sections

Agents are automatically translated to each IDE's native format on install.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.