file-tools

Simple shell utilities for files and archives.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

87%

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, concrete, and copy-paste ready with well-organized sections and a verified script reference. Its only weakness is that the examples are standalone demos with no sequenced workflow or validation steps.

Dimension	Reasoning	Score
Conciseness	The body is lean and well under budget, with no padding or explanation of concepts Claude already knows; each numbered example carries its own weight, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	All three examples give fully executable, copy-paste-ready commands (`ls -la`, `bash scripts/write_sample.sh ...`, `tar -czf out/sample.tgz -C out .`), and the referenced script exists, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	The three numbered examples are individually clear but they are independent demos rather than a sequenced workflow, and there are no validation checkpoints, fitting the 'steps listed but checkpoints missing or implicit' anchor.	2 / 3
Progressive Disclosure	This short, single-file skill is organized into clear sections (Overview, Examples, Output Files) with one real one-level-deep script reference (scripts/write_sample.sh), meeting the simple-skill allowance for level 3.	3 / 3
	Total	11 / 12 Passed

Description

22%

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 too abstract: it names a category rather than concrete actions and omits any explicit trigger guidance, leaving a user unsure when to invoke it. It is distinguishable but only modestly so.

Suggestions

Name concrete actions instead of a category, e.g. 'List, copy, and write files; create and extract .tar.gz archives.'

Add an explicit trigger clause such as 'Use when the user asks to inspect, write, or archive files from the shell.'

Include natural trigger variations users actually say ('compress files', 'tar', 'list files') to improve both trigger coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description 'Simple shell utilities for files and archives' names a tool class and two domains but lists no concrete actions or verbs, fitting the 'vague or no actions' anchor rather than the 'names some actions' anchor at level 2.	1 / 3
Completeness	It states a vague 'what' (shell utilities for files and archives) and provides no explicit 'when' / 'Use when...' trigger guidance, so both halves are weak or missing per the level-1 anchor.	1 / 3
Trigger Term Quality	'files' and 'archives' are natural terms a user would say, but 'shell utilities' is technical and common variations like 'compress', 'tar', or 'list files' are missing, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	'shell utilities' narrows the niche somewhat, but 'files and archives' is broad and could overlap with other file-handling skills, matching the 'somewhat specific but could still overlap' anchor.	2 / 3
	Total	6 / 12 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
Commit: 737835b

Reviewed: 3 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.