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 that restates the skill name without providing any meaningful information about capabilities, use cases, or trigger conditions. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and any distinguishing details that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions describing what the skill does, e.g., 'Extracts metadata fields (author, date, format, dimensions) from files in data pipelines, parses EXIF data from images, and reads document properties from PDFs and Office files.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about file metadata, document properties, EXIF data, file tags, or needs to extract metadata as part of a data pipeline.'
Remove the duplicate trigger term and expand with varied natural keywords users might say, such as 'file properties', 'document info', 'image metadata', 'EXIF', 'tags', 'attributes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('metadata extractor' and '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 'what does this do' beyond the name itself, and the 'when' clause is essentially just restating the skill name as a trigger. There is no explicit 'Use when...' guidance with meaningful context. | 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', 'document info', 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 numerous other skills involving data processing, ETL, file analysis, or any metadata-related task. There are no distinct triggers 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 shell with no substantive content. It consists entirely of generic, self-referential descriptions ('provides guidance for metadata extractor') without any actual guidance, code, commands, examples, or workflows. It would provide no value to Claude beyond what the skill's title and tags already convey.
Suggestions
Add concrete, executable code examples for common metadata extraction tasks (e.g., extracting metadata from files using Python libraries like `pdfplumber`, `exiftool`, or Spark DataFrame schema inspection).
Define a clear multi-step workflow for a metadata extraction pipeline, including validation steps (e.g., schema validation, null checks on extracted metadata fields).
Replace the generic 'Capabilities' and 'When to Use' sections with specific patterns, configurations, or recipes (e.g., an Airflow DAG for metadata extraction, a Spark job template).
If the skill is meant to cover multiple sub-topics (ETL metadata, file metadata, streaming metadata), create separate reference files and link to them from a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing it doesn't already know. Phrases like 'Provides step-by-step guidance,' 'Follows industry best practices,' and 'Generates production-ready code' are vacuous and waste tokens without conveying any actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of metadata extraction. The entire skill describes what it does in abstract terms without ever instructing Claude how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, sequence, or steps are defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic marketing-style text with no references to supporting files, no structured navigation, and no separation of overview from detail. There are no bundle files to reference either, but the content itself doesn't even organize its (absent) substance. | 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.