CtrlK
BlogDocsLog inGet started
Tessl Logo

shell-agent-file-ops

Leverage shell_agent for autonomous file creation and modification with automatic tool selection and error recovery

53

Quality

58%

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-file-ops/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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 and self-contained with useful examples and anti-patterns, but it stops short of showing the concrete shell_agent invocation and lacks explicit validation feedback loops for the operations it describes.

Suggestions

Show the actual shell_agent call syntax in at least one example so guidance is executable rather than prompt-only.

Replace the soft 'Check the output' step with an explicit validation checkpoint (e.g., verify files exist, inspect content, re-issue the task if requirements are unmet).

Tighten the body by merging the redundant Summary into Purpose and removing or enriching the thin 'Basic Pattern' subsection.

DimensionReasoningScore

Conciseness

The body is mostly efficient and does not explain concepts Claude already knows, but the Summary section restates the Purpose and the 'Basic Pattern' subsection adds little, so it could be tightened.

2 / 3

Actionability

Concrete, copy-pasteable task-description examples are provided, but the skill never shows the actual shell_agent invocation syntax, so the guidance on how to call the tool is incomplete.

2 / 3

Workflow Clarity

A sequence is present ('1. Decide... 2. Write... 3. Handle errors... 4. Return'), but validation is only a soft 'Check the output' best practice with no explicit checkpoint or fix-and-retry feedback loop.

2 / 3

Progressive Disclosure

The skill is single-purpose, self-contained, and organized into clearly labeled sections (Purpose, When to Use, How to Use, Best Practices, Comparison, Anti-Patterns) with no nested or external references, fitting the simple-skill allowance.

3 / 3

Total

9

/

12

Passed

Description

60%

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 specific about capabilities but reads as a technical summary rather than a user-facing trigger. It states the 'what' clearly but omits an explicit 'when to use' clause, capping completeness and weakening trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when you need files created or modified and want the tool to pick the approach and recover from errors automatically').

Replace technical framing ('Leverage shell_agent', 'autonomous') with language a user would naturally say, and include common variations like 'create files', 'update files', 'generate files'.

Sharpen distinctiveness by contrasting with direct file tools (e.g., 'Use when the best approach is unclear; use write_file directly when content is already known').

DimensionReasoningScore

Specificity

The description explicitly enumerates multiple concrete actions — 'file creation and modification', 'automatic tool selection', and 'error recovery' — matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.

3 / 3

Completeness

It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

'file creation' and 'modification' are natural user terms, but the framing is technical ('Leverage shell_agent', 'autonomous', 'automatic tool selection') and lacks common variations a user would actually say.

2 / 3

Distinctiveness Conflict Risk

The shell_agent niche is somewhat specific, but 'file creation and modification' is broad enough to overlap with direct file-write tools, so it is not yet a clearly distinct trigger set.

2 / 3

Total

9

/

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.