data-lineage-tracker
Data Lineage Tracker - Auto-activating skill for Data Pipelines. Triggers on: data lineage tracker, data lineage tracker Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill data-lineage-trackerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting primarily of boilerplate metadata rather than useful content. It fails to explain what the skill does, provides no meaningful trigger terms beyond the skill's own name, and gives Claude no guidance on when to select this skill over others in a multi-skill environment.
Suggestions
Add specific actions the skill performs, e.g., 'Tracks data flow from source to destination, maps column-level dependencies, visualizes transformation chains, identifies upstream/downstream impacts'
Include a 'Use when...' clause with natural trigger terms like 'data flow', 'where does this data come from', 'impact analysis', 'upstream dependencies', 'downstream consumers', 'ETL lineage'
Remove the duplicate trigger term and replace with varied, user-natural phrases that would indicate a need for lineage tracking
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Data Lineage Tracker' and category 'Data Pipelines'. There are no verbs describing what the skill actually does (e.g., tracks dependencies, visualizes data flow, maps transformations). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is essentially non-existent - just stating it triggers on its own name provides no guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'data lineage tracker' repeated twice. This is the skill name itself, not natural keywords users would say. Missing terms like 'data flow', 'dependencies', 'upstream', 'downstream', 'source to target', 'ETL tracking'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'data lineage' is somewhat specific to a particular domain, which provides some distinctiveness. However, without concrete actions or clear triggers, it could still conflict with other data pipeline or data management skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content. It consists entirely of generic placeholder text that could apply to any skill topic. There is no information about data lineage tracking concepts, tools, implementation patterns, or concrete guidance of any kind.
Suggestions
Add concrete code examples showing how to implement data lineage tracking (e.g., using Apache Atlas, OpenLineage, or custom metadata tracking)
Define a clear workflow for tracking data lineage through a pipeline, including validation steps to verify lineage metadata is captured correctly
Include specific tool recommendations with executable configuration examples (e.g., Airflow lineage backend setup, Spark lineage listeners)
Replace generic capability claims with actual implementation patterns, such as how to capture source-to-target mappings, transformation logic, and data quality metrics
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual data lineage tracking. The content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, and no organization beyond generic section headers that contain no useful 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.