CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

62

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/builtin/finding-agents/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, largely executable reference for a simple CLI skill: concrete commands, a full options table, and covering examples. Its weaknesses are redundant duplication between Common Patterns and Examples, and a muddled final workflow whose last step does not match the state it receives (an agent_id, not a partial name).

Suggestions

Merge the Examples section into Common Patterns (or keep one) to eliminate the repeated commands and cut the token cost of the skill.

Fix the topic workflow's final step to act on the agent_id actually obtained, e.g., a concrete command like "letta agents list --name <partial-name>" or a documented agents-get endpoint instead of the vague "use the agent_id directly in the Letta API".

Promote "Finding Agents by Topic" to its own top-level section (or nest it under CLI Usage) rather than burying it beneath "## Output", since it is a workflow, not an output-field description.

DimensionReasoningScore

Conciseness

The Common Patterns and Examples sections repeat the same commands verbatim ("letta agents list", "--shared", "--tags \"origin:letta-code\"\" each appear twice), and filler like "This is useful when the user is looking for agents they've worked with in Letta Code CLI sessions" adds little. Mostly efficient but clearly could be tightened by merging the duplicated sections, matching the anchor of 3 rather than the minor-trim anchor of 4.

3 / 5

Actionability

Commands are copy-paste ready with a complete options table and six concrete examples covering common cases. The gap is in the topic workflow, where step 3 suggests "letta agents list --query \"partial-name\"" even though the user holds an agent_id, and "use the agent_id directly in the Letta API" gives no executable command — minor gaps that keep it below the fully-executable anchor of 5.

4 / 5

Workflow Clarity

The core single action (letta agents list) is unambiguous, and the topic workflow is a numbered 3-step sequence. Step 3's guidance mismatches the workflow state (querying by partial name when an agent_id is in hand), a minor gap; operations are read-only so the destructive/batch validation cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is organized into clear sections with nothing nested more than one level deep, which is appropriate for a skill of this size. Minor organizational gaps remain: "Finding Agents by Topic" is oddly nested as a subsection under "## Output", and the Examples section largely duplicates Common Patterns instead of pointing to it.

4 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-formed description with an explicit what and a concrete multi-clause Use-when trigger list. Its main weaknesses are limited action variety (essentially one find/list capability) and slightly generic agent vocabulary that omits the product name and common phrasings like "list agents".

Suggestions

Broaden the capability statement beyond a single action, e.g., "Find and list other agents on the same Letta server, search them by name or tags, and inspect their details".

Include the product name (Letta) and the natural phrase "list agents" in the trigger clause so users asking to "list my Letta agents" match unambiguously.

DimensionReasoningScore

Specificity

"Find other agents on the same server" names the domain and one concrete action, with by-name and by-tags as modes of that same action rather than distinct capabilities. It matches the anchor for 1-2 concrete actions without comprehensive coverage, and does not list several separate actions that would justify a 4.

3 / 5

Completeness

It explicitly answers both parts: the what ("Find other agents on the same server") and the when ("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") with three concrete trigger clauses, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural phrases like "asks about other agents", "migrate memory from another agent", and "find an agent by name or tags" are phrasing a user would plausibly say. A few natural terms are missing (e.g., "list agents", "Letta", "search agents"), keeping it below the comprehensive-synonyms anchor of 5.

4 / 5

Distinctiveness Conflict Risk

The niche (agent discovery and memory migration on a shared server) is fairly distinct with dedicated triggers. However, generic terms like "agents" and "same server" without the product name leave minor overlap risk with other agent-management skills, so it does not fully reach the minimal-conflict anchor of 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

letta-ai/letta-code

Path

src/skills/builtin/finding-agents/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.