cut
Remove sections from each line of files. Use when extracting columns, fields from CSV/TSV data, or specific character positions.
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
67%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 functional with a clear 'what' and 'when' structure, and includes some relevant trigger terms for CSV/TSV column extraction. However, it lacks the name of the underlying tool (likely 'cut'), misses several natural trigger terms users might use, and could be more specific about the concrete actions it supports to better distinguish itself from other text-processing skills.
Suggestions
Include the tool name 'cut' as a trigger term, since users familiar with Unix tools will search for it by name.
Add more natural trigger terms like 'delimiter', 'split lines', 'tab-separated', 'extract field', and 'cut command' to improve discoverability.
List more specific actions such as 'cut by delimiter, extract character ranges, select specific fields by position' to increase specificity and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Describes the core action ('Remove sections from each line of files') and mentions some use cases (extracting columns, fields from CSV/TSV, character positions), but doesn't list multiple specific concrete actions like cutting by delimiter, cutting by character range, or cutting by field number. | 2 / 3 |
Completeness | Clearly answers both 'what' ('Remove sections from each line of files') and 'when' ('Use when extracting columns, fields from CSV/TSV data, or specific character positions'), with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes useful terms like 'columns', 'fields', 'CSV/TSV', and 'character positions', but misses the key trigger term 'cut' (the Unix command this likely refers to), as well as variations like 'delimiter', 'tab-separated', 'extract column', or 'split lines'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is somewhat specific to line-based field extraction, but 'extracting columns' and 'CSV/TSV data' could overlap with skills for awk, sed, or general CSV processing tools. It doesn't clearly identify itself as the 'cut' command skill. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file for the `cut` command. It is concise, fully actionable with executable examples, well-structured with clear sections, and includes a valuable Gotchas section that highlights non-obvious limitations and suggests alternatives. The content respects Claude's intelligence while providing precisely the reference information needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It presents flags in a table, examples as executable one-liners with brief comments, and gotchas that add genuine value (e.g., single-character delimiter limitation, field reordering impossibility). No unnecessary explanations of what `cut` is conceptually or how command-line tools work in general. | 3 / 3 |
Actionability | Every example is a fully executable bash command with a clear comment explaining the use case. The flag table is precise and complete. The gotchas section provides actionable alternatives (use `awk` for multi-char delimiters, reordering, etc.). | 3 / 3 |
Workflow Clarity | This is a single-purpose, non-destructive command-line utility skill. There is no multi-step workflow or destructive operation requiring validation checkpoints. The synopsis, flags, examples, and gotchas are clearly sequenced and unambiguous for a simple skill. | 3 / 3 |
Progressive Disclosure | For a simple, self-contained skill with no bundle files and under ~80 lines, the content is well-organized into logical sections (Synopsis, Flags, LIST Format, Examples, Gotchas) that allow quick scanning. No external references are needed, and no content is unnecessarily inlined. | 3 / 3 |
Total | 12 / 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
- flox/floxenvs
- Commit
bb1f07d
- 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.