user-file-ops
Simple operations on user-provided text files including summarization.
36
32%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/skillrun/skills/user_file_ops/SKILL.mdQuality
Discovery
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 and generic to be effective for skill selection. It lacks specific concrete actions beyond 'summarization,' provides no explicit trigger guidance ('Use when...'), and would easily conflict with other text or file processing skills. The phrase 'simple operations' is particularly unhelpful as it gives Claude no meaningful information about what the skill actually does.
Suggestions
List specific concrete operations the skill performs (e.g., 'Summarizes, counts words, extracts sections, and searches within user-provided text files').
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').
Replace the vague 'simple operations' with enumerated capabilities to make the skill clearly distinguishable from other file-processing skills.
| Dimension | Reasoning | Score |
|---|---|---|
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. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the weak 'what' brings it down to 1. | 1 / 3 |
Trigger Term Quality | Includes 'text files' and 'summarization' which are somewhat natural terms users might say, but misses common variations like 'summarize', '.txt', 'read file', 'parse text', or other specific operations users would request. | 2 / 3 |
Distinctiveness Conflict Risk | 'Simple operations on text files' is extremely generic and could overlap with nearly any skill that processes files or text. There are no distinct triggers to differentiate this from other file-handling or text-processing skills. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
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 repetitive guide to running a summarization script. Its main weakness is redundancy across examples that all demonstrate the same pattern, and a lack of detail about what the script actually produces or how to handle errors. The content would benefit from showing expected output format and consolidating the examples.
Suggestions
Consolidate the three nearly identical examples into one example with a note that the same pattern applies to any input/output path, reducing redundancy.
Add a brief description or example of what the output file actually contains (e.g., show a sample summary output with line count, word count, preview).
Include basic error handling guidance—what happens if the input file doesn't exist or is not a text file.
Remove the 'Output Files' section since it just restates information already visible in the examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview paragraph explaining where user-provided files live and how the framework stages them is somewhat unnecessary context that Claude could infer. The three examples are repetitive—they all show the same command pattern with different filenames, and two of them could be collapsed. The 'Output Files' section just restates what's already shown in the examples. | 2 / 3 |
Actionability | The commands are concrete and copy-paste ready (bash scripts/summarize_file.sh ...), but the skill never shows what the script actually does, what the output looks like, or what options are available. Without the bundle providing the script, the user has no way to understand or verify behavior. There's no explanation of what 'summarize' means here (statistics? LLM summary? truncation?). | 2 / 3 |
Workflow Clarity | The skill is essentially a single-step operation (run a script), so the workflow is simple. However, there's no validation or error handling guidance—what happens if the input file doesn't exist, or if the script fails? For a simple skill this is less critical, but the lack of any feedback on success/failure keeps it from a 3. | 2 / 3 |
Progressive Disclosure | The content is reasonably organized with Overview, Examples, and Output Files sections. However, there are no references to the actual script (scripts/summarize_file.sh) for understanding its internals, no bundle files are provided, and the three nearly identical examples could be condensed. The structure is adequate but not well-optimized. | 2 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- trpc-group/trpc-agent-go
- Commit
9f4b734
- 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.