metadata-extractor
Metadata Extractor - Auto-activating skill for Data Pipelines. Triggers on: metadata extractor, metadata extractor Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill metadata-extractorOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is severely underdeveloped and essentially only provides the skill name with no substantive content. It lacks any concrete actions, meaningful trigger terms, explicit usage guidance, or distinguishing characteristics. The redundant trigger term and boilerplate category mention provide no value for skill selection.
Suggestions
Add specific concrete actions describing what metadata is extracted and from what sources (e.g., 'Extracts EXIF data from images, ID3 tags from audio files, and document properties from PDFs').
Include a proper 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about file properties, image metadata, EXIF data, document info, or wants to read embedded file information').
Specify the data types or file formats this skill handles to distinguish it from other potential metadata-related skills in the Data Pipelines category.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Metadata Extractor') without describing any concrete actions. There are no specific capabilities listed - no mention of what metadata is extracted, from what sources, or what operations are performed. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' section is not a proper 'Use when...' clause and only repeats the skill name. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'metadata extractor' repeated twice, which is redundant and unlikely to match natural user language. Users would more likely say 'extract metadata', 'get file info', 'read EXIF data', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'metadata' could apply to files, images, documents, audio, video, databases, APIs, etc. Without specifying what type of metadata or from what sources, this could conflict with many other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual instructional content. It describes what a metadata extractor skill would theoretically do but provides zero actionable guidance, code examples, or specific techniques for extracting metadata from data pipelines. The entire content could be replaced with actual implementation details.
Suggestions
Add concrete, executable code examples showing how to extract metadata from common data sources (databases, files, APIs) using specific tools like Apache Spark, Airflow, or Python libraries
Define a clear workflow with steps: identify source -> extract schema/metadata -> validate -> store/catalog, including validation checkpoints
Remove generic boilerplate sections ('Purpose', 'Capabilities' with vague claims) and replace with specific techniques, patterns, and tool configurations
Include example input/output showing what metadata looks like before and after extraction (e.g., schema definitions, data lineage, column statistics)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about metadata extraction. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it claims to do ('generates production-ready code') but provides zero executable examples or actual instructions for metadata extraction. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content only lists vague capabilities without explaining how to actually perform metadata extraction tasks. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed documentation, examples, or related files. There's nothing to disclose progressively because there's no substantive content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.