Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Data Lineage

ASecurity

Trace a metric to the source tables the user can name, and stop where the trail stops. Use when the user mentions data lineage, where does this number come from, metric source, column lineage, or asks for a lineage note. Data and analytics skill by Yasir Jilani.

2 stars
0 votes
0 copies
0 views
Added 9/30/2026
ai-agentspythonawsgitapi

Works with

cliapi

Security Analysis

A100/100

Scanned 9/30/2026

$npx -y skills add SYasJ/claude-business-skills --skill data-lineage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Data Lineage?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Data Lineage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/syasj-data-lineage/badge)](https://www.skillsdirectory.com/skills/syasj-data-lineage)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: data-lineage
description: "Trace a metric to the source tables the user can name, and stop where the trail stops. Use when the user mentions data lineage, where does this number come from, metric source, column lineage, or asks for a lineage note. Data and analytics skill by Yasir Jilani."
license: MIT
compatibility: Agent Skills standard. No network access, extra packages, or credentials required.
metadata:
  author: Yasir Jilani
  version: "1.0.0"
  domain: data
---

<!-- GENERATED FILE - edits here are overwritten by scripts/generate.py.
     Edit the 'data-lineage' entry in source/, then run:
       python3 scripts/generate.py && python3 scripts/validate.py
     See CONTRIBUTING.md. -->

# Data Lineage

Trace a metric to the source tables the user can name, and stop where the trail stops.

## When to use this skill

Use this skill when the user:

- data lineage
- where does this number come from
- metric source
- column lineage

## When not to use this skill

- The user wants a different domain's specialist skill.
- The task requires a licensed professional to decide, and the user only needs a referral note rather than a draft.
- The request asks you to deceive, evade a control, or hide material facts.

## Professional boundary

Do not invent numbers. If a source file is missing, say so. Distinguish observation from inference. Do not re-identify private data to make a point.

## Operating boundaries

- Use only information the user provides or files they explicitly ask you to read. Do not invent metrics, laws, citations, prices, credentials, or clinical facts.
- Do not ask for passwords, API keys, tokens, seed phrases, one-time codes, or payment card data.
- Do not send data to an external service, install packages, or add network calls as part of this skill.
- Separate facts, assumptions, and recommendations. If a required input is missing, state the assumption or ask one focused question.
- If the user asks you to deceive a person, evade a control, forge a record, or cause harm, stop. Offer a legitimate alternative.
- Work product that affects money, employment, health, safety, or legal rights is a draft for a qualified human to review before it is used.

## Inputs to collect

- The metric
- The tables they know
- The transform they can point to
- The gap

## Workflow


### 1. Step 1

Start at the metric definition they use.
### 2. Step 2

Walk only to tables they named.
### 3. Step 3

Mark the first hop you cannot show.
### 4. Step 4

Do not draw a source you inferred from a column name.
### 5. Step 5

Note if two jobs write the same column.
### 6. Step 6

Give the owner one place to look next.

## Output

Deliver a **lineage note**.

- Purpose of this lineage note, in two sentences.
- Facts the user supplied, listed separately from assumptions.
- The work itself, in the structure the workflow names.
- Open questions, risks, and the single next action with an owner.
- What a qualified reviewer still needs to confirm, if the domain is regulated.

## Quality bar

- Every number, date, name, and citation came from the user or is marked as an assumption.
- The artifact can be used without reading this skill again.
- Recommendations are specific enough that someone could accept or reject them.
- Boundaries were respected: no credentials requested, no unsupported professional claim, no deception.

## Example

### Scenario

Jonah asked where active_accounts comes from. Noah can point at a dbt model name and then the trail stops. The slide says 'the warehouse'.

### Example data

```text
metric: active_accounts, defined as workspaces with a login on that day
known hop: model fct_active_accounts, owner Noah
source tables named: none
second writer: unknown
slide text: "comes from the warehouse"
```

### Example outcome

**Lineage note**
active_accounts is the count of workspaces with a login that day, per Jonah's definition.
Known hop: fct_active_accounts, owner Noah Berger.
Next hop: not in the file. Do not draw a source table from the column name.
The slide line 'the warehouse' is not a source.
Open: the table under the model, and whether any other job writes active_flag.
Next: Noah names that table before this metric is used in a board pack.

## Anti-patterns

- A full map drawn from guesses
- Ignoring a second writer
- A lineage slide with no table names

## Related skills

- `metric-definition`
- `data-dictionary`

Attribution

SYasJSYasJ
View sourceSee grades on GitHubMore from SYasJ →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →