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
Quality
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 severely underdeveloped and fails across all dimensions. It provides no concrete actions, no useful trigger terms beyond the skill name repeated, no guidance on when to use it, and would likely conflict with many other file or data-related skills. The description reads as auto-generated boilerplate rather than a useful skill selector.
Suggestions
Add specific concrete actions like 'Converts between CSV, JSON, XML, YAML, and Parquet formats. Handles batch conversions and preserves data types.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks to convert files, change formats, transform data between CSV/JSON/XML, or mentions file type conversion.'
Add common file extensions and format names users would mention: '.csv, .json, .xml, .yaml, .parquet, spreadsheet to JSON, tabular data conversion'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'File Format Converter' without listing any concrete actions. It doesn't specify what formats are supported, what conversion operations are performed, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the generic name, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'file format converter' repeated twice, which is redundant and overly generic. Missing natural variations users would say like 'convert CSV to JSON', 'change file type', specific format names, or common file extensions. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'file format converter' could overlap with many other skills dealing with files, data transformation, or specific format handling. No distinct triggers or niche is established. | 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 content is essentially a placeholder template with no actual instructional value. It describes what a file format converter skill should do without providing any concrete guidance, code examples, or workflows. The entire content is meta-description rather than actionable instruction.
Suggestions
Add concrete code examples for common file format conversions (e.g., CSV to JSON, JSON to Parquet, XML to JSON) with executable Python snippets
Define a clear workflow with validation steps: read source -> validate input -> transform -> validate output -> write destination
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') and replace with actual conversion patterns and library usage
Include specific tool recommendations (pandas, pyarrow, json module) with copy-paste ready code for each conversion type
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual instructions on how to convert file formats. The content only describes what the skill supposedly does without showing how. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for file conversion operations. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no useful structure. There are no references to detailed documentation, no examples file, and no actual content to organize. | 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
0c08951
- 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.