agentleFS
changocrchangocr/agents-lab/.agents/skills/data-pipeline/SKILL.md

data-pipeline

Skill0 starsChanged 4 months agoMITView on GitHub

Build or revise privacy-safe data ingestion, cleaning, joining, and feature pipelines with explicit provenance, grain, keys, null semantics, validation, and output contracts. Use for data engineering tasks involving confidential or large structured data.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Keep inputs outside version control or in the project's explicitly ignored private area.

    line 9
  2. Distinctive:

    Use DuckDB or Polars for large columnar workloads when justified.

    line 12
  3. Distinctive:

    Write code and schema contracts, never private data or derived datasets.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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 Pipeline

  1. Confirm source ownership, permitted use, availability timing, and storage boundary.
  2. Keep inputs outside version control or in the project's explicitly ignored private area.
  3. Define grain, primary keys, types, null meaning, and expected coverage before transforms.
  4. Validate row counts, uniqueness, joins, non-matches, ranges, and freshness at each boundary.
  5. Use DuckDB or Polars for large columnar workloads when justified.
  6. Write code and schema contracts, never private data or derived datasets.
  7. Record evidence and limits using the project's durable-output contract; do not fill unavailable values silently.

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.