Finding Agents
Find other agents on the same server. Use when the user asks about other agents, wants to migrate memory from another agent, or needs to find an agent by name or tags.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Finding Agents when an AI agent needs a reusable SKILL.md workflow for this job: Find other agents on the same server. Use when the user asks about other agents, wants to migrate memory from another agent, or needs to find an agent by name or tags.
When not to use it
Skip Finding Agents when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/finding-agents # Save SKILL.md to ~/.claude/skills/finding-agents/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/finding-agents/SKILL.md. For a shared project, commit the folder at .claude/skills/finding-agents/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Finding Agents skill for this task: User asks about other agents they have. Confirm any required inputs or files before making changes.
What supports this recommendation?
83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 92/100
- Practical detail
- 92/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Finding Agents
This skill helps you find other agents on the same Letta server.
## When to Use This Skill
- User asks about other agents they have - User wants to find a specific agent by name - User wants to list agents with certain tags - You need to find an agent ID for memory migration - You found an agent_id via message search and need details about that agent
## CLI Usage
```bash letta agents list [options] ```
### Options
| Option | Description | |--------|-------------| | `--name <name>` | Exact name match | | `--query <text>` | Fuzzy search by name | | `--tags <tag1,tag2>` | Filter by tags (comma-separated) | | `--match-all-tags` | Require ALL tags (default: ANY) | | `--include-blocks` | Include agent.blocks in response | | `--shared` | List agents shared with the current user | | `--limit <n>` | Max results (default: 20) |
## Common Patterns
### Finding Letta Code Agents
Agents created by Letta Code are tagged with `origin:letta-code`. To find only Letta Code agents:
```bash letta agents list --tags "origin:letta-code" ```
This is useful when the user is looking for agents they've worked with in Letta Code CLI sessions.
### Finding All Accessible Agents
List agents owned by the current user, then list agents shared with them:
```bash letta agents list letta agents list --shared ```
Use `--query <text>` with either command to search by name.
## Examples
**List all agents (up to 20):** ```bash letta agents list ```
**Find agent by exact name:** ```bash letta agents list --name "ProjectX-v1" ```
**Search agents by name (fuzzy):** ```bash letta agents list --query "project" ```
**Find only Letta Code agents:** ```bash letta agents list --tags "origin:letta-code" ```
**Find agents with multiple tags:** ```bash letta agents list --tags "frontend,production" --match-all-tags ```
**Include memory blocks in results:** ```bash letta agents list --query "project" --include-blocks ```
## Output
Returns the raw API response with full agent details. Key fields: - `id` - Agent ID (e.g., `agent-abc123`) - `name` - Agent name - `description` - Agent description - `tags` - Agent tags - `blocks` - Memory blocks (if `--include-blocks` used)
### Finding Agents by Topic
If you need to find which agent worked on a specific topic:
1. Search messages across all agents: ```bash letta messages search --query "topic" --all-agents --limit 10 ``` 2. Note the `agent_id` values from matching messages 3. Get agent details: ```bash letta agents list --query "partial-name" ``` Or use the agent_id directly in the Letta API
Intended uses
- User asks about other agents they have
- User wants to find a specific agent by name
- User wants to list agents with certain tags
- You need to find an agent ID for memory migration
- You found an agentid via message search and need details about that agent
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.