CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

find-skills

Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/teamharness/skills/agent/find-skills/SKILL.md

The canonical home for this skill is find-skills in agentscope-ai/AgentTeams

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is a well-structured, actionable guide with a clearly sequenced search-then-install workflow and an appropriately minimal one-file bundle. Its main weakness is token efficiency: several peripheral sections (security assurances, search tips, CLI conceptual intro, trigger restatements) add tokens without adding capability Claude doesn't already have.

Suggestions

Delete the "Security Assurance" and "Tips for Effective Searches" sections and trim "What is the Skills CLI?" to one line — the generic assurance and search basics (e.g., "use specific keywords") explain things Claude already knows and add pure token cost.

Cut the "When to Use This Skill" bullets that restate the description's triggers, keeping only the market-import phrasings ("import xxx skill from market") that add new trigger information.

Unify the command surface: use the resolved "${FIND_SKILLS_SCRIPT}" wrapper (or the `skills` CLI) consistently, and make the sample search output use the resolved variable instead of a hardcoded path, matching the skill's own advice against hardcoded container paths.

DimensionReasoningScore

Conciseness

The operational core (script resolution, commands, Steps 1-4) is efficient, but several sections pad the token budget: "Security Assurance" ("Worker is completely isolated and cannot access any admin's personal sensitive data"), "Tips for Effective Searches" ("'react testing' is better than just 'testing'"), the conceptual explanation of what the Skills CLI/skills are, and a "When to Use This Skill" list that largely duplicates the description's triggers. This is "mostly efficient with some unnecessary explanation" (anchor 3) rather than the several padded sections of anchor 2, since every operational section still carries concrete content.

3 / 5

Actionability

The bash block that resolves FIND_SKILLS_SCRIPT is fully executable, and find/install commands plus example user queries and example responses are copy-paste ready. Minor gaps keep it below anchor 5: the command surface is inconsistent (the wrapper script for find/install vs. bare `skills check`/`skills update` for maintenance), and the sample search output hardcodes "./skills/find-skills/scripts/agentteams-find-skill.sh install <skill>" while the skill itself warns against hardcoded container paths.

4 / 5

Workflow Clarity

Steps 1-4 (understand the need, search, present options, offer to install) are clearly sequenced with a Step 2A branch for direct market imports and an error-avoidance checkpoint ("If the provided name looks ambiguous or you are not sure about the exact package name, search first"). It falls short of anchor 5 because there is no post-install verification (e.g., confirming the skill is installed/available), but installs are not destructive or batch operations, so no cap applies.

4 / 5

Progressive Disclosure

Scored against the actual bundle: one script (scripts/agentteams-find-skill.sh) referenced one level deep and clearly signaled both in the resolution block and in "Skill Resources" ("agentteams-find-skill.sh is the resource that belongs to this skill"), with well-organized headers, no nested references, and no large content inlined that belongs in a separate file. This matches anchor 5's clear overview with well-signaled one-level-deep references.

5 / 5

Total

16

/

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 strong description that clearly and explicitly states both what the skill does and when to use it, in third-person voice with no fluff. Its main gaps are modest: only two capabilities are named, and a few natural user phrasings (e.g., "find a skill", "market") are absent.

DimensionReasoningScore

Specificity

"Discover and install agent skills from the open ecosystem" names the domain plus exactly two concrete actions (discover, install), matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because no further capabilities (browse, update, create skills) are listed, and not a 2 because the actions stated are concrete rather than generic.

3 / 5

Completeness

It explicitly answers both questions: the "what" is "Discover and install agent skills from the open ecosystem" and the "when" is a concrete "Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task". Both are explicit with concrete trigger situations, matching anchor 5 rather than anchor 4's weaker 'when'.

5 / 5

Trigger Term Quality

Natural phrases like "unfamiliar domain, framework, or workflow", "searching for skills", and "install" give good keyword coverage, but common user phrasings such as "find a skill for X", "is there a skill for", or "market/plugin" are missing. This sits above anchor 3 (missing common variations) but short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Skill discovery/installation is a clear niche unlikely to trigger for the wrong skill, but the trigger "unfamiliar domain, framework, or workflow that you lack specialized knowledge about" is broad and could fire in almost any knowledge-gap situation. Mostly distinct with minor overlap risk fits anchor 4; anchor 5 would require tighter, uniquely-owned triggers.

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

agentscope-ai/AgentTeams

Path

plugins/teamharness/skills/agent/find-skills/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.