CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentlas-search

Search Agentlas Cloud and Hub agent candidates without invoking.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./kimi/skills/agentlas-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplarily lean delegation stub: it resolves the target file path precisely, defines argument handling, and includes an anti-drift guardrail ("do not improvise a separate workflow and do not summarize from memory"). Its only structural weakness is total dependence on an external sibling file with no guidance for handling its absence.

DimensionReasoningScore

Conciseness

The ~10-line body is lean and efficient with zero padding: it states the delegation target, the exact path resolution, and the argument mapping without explaining anything Claude already knows. Every token earns its place, matching anchor 5.

5 / 5

Actionability

Guidance is concrete for an instruction-only skill — exact relative path "../hep-search/SKILL.md", the instruction to read and follow it exactly, and the argument rule "treating everything typed after /skill:agentlas-search as that command's request". The minor gap is that all executable domain content lives in an external sibling file with no fallback if it is absent, fitting anchor 4 rather than 5.

4 / 5

Workflow Clarity

The single task is unambiguous: locate the sibling skill directory, read its SKILL.md, follow it exactly, and pass the user's request through. The simple-skill exception applies (no destructive or batch operations), so a clear single-purpose instruction earns 5.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and a single clearly-signaled, one-level-deep reference (the sibling hep-search/SKILL.md), which is exactly the well-organized, easy-to-navigate structure the rubric rewards.

5 / 5

Total

19

/

20

Passed

Description

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

The description is concise and clearly scoped to a distinct niche, but it only states a single action and provides no trigger guidance for when the skill should be used. It reads as a capable one-line summary rather than a complete activation spec.

Suggestions

Add an explicit 'when' clause, e.g. "Use when the user wants to look up or evaluate agents on Agentlas Cloud or Hub without running them."

Include natural trigger variations and synonyms such as "find", "browse", "compare", or "agent search" alongside "search" so the description matches how users actually phrase the request.

Consider mentioning what the search results surface (e.g., candidate metadata, descriptions) to sharpen the 'what' beyond a single verb.

DimensionReasoningScore

Specificity

"Search Agentlas Cloud and Hub agent candidates without invoking" names the domain and one concrete action plus a behavioral constraint, matching the 'Processes PDF files and extracts content' level. It does not list several specific actions, so it falls short of anchor 4.

3 / 5

Completeness

The description gives a clear "what" (search agent candidates without invoking) but contains no "when" or "Use when..." guidance, which per the rubric guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Keywords "Agentlas Cloud", "Hub", "agent candidates", and "search" are the natural terms for this niche, but there are no synonyms or common variations (e.g., find, browse, compare), matching anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

"Agentlas Cloud and Hub agent candidates" is a product-specific niche with distinct triggers and minimal risk of firing for unrelated skills, matching the anchor 5 example's clear-niche pattern.

5 / 5

Total

14

/

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

agentlas-ai/Agentlas-OS

Path

kimi/skills/agentlas-search/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.