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

62

Quality

72%

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

70%

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, well-sequenced workflow with verification and good organization. Its main weaknesses are conceptual rather than executable code examples and some redundant explanatory padding.

Suggestions

Replace the 'Conceptual example' code blocks with a real, copy-paste-ready shell_agent invocation (including actual import/usage) or explicitly justify why pseudocode is sufficient.

Trim the 'Why This Works' section to only what Claude would not already infer about shell_agent, and de-duplicate Best Practices against the step-by-step instructions.

Consider folding the Anti-Patterns list into the relevant steps to reduce repetition, or condensing both Best Practices and Anti-Patterns into a single compact guidance block.

DimensionReasoningScore

Conciseness

Mostly efficient, but the 'Why This Works' section explains shell_agent capabilities Claude can largely infer, and Best Practices / Anti-Patterns restate points already made in the instructions.

2 / 3

Actionability

Provides concrete task-description templates and a specific timeout value, but the code blocks are explicitly labeled 'Conceptual example' and are pseudocode rather than copy-paste executable code.

2 / 3

Workflow Clarity

A clear four-step sequence culminates in a Monitor-and-Verify step with an explicit feedback loop ('If issues remain, provide refined instructions to shell_agent'); the operation is non-destructive so no validation cap applies.

3 / 3

Progressive Disclosure

No bundle files exist; the single SKILL.md is organized into well-labeled sections with no nested references, which is appropriate for a self-contained skill of this size.

3 / 3

Total

10

/

12

Passed

Description

75%

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 well-formed, answering both what the skill does and when to apply it with a distinct, low-conflict niche. It is held back from the top tier by jargon-heavy trigger terms and a less-than-comprehensive enumeration of concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and some concrete actions ('Delegate complex tasks to shell_agent', 'leveraging autonomous error recovery and library selection') but does not list multiple specific actions comprehensively.

2 / 3

Completeness

Explicitly states what the skill does (delegate complex tasks to shell_agent) and when to use it ('when direct tool execution fails'), satisfying both the 'what' and 'when' with an explicit trigger.

3 / 3

Trigger Term Quality

'when direct tool execution fails' is a recognizable trigger, but the description leans on technical jargon ('shell_agent', 'autonomous error recovery', 'library selection') and omits common natural variations.

2 / 3

Distinctiveness Conflict Risk

Targets a specific tool and a narrow failure scenario (delegation when direct execution fails), giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.