csv-processor
Csv Processor - Auto-activating skill for Business Automation. Triggers on: csv processor, csv processor Part of the Business Automation skill category.
32
0%
Does it follow best practices?
Impact
91%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/csv-processor/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 severely lacking across all dimensions. It provides no concrete actions, no natural trigger terms beyond the skill name repeated, no 'Use when...' clause, and no distinguishing details. It reads as an auto-generated placeholder rather than a functional skill description.
Suggestions
Add specific concrete actions such as 'Parses, filters, transforms, and exports CSV files. Supports column selection, row filtering, data aggregation, and format conversion.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to process CSV files, parse .csv data, filter spreadsheet rows, convert comma-separated values, or perform bulk data transformations.'
Remove the duplicate trigger term 'csv processor' and replace with varied natural language terms users would actually say, such as 'CSV', '.csv file', 'comma-separated', 'tabular data', 'data import'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Csv Processor' and 'Business Automation' without listing any concrete actions like parsing, filtering, transforming, or exporting CSV data. It is entirely vague about what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no concrete actions) and 'when should Claude use it' (no explicit 'Use when...' clause or meaningful trigger guidance). The auto-activating label and repeated trigger term do not constitute meaningful guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'csv processor' repeated twice. It misses natural user terms like 'CSV file', 'spreadsheet', 'comma-separated', '.csv', 'parse CSV', 'import data', or 'tabular data'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'Business Automation' is extremely broad and could overlap with many other skills. Without specific actions or file-type triggers, this could easily conflict with any data processing or automation skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell—a template placeholder with no actual instructional content. It describes what a CSV processor skill would do in abstract terms but provides zero concrete guidance, code examples, or workflows. It fails on every dimension because it teaches Claude nothing it doesn't already know.
Suggestions
Add concrete, executable code examples for common CSV operations (reading, filtering, transforming, writing) using Python's csv module or pandas.
Define a clear workflow for CSV processing tasks, e.g.: 1. Read and inspect headers, 2. Validate data types, 3. Apply transformations, 4. Validate output, 5. Write results.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual actionable content—specific patterns, code snippets, and edge case handling.
Add concrete examples showing input CSV data and expected output for common business automation scenarios like deduplication, merging, or format conversion.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every token is wasted on describing the skill rather than teaching anything. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of CSV processing. The 'capabilities' section lists vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just abstract claims about what the skill can do without any actual process described. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain no substantive information. There are no references to detailed files, no examples, and no structured navigation to deeper content. The sections are purely decorative. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.