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.
32
0%
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
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 essentially a placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be nearly impossible for Claude to reliably choose this skill from a pool of similar data processing skills.
Suggestions
Add specific concrete actions such as 'Converts between file formats including CSV, JSON, XML, Parquet, YAML, and Excel. Supports batch conversion and schema mapping.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks to convert files between formats, transform CSV to JSON, change file types, or mentions format conversion for data pipeline inputs/outputs.'
Include specific file format names and extensions (.csv, .json, .xml, .parquet, .yaml, .xlsx) as trigger terms since users will reference these directly when requesting 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 barely addresses 'what does this do' (just the name 'File Format Converter') and has no explicit 'when should Claude use it' clause. The 'Triggers on' line just repeats the skill name and provides no meaningful guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'file format converter' repeated twice. It lacks natural user language 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 description is extremely generic — 'file format converter' could overlap with any skill that handles file transformations, data processing, or format changes. There are no distinct triggers or niche identifiers to differentiate it from other data processing skills. | 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/placeholder with no actual instructional content. It repeatedly references 'file format converter' without ever explaining how to convert between any file formats, which libraries or tools to use, or providing any code examples. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for common file format conversions (e.g., CSV to Parquet with pandas/pyarrow, JSON to CSV, Avro to JSON) with specific library imports and commands.
Replace the boilerplate 'Capabilities' and 'When to Use' sections with an actual workflow: e.g., 1. Detect input format, 2. Choose conversion method, 3. Convert with validation, 4. Verify output integrity.
Include specific tool/library recommendations (e.g., pandas, pyarrow, fastavro, xmltodict) with brief code snippets showing their usage for format conversion.
Add a validation/verification step showing how to confirm the converted file is correct (e.g., row count checks, schema validation, sample data comparison).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'file format converter' excessively, and provides zero substantive information about how to actually convert file formats. | 1 / 3 |
Actionability | There are no concrete code examples, commands, library recommendations, or executable guidance of any kind. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow steps, sequences, or validation checkpoints are provided. The 'step-by-step guidance' is merely claimed in a bullet point but never actually delivered. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to detailed files, no structured navigation, and no meaningful content organization beyond boilerplate headings. | 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.