file-tools

Simple shell utilities for files and archives.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./examples/skillrun/skills/file_tools/SKILL.md

Quality

Content

88%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 a lean, fully executable set of examples with clear per-example commands and a valid bundle script reference. Its only weaknesses are minor: one trimmable meta-sentence and section headings that are plain text rather than markdown headers.

Suggestions

Format section headings as markdown headers (e.g., '## Overview', '## Examples') to strengthen structure and navigation.

Remove or tighten the meta-sentence 'The assistant can run them and return results and files.' since it adds no actionable guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence throughout, with only one trimmable sentence of meta-explanation ("The assistant can run them and return results and files."). It is not a 5 because that sentence does not earn its place; not a 3 because everything else is efficient.	4 / 5
Actionability	All three commands (`ls -la`, `bash scripts/write_sample.sh ...`, `tar -czf out/sample.tgz -C out .`) are concrete, copy-paste ready, and cover the stated cases; the referenced script exists in the bundle and matches the invocation. Not a 4 because there are no gaps in executability.	5 / 5
Workflow Clarity	This is a simple skill where each numbered example is a single unambiguous action, so the simple-skill exception applies. The operations are not destructive or batch, so no validation checkpoints are required. Not a 4 because no sequence ambiguity remains.	5 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external references, and the sections (Overview, Examples, Output Files) are present and appropriately minimal. Not a 5 because the sections are plain text rather than markdown headers, weakening structure and navigation slightly.	4 / 5
	Total	18 / 20 Passed

Description

25%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 but severely underspecified: it names a domain without concrete actions, lacks any 'when to use' trigger guidance, and is broad enough to conflict with many other file-related skills. It sits well below the quality of the reference good examples.

Suggestions

List the concrete capabilities, e.g., 'List files, write sample output files, and create tar.gz archives via shell commands.'

Add an explicit trigger clause, e.g., 'Use when the user asks to run basic shell commands, create archives, or generate sample files in the skill workspace.'

Include natural trigger terms users would actually say (tar, zip, compress, archive, shell commands, .tar.gz) to improve discoverability and reduce conflict with other file skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("shell utilities", "files and archives") but lists no concrete actions — comparable to the anchor 'Processes PDF files'. It is not a 3 because no specific operations (e.g., listing, writing, archiving) are stated.	2 / 5
Completeness	It provides only a vague 'what' ("Simple shell utilities for files and archives") and contains no 'when' or 'Use when...' guidance at all, matching the anchor 'Has a vague what and no when'. Not a 3 because the 'what' itself is not clear or concrete.	2 / 5
Trigger Term Quality	"files" and "archives" are one or two generic keywords; the natural phrases users would actually say (tar, zip, compress, extract, .tar.gz) are missing. Not a 3, since even the present keywords are generic domain words rather than relevant distinct triggers.	2 / 5
Distinctiveness Conflict Risk	"files and archives" is very broad and would overlap with virtually any file-handling skill, matching the anchor 'Very broad; high overlap risk with many similar skills'. Not a 1 since it does name a recognizable niche (shell utilities) rather than being entirely generic.	2 / 5
	Total	8 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: trpc-group/trpc-agent-go
Path: examples/skillrun/skills/file_tools/SKILL.md
Commit: 9bb1c42

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.