CtrlK
BlogDocsLog inGet started
Tessl Logo

shell-agent-delegation

Delegate complex tasks to shell_agent when direct tool execution fails, leveraging autonomous error recovery and library selection

56

Quality

63%

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 ./benchmarks/gdpval/skills/shell-agent-delegation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 well-structured with a clear sequenced workflow and verification step, but it loses points to conceptual rather than executable code examples and some redundant explanatory sections. Replacing pseudocode with real shell_agent invocations and trimming the 'Why This Works' section would raise actionability and conciseness.

Suggestions

Replace the 'Conceptual example' and commented pseudocode with a real, runnable shell_agent call demonstrating actual parameters.

Trim the 'Why This Works' section to a brief bullet list or remove it, since the capabilities are largely self-evident.

Strengthen Step 4 with an explicit validation checklist (expected file exists, content matches required sections, re-delegate with refined prompt if not).

DimensionReasoningScore

Conciseness

Mostly efficient with clear sections, but the 'Why This Works' section explains shell_agent capabilities Claude could infer, and Best Practices/Code Example overlap with Step 2 guidance.

3 / 5

Actionability

Provides step-by-step guidance and a task-description template, but the code examples are explicitly labeled 'Conceptual example' with commented-out pseudocode rather than executable calls.

3 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced and Step 4 includes a verify-and-refine feedback loop, though the validation guidance is light compared to the explicit checkpoints a 5 would require.

4 / 5

Progressive Disclosure

Single self-contained file with well-organized section headers and no bundle files to navigate; structure is good though slightly over the 50-line simple-skill threshold.

4 / 5

Total

14

/

20

Passed

Description

67%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 purpose and trigger condition with concrete capabilities, but relies on somewhat technical language that limits natural trigger-term quality. Tightening the when clause and adding user-natural phrasing would lift completeness and trigger scores.

Suggestions

Add natural trigger phrases users would actually say (e.g., 'Use when a tool keeps returning unknown error or repeated attempts fail').

Soften jargon like 'autonomous error recovery' and 'library selection' in favor of plain-language capability descriptions.

Make the when clause more specific about which tools and failure modes trigger delegation.

DimensionReasoningScore

Specificity

Names the tool (shell_agent) and several concrete capabilities ('Delegate complex tasks', 'autonomous error recovery', 'library selection'), with only minor gaps in coverage.

4 / 5

Completeness

Explicitly states both what ('Delegate complex tasks to shell_agent') and when ('when direct tool execution fails'), though the when clause could be more specific about failure scenarios.

4 / 5

Trigger Term Quality

Contains a relevant trigger ('when direct tool execution fails') but leans on technical jargon ('autonomous error recovery', 'library selection') and misses more natural phrasings a user would say.

3 / 5

Distinctiveness Conflict Risk

The delegation-on-failure niche is mostly distinct with a clear trigger, though 'complex tasks' is broad enough to risk minor overlap with general task-execution skills.

4 / 5

Total

15

/

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.