CtrlK
BlogDocsLog inGet started
Tessl Logo

user-file-ops

Simple operations on user-provided text files including summarization.

36

Quality

32%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./examples/skillrun/skills/user_file_ops/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a functional but somewhat verbose guide to a simple file summarization task. The three nearly identical examples add bulk without adding value, and the explanation of file staging conventions is unnecessary context for Claude. The skill would benefit from showing the actual output format and trimming redundant examples.

Suggestions

Reduce the three examples to one, since they all demonstrate the same command pattern with different filenames.

Remove the paragraph explaining where user-provided files are typically exposed—Claude can infer file locations from the command examples.

Add an example of what the summary output file actually contains (format, structure) so Claude knows what to expect.

Include the actual `scripts/summarize_file.sh` script in the bundle or describe its behavior so Claude can troubleshoot or adapt it.

DimensionReasoningScore

Conciseness

The content includes some unnecessary explanation (e.g., explaining where user-provided files are typically exposed, what the framework does with uploads). The examples are repetitive—three examples that all do the same thing with different filenames add little value. Could be tightened significantly.

2 / 3

Actionability

The commands are concrete and copy-paste ready, which is good. However, there's no indication of what the script actually does internally, what the output format looks like, or what options are available. The script itself isn't provided in the bundle, so Claude can't verify or adapt the behavior.

2 / 3

Workflow Clarity

This is a simple single-step skill (run a bash script), so multi-step workflow isn't strictly needed. However, there's no validation or error handling guidance—what happens if the file doesn't exist, if the script fails, or if the output is unexpected. For a simple skill this is acceptable but not exemplary.

2 / 3

Progressive Disclosure

The content is reasonably organized with sections (Overview, Examples, Output Files), but the 'Output Files' section just lists hardcoded filenames from the examples which isn't useful as a reference. No bundle files are provided, so there's no script to reference or link to, which limits the skill's completeness.

2 / 3

Total

8

/

12

Passed

Description

14%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague to be effective for skill selection. It lacks specific concrete actions beyond 'summarization,' provides no explicit 'Use when...' trigger guidance, and is generic enough to conflict with numerous other file- or text-related skills.

Suggestions

List specific concrete operations the skill performs (e.g., 'Summarize text files, count words, search for patterns, extract sections').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks to summarize, read, or perform basic operations on .txt or plain text files').

Narrow the scope language to reduce conflict risk—replace 'simple operations' with the actual enumerated capabilities to distinguish this from other file-handling skills.

DimensionReasoningScore

Specificity

The description mentions 'simple operations' and 'summarization' but 'simple operations' is extremely vague. Only one concrete action (summarization) is named, and the rest is abstract language.

1 / 3

Completeness

The 'what' is weak (vague 'simple operations' plus summarization) and there is no 'when' clause or explicit trigger guidance at all, which per the rubric should cap completeness at 2 at best—but the what is also too weak, landing this at 1.

1 / 3

Trigger Term Quality

Includes some relevant terms like 'text files' and 'summarization' that users might say, but misses common variations and additional natural keywords (e.g., 'summarize', '.txt', 'read file', 'word count', specific operation types).

2 / 3

Distinctiveness Conflict Risk

'Simple operations on text files' is extremely generic and would easily conflict with many other skills that handle files, text processing, or document manipulation.

1 / 3

Total

5

/

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.

Validation11 / 11 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.