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
Quality
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 essentially a placeholder that provides almost no useful information for skill selection. It lacks any concrete capabilities, meaningful trigger terms, or use case guidance. The only distinguishing element is the skill name itself, which is insufficient for Claude to make informed decisions about when to select this skill.
Suggestions
Add specific capabilities using action verbs, e.g., 'Traces data flow through pipelines, maps dependencies between datasets, visualizes transformation lineage, identifies data sources and sinks.'
Include a 'Use when...' clause with natural trigger phrases like 'Use when the user asks about data origins, wants to trace where data comes from, needs to understand data dependencies, or mentions lineage, provenance, or data flow.'
Add relevant file types or technologies if applicable, e.g., 'Works with ETL pipelines, data warehouses, SQL transformations, and DAG definitions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Data Lineage Tracker') without describing any concrete actions. There are no verbs indicating what the skill actually does - no 'tracks', 'visualizes', 'maps', or similar action words. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no explicit use cases or scenarios). The 'Triggers on' clause just repeats the skill name rather than providing meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'data lineage tracker' repeated twice, which is the skill name itself. Missing natural user phrases like 'trace data flow', 'data dependencies', 'where does this data come from', 'data source tracking', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Data Lineage Tracker' is a somewhat specific domain, the lack of concrete capabilities means it could overlap with other data pipeline skills. The mention of 'Data Pipelines skill category' provides some context but doesn't clearly distinguish it from other data-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 essentially a placeholder template with no actual content about data lineage tracking. It contains only generic boilerplate text that could apply to any skill topic, with zero actionable guidance, code examples, or specific information about tracking data lineage in pipelines.
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 capturing lineage: identify sources → track transformations → record destinations → validate lineage graph
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 column-level lineage tracking or cross-system lineage integration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about data lineage tracking. 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 but never shows how to actually track data lineage - no examples, no tools, no implementation details. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill mentions 'step-by-step guidance' but provides none. There are no sequences, validation steps, or any actual process for tracking data lineage. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples or advanced topics, 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.