metadata-extractor
Metadata Extractor - Auto-activating skill for Data Pipelines. Triggers on: metadata extractor, metadata extractor Part of the Data Pipelines skill category.
29
Quality
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 functional content. It only states the skill name and category without explaining what metadata is extracted, from what sources, or in what contexts Claude should select this skill. The redundant trigger term and complete absence of action verbs make this unusable for skill selection.
Suggestions
Add specific actions describing what the skill does, e.g., 'Extracts metadata from images (EXIF), documents (author, dates), and media files (duration, codec)'
Add a 'Use when...' clause with natural trigger terms like 'file properties', 'image info', 'document metadata', 'EXIF data', 'media information'
Specify the types of files or data sources this skill handles to distinguish it from other extraction or data pipeline skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Metadata Extractor') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of extracting, parsing, analyzing, or any specific operations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use cases or trigger guidance beyond the skill name itself). The 'Part of Data Pipelines' is category metadata, not functional guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'metadata extractor' repeated twice, which is redundant and overly narrow. Missing natural variations users might say like 'extract metadata', 'file properties', 'EXIF data', 'document info', or specific file types. | 1 / 3 |
Distinctiveness Conflict Risk | While 'metadata extractor' sounds specific, the lack of detail about what kind of metadata (file metadata, image EXIF, document properties, database metadata) makes it unclear when to use this vs other extraction or 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 essentially a placeholder template with no actual content. It describes capabilities in abstract terms without providing any concrete guidance, code, examples, or workflows for metadata extraction. The content fails all dimensions because it teaches Claude nothing actionable about the task.
Suggestions
Add concrete, executable code examples showing how to extract metadata from common data sources (files, databases, APIs)
Define a clear workflow with specific steps for metadata extraction, including validation checkpoints
Remove generic boilerplate sections ('When to Use', 'Example Triggers') and replace with actual technical guidance
Include specific metadata schemas, output formats, or transformation patterns relevant to data pipelines
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands and add no value. | 1 / 3 |
Actionability | There is no concrete code, commands, or specific guidance. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no processes, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples or documentation, and no meaningful organization beyond generic section headers. | 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.