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.
33
3%
Does it follow best practices?
Impact
85%
0.98xAverage 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/data-lineage-tracker/SKILL.mdQuality
Discovery
7%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 extremely weak across all dimensions. It reads as auto-generated boilerplate with no substantive content—no concrete actions, no natural trigger terms beyond the skill name repeated, and no explicit guidance on when to use it. It would be nearly impossible for Claude to reliably select this skill from a pool of similar data-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Tracks data flow across pipeline stages, maps upstream/downstream dependencies, identifies source-to-target transformations, and visualizes data provenance.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about data lineage, data flow, data origin, upstream/downstream dependencies, ETL tracing, pipeline provenance, or source-to-target mapping.'
Remove the duplicated trigger term ('data lineage tracker' listed twice) and expand with varied natural language terms users would actually say, such as 'where does this data come from', 'trace data', 'data dependency', 'column lineage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself ('Data Lineage Tracker') and mentions a category ('Data Pipelines') but never describes what it actually does—no verbs like 'tracks', 'maps', 'visualizes', or any specific capabilities. | 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—only a vague auto-activation mention and a repeated trigger phrase. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'data lineage tracker' repeated twice. There are no natural user keywords like 'data flow', 'data origin', 'upstream', 'downstream', 'dependency', 'ETL', 'pipeline tracing', or other terms a user would naturally use when needing lineage tracking. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'data lineage' is somewhat specific to a niche domain, which provides some distinctiveness. However, the lack of concrete actions and the broad 'Data Pipelines' category label could cause overlap with other pipeline-related skills. | 2 / 3 |
Total | 5 / 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—a boilerplate template that contains no actual instructional content about data lineage tracking. It lacks any concrete guidance, code examples, tool recommendations, or workflow steps. It would provide no value to Claude beyond what the skill's title alone conveys.
Suggestions
Add concrete, executable code examples for data lineage tracking (e.g., using OpenLineage, Apache Atlas, or custom metadata tracking with Python/SQL)
Define a clear multi-step workflow for implementing lineage tracking in a data pipeline, including validation steps to verify lineage metadata is captured correctly
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content such as specific patterns, configuration snippets, and integration examples
Include at least one complete, copy-paste-ready example showing how to instrument a pipeline (e.g., an Airflow DAG or Spark job) with lineage tracking
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual knowledge or instructions. Every section restates the same vague information about 'data lineage tracker' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of data lineage tracking implementations. The content only describes what the skill could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, no validation checkpoints. The bullet 'Provides step-by-step guidance' is a claim without any actual steps provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed materials, no links to related files, and no structured navigation to deeper content. | 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
4dee593
- 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.