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 critically underdeveloped. It provides no concrete actions, no meaningful trigger terms beyond the skill name repeated, and no guidance on when Claude should select this skill. It reads as auto-generated boilerplate rather than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Parses, filters, transforms, and analyzes CSV files. Supports column extraction, data aggregation, format conversion, and merging multiple CSV files.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about CSV files, .csv data, comma-separated values, tabular data processing, or importing/exporting spreadsheet data.'
Remove the duplicate trigger term 'csv processor' and replace with diverse natural language variations users would actually say, such as 'CSV', '.csv', 'comma-separated', 'parse CSV', 'CSV data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Csv Processor' and 'Business Automation' without describing any concrete actions. There are no specific capabilities listed such as parsing, filtering, transforming, or analyzing CSV data. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger 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', 'tabular data', 'import data', or 'parse CSV'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Business Automation' is extremely generic and could overlap with many other skills. 'Csv Processor' is slightly more specific but without concrete actions, it's unclear how this differs from any other data processing 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 template with no substantive content. It contains only generic boilerplate descriptions that could apply to literally any skill topic, with zero CSV-specific guidance, no executable code, no concrete examples, and no actual instructions for processing CSV files. It provides no value beyond what Claude already knows.
Suggestions
Add concrete, executable code examples for common CSV operations (e.g., reading, filtering, transforming, and writing CSV files using Python's csv module or pandas).
Define a clear workflow with specific steps for typical CSV processing tasks, including validation checkpoints (e.g., checking for malformed rows, encoding issues, or missing headers).
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content such as common patterns, edge case handling (quoting, delimiters, encoding), and production-ready code snippets.
Add specific examples showing input CSV data and expected output to make the skill truly actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific information about CSV processing, and every section is generic placeholder text that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific CSV processing techniques, no examples of input/output. Every bullet point is vague and abstract (e.g., 'Provides step-by-step guidance' without any actual steps). | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just generic claims about capabilities without any actual process description. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no meaningful content organization. There are no bundle files to reference either, but the skill body itself contains nothing worth disclosing progressively. | 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 | |
3a2d27d
Table of Contents
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.