metadata-extractor
Metadata Extractor - Auto-activating skill for Data Pipelines. Triggers on: metadata extractor, metadata extractor Part of the Data Pipelines skill category.
29
0%
Does it follow best practices?
Impact
77%
1.08xAverage 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/metadata-extractor/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 names the skill and its category but provides zero information about what it actually does, what inputs/outputs it handles, or when it should be selected. It would be nearly impossible for Claude to correctly choose this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Extracts metadata fields (author, date, file size, EXIF data) from files in data pipeline workflows, parses headers, and outputs structured metadata records.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to extract metadata, read file properties, parse document headers, or retrieve EXIF/ID3 tags from files in a pipeline context.'
Remove the duplicate trigger term ('metadata extractor' is listed twice) and expand with varied natural language terms users might actually say, such as 'file info', 'document properties', 'metadata fields', 'tags extraction'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('metadata extractor', 'Data Pipelines') but provides no concrete actions. There is no indication of what specific operations this skill performs—no verbs like 'extract', 'parse', 'transform', or any mention of what kind of metadata or from what sources. | 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 'metadata extractor' repeated twice. There are no natural user-facing keywords like 'extract metadata', 'file properties', 'EXIF data', 'tags', or any variations a user might naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'metadata extractor' and 'Data Pipelines' could overlap with many data processing, ETL, or file analysis skills. There are no distinct triggers or specific use cases to differentiate it. | 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 repeat the skill name without providing any actionable guidance, code, tools, or workflows for metadata extraction. It fails on every dimension because it teaches Claude nothing it doesn't already know.
Suggestions
Add concrete, executable code examples for metadata extraction (e.g., using Python libraries like pdfplumber, exiftool, or Apache Tika) with specific input/output examples.
Define a clear workflow with steps: identify file type → select extraction method → extract metadata → validate output → handle errors, including validation checkpoints.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that describe the skill abstractly and replace with actual technical content.
If the skill covers multiple metadata extraction scenarios (files, databases, APIs, streaming), create a concise overview with links to separate detailed guides for each.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'metadata extractor' excessively, and provides zero substantive information about how to actually extract metadata. | 1 / 3 |
Actionability | There are no concrete code examples, commands, specific tools, or executable guidance. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any steps. | 1 / 3 |
Workflow Clarity | No workflow, sequence, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero steps. There are no validation checkpoints or any operational detail. | 1 / 3 |
Progressive Disclosure | The content is a flat, shallow document with no references to detailed materials, no links to related files, and no structured navigation. It mentions 'Related Skills' but provides no actual links or file references. | 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.