file-format-converter
File Format Converter - Auto-activating skill for Data Pipelines. Triggers on: file format converter, file format converter Part of the Data Pipelines skill category.
34
3%
Does it follow best practices?
Impact
90%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/11-data-pipelines/file-format-converter/SKILL.mdQuality
Discovery
7%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 essentially a placeholder with no substantive content beyond the skill's name and category. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should select this skill. The repeated trigger term ('file format converter' listed twice) suggests auto-generated boilerplate rather than a thoughtfully crafted description.
Suggestions
Add specific concrete actions such as 'Converts between file formats including CSV, JSON, XML, Parquet, YAML, and AVRO for data pipeline workflows.'
Include a 'Use when...' clause with natural trigger terms like 'convert CSV to JSON', 'transform file format', 'change file type', '.csv', '.json', '.xml', 'data format conversion'.
Describe the scope and boundaries of the skill to distinguish it from general file processing skills, e.g., 'Handles structured data format conversions within ETL/data pipeline contexts, not binary or media file conversions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('File Format Converter') but provides no concrete actions. There is no mention of what formats are supported, what conversion operations are performed, or any specific capabilities beyond the generic label. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'file format converter' repeated twice. There are no natural user keywords like 'convert CSV to JSON', 'transform file', specific format names (.csv, .json, .xml, .parquet), or common variations users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The 'File Format Converter' label and 'Data Pipelines' category provide some specificity that distinguishes it from generic document or code skills, but the lack of specific formats or actions means it could overlap with any skill that touches file transformation. | 2 / 3 |
Total | 5 / 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 with no substantive content. It consists entirely of generic boilerplate that describes what a file format converter skill might do without providing any actual guidance, code, examples, or workflows. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Add concrete, executable code examples for common file format conversions (e.g., CSV to Parquet with pandas/pyarrow, JSON to CSV, XML to JSON) with specific library imports and function calls.
Define a clear workflow with validation steps, e.g.: 1) Detect input format, 2) Read with appropriate library, 3) Validate schema, 4) Convert and write output, 5) Verify output integrity.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual technical content.
Add a quick-reference table mapping common format pairs (CSV↔Parquet, JSON↔YAML, etc.) to recommended libraries and one-liner conversion commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no concrete information about file format conversion, and wastes tokens on generic meta-descriptions like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific formats, no libraries, no conversion examples. Every section describes what the skill could do rather than instructing Claude how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The phrase 'step-by-step guidance' is mentioned but none is actually provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no separation of concerns. There are no bundle files to reference either, but the content itself doesn't even organize what little it has. | 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
ba8561d
- 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.