user-file-ops
Simple operations on user-provided text files including summarization.
43
Quality
28%
Does it follow best practices?
Impact
Pending
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
0%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 useful for skill selection. It lacks specific actions beyond 'summarization', contains no trigger guidance, and uses generic language that would conflict with many other skills. The phrase 'simple operations' provides no meaningful information about what the skill actually does.
Suggestions
Replace 'simple operations' with specific concrete actions (e.g., 'Read, summarize, search, and extract content from text files').
Add a 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks to read, summarize, or analyze .txt files, plain text documents, or text content').
Include file extension triggers and common user phrases (e.g., '.txt', 'plain text', 'text document', 'summarize this file').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'simple operations' without listing concrete actions. 'Summarization' is one specific action, but 'simple operations' is abstract and undefined. | 1 / 3 |
Completeness | Weakly addresses 'what' with vague 'simple operations' and one action (summarization). Completely missing 'when' guidance - no 'Use when...' clause or explicit triggers. | 1 / 3 |
Trigger Term Quality | Contains only generic terms like 'text files' and 'summarization'. Missing natural variations users would say like 'summarize', 'txt files', '.txt', 'read file', 'analyze text', etc. | 1 / 3 |
Distinctiveness Conflict Risk | Very generic description that could conflict with many skills. 'Text files' and 'operations' are broad enough to overlap with document processing, code analysis, data extraction, and numerous other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
57%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 overview for text file summarization with concrete command examples, but suffers from redundant examples and missing script implementation details. The lack of error handling guidance and validation steps weakens the workflow, and the repetitive examples could be consolidated to improve token efficiency.
Suggestions
Show the contents of scripts/summarize_file.sh or explain what statistics/preview it produces, so the summarization behavior is clear
Consolidate the three nearly identical examples into one example with a note that any input/output paths can be substituted
Add a validation step or error handling guidance (e.g., what happens if the input file doesn't exist)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., explaining where user-provided files are typically exposed, which Claude would understand from context). The examples are repetitive - three nearly identical examples don't add much value. | 2 / 3 |
Actionability | Provides concrete bash commands which is good, but the commands reference a script (scripts/summarize_file.sh) without showing its contents or explaining what it does. The user cannot verify or understand the actual summarization logic. | 2 / 3 |
Workflow Clarity | For a simple single-task skill, the workflow is straightforward (run script with input/output paths). However, there's no validation step mentioned - no way to verify the summary was created correctly or handle errors if the input file doesn't exist. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with a single purpose, the structure is appropriate. Clear sections (Overview, Examples, Output Files) make navigation easy, and no external references are needed for this scope. | 3 / 3 |
Total | 9 / 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
50ef2f3
- 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.