agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/data-lineage-mapper/SKILL.md

data-lineage-mapper

Skill1 starsChanged 23 days agoMITView on GitHub

Traces data from origin to use when transformations, ownership and reporting dependencies need to be understood.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for critical metrics, compliance evidence, migration design or investigation of inconsistent outputs.

    line 9
  2. Distinctive:

    Every critical handoff has ownership and a validation control.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data Lineage Mapper

When to use it

Use for critical metrics, compliance evidence, migration design or investigation of inconsistent outputs.

What Claude needs

  • client-context.md for business background
  • Priority data elements and business definitions
  • Source systems, interfaces and transformation rules
  • Reports, decisions, owners and retention requirements

Method

  1. Select critical data elements based on risk, value and downstream reach.
  2. Trace each element from capture through stores, transformations and final uses.
  3. Record business owner, technical custodian, rule and control at each stage.
  4. Reconcile definitions, formats and timing across branches of the lineage.
  5. Flag opaque transformations, manual edits, duplicated sources and broken custody.
  6. Design validation points and ownership fixes for the highest-risk gaps.

Output format

Deliver lineage diagrams and a register with element, stage, source, transformation, destination, owner and control. Include unresolved gaps and validation actions.

Quality checks

  • Lineage reaches original capture rather than stopping at an intermediate file.
  • Transformations describe logic and timing.
  • Every critical handoff has ownership and a validation control.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.