CtrlK
BlogDocsLog inGet started
Tessl Logo

route-failed-searches-to-shell-agent

Delegate web search tasks to shell_agent when direct search_web tool fails, using its retry mechanism and multi-step capabilities for resilient data gathering

57

Quality

65%

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 ./benchmarks/gdpval/skills/route-failed-searches-to-shell-agent/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.

The body delivers a clear, actionable workflow with concrete code and good section structure. Its main weakness is repetition across the code example, comparison table, and best-practices sections that inflates length without adding new information.

Suggestions

Collapse the standalone 'Code Example' section into Step 2 or trim it to only the delta beyond the Step 2 snippet to remove redundancy.

Either cut the 'Why This Works' table or replace the Core Pattern bullets with it, since they convey the same retry/flexibility/adaptation points.

Turn Step 3's verification into an explicit pass/fail gate (e.g., 'If results incomplete, re-issue shell_agent with tighter requirements before proceeding') to strengthen the feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient but contains notable redundancy: the standalone code example repeats Step 2's snippet, and the 'Why This Works' table restates the Core Pattern bullets, so it could be meaningfully tightened.

3 / 5

Actionability

Provides mostly executable guidance with concrete shell_agent(task=..., timeout=...) calls and specific troubleshooting actions, though the speculative 'from tools import shell_agent' import and scenario-bound task strings are minor gaps.

4 / 5

Workflow Clarity

Clear four-step sequence with a verification checkpoint in Step 3 and troubleshooting feedback paths, but verification is a soft checklist rather than an explicit validate→fix→retry gate.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clearly signaled sections and no missing or nested references; slightly below a 5 because some sections are redundant and the file is a touch long for a lean overview.

4 / 5

Total

15

/

20

Passed

Description

62%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 clearly conveys both what the skill does and when to use it, with a specific failure-triggered delegation scenario. It is somewhat held back by reliance on internal tool names as triggers and limited action coverage.

Suggestions

Replace internal tool-name phrasing with natural user-language triggers (e.g., 'Use when web searches keep failing or returning errors and you need resilient multi-source data gathering').

Add a broader set of concrete actions beyond delegation (e.g., retries via alternative sources, scraping, API fallbacks) to lift specificity.

Include common synonyms users say ('search not working', 'search keeps erroring', 'need to scrape data') to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (web search delegation) plus 1-2 concrete actions (delegate to shell_agent, leverage retry/multi-step capabilities), but coverage is not comprehensive—essentially one primary action.

3 / 5

Completeness

Explicitly states both the 'what' (delegate web search tasks to shell_agent) and the 'when' (when direct search_web tool fails), though the trigger phrasing could be more explicit and user-natural.

4 / 5

Trigger Term Quality

Contains relevant keywords ('web search tasks', 'search_web tool fails', 'shell_agent') but leans on internal tool names rather than natural user phrasing and misses common synonyms users would actually say.

3 / 5

Distinctiveness Conflict Risk

Targets a fairly distinct niche (search_web failure → delegation) with minor overlap risk against general web-search or delegation skills rather than a crystal-clear minimal-conflict niche.

4 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
HKUDS/OpenSpace
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.