CtrlK
BlogDocsLog inGet started
Tessl Logo

file-tools

Simple shell utilities for files and archives.

56

Quality

62%

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 ./examples/skillrun/skills/file_tools/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, mostly executable, and well-organized for a simple skill, with a real referenced script present. It loses points only for missing explicit output-verification steps and slightly informal reference signaling.

DimensionReasoningScore

Conciseness

The body is brief and largely free of padding, presenting commands with minimal explanation, though 'Use these examples to explore basic shell commands inside a skill workspace' is slightly more preamble than a lean skill needs.

4 / 5

Actionability

Each example gives a concrete, executable command (ls -la, bash scripts/write_sample.sh, tar -czf), and the referenced script exists, with only minor gaps like unspecified preconditions for the archive command.

4 / 5

Workflow Clarity

The three numbered examples form a clear sequence of independent tasks each with its command, but there is no explicit verification of outputs (e.g., checking that out/sample.txt or the archive were created), a minor checkpoint gap.

4 / 5

Progressive Disclosure

For a short skill, content is well-organized into Overview/Examples/Output Files sections and references a real scripts/write_sample.sh one level deep; minor gaps are the absence of a reference section header for the script and no link syntax for the script path.

4 / 5

Total

16

/

20

Passed

Description

50%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 names a domain, but it lacks a 'Use when' trigger clause and concrete actions, leaving both completeness and specificity at the midpoint. Adding explicit trigger phrases and named operations would substantially improve it.

Suggestions

Add a 'Use when...' clause naming concrete triggers (e.g., 'Use when the user asks to list files, write a sample file, or create a tar.gz archive').

Replace the generic word 'utilities' with specific actions (e.g., 'List files, write sample files, and create tar.gz archives').

Include natural synonyms and file extensions (tar.gz, .tgz, shell commands) to improve trigger term coverage and distinctiveness.

DimensionReasoningScore

Specificity

The phrase 'Simple shell utilities for files and archives' names the domain and one concrete category (archives), but the actions are generic ('utilities') without naming concrete operations like list, write, or tar.

3 / 5

Completeness

It gives a clear 'what' (shell utilities for files and archives) but entirely lacks a 'when'/'Use when' trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'files' and 'archives' are relevant keywords a user might say, but common natural variants (tar, tar.gz, shell commands) and file extensions are missing, so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

'files and archives' is somewhat specific but very broad and could overlap with many general file-handling skills, so it is not clearly a distinct niche.

3 / 5

Total

12

/

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
trpc-group/trpc-agent-go
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.