agentleFS
DataWithBaraaDataWithBaraa/claude-code-data-engineering-skills/skills/metadata/SKILL.md

metadata

Skill84 starsChanged 13 days agoMITView on GitHub

Use when the metadata of a source has to be built or extended, to describe every table and column, the names and types from the data with a script, the descriptions from the documents, never guessed.

4 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 7

    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:

    Read the example: one source, one table, the format to follow.

    line 15
  2. Distinctive:

    Write a Python script that reads every file, every column as text first, and extracts the table names, the column names and the data types.

    line 17
  3. Distinctive:

    Read only the documents the data engineer points at: PDFs, handbooks, data dictionaries.

    line 19
  4. Distinctive:

    Write every table into the metadata file, in the format of the example.

    line 22
  5. Distinctive:

    Never invents a column, a type or a description.

    line 39
  6. Distinctive:

    Never reads a document the data engineer did not point at.

    line 40
  7. Distinctive:

    Never changes a data file.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 3 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

Metadata

The job: extend the metadata of a source from its files and its documents. Facts from the data, descriptions from the documents, nothing invented.

Input: the source, its data files, its documents, and one example table written by hand.

Steps

  1. Read the example: one source, one table, the format to follow. Table name, description, then every column with its name, type, key and description.
  2. Point at the data of the source: the exports or the landing files, one file per table.
  3. Write a Python script that reads every file, every column as text first, and extracts the table names, the column names and the data types. IDs stay strings and keep their leading zeros. The script does this, not the model, so nothing is invented.
  4. Take the keys from the profile of the source, never from a guess.
  5. Read only the documents the data engineer points at: PDFs, handbooks, data dictionaries.
  6. Take every description from the documents. A description must trace to a document.
  7. Where the documents say nothing, leave the description empty and list it. Never guess a description.
  8. Write every table into the metadata file, in the format of the example.
  9. Report what was filled and what is still empty.

Output

One metadata file per source, like references/purchasing.yaml: the source, its tables, and for every column the name, the type, the key and the description.

Reads

  • the data files of the source, the profile, the documents, the example metadata

Writes

  • the metadata file of the source, and the script that extracted the technical facts

Never

  • Never invents a column, a type or a description.
  • Never reads a document the data engineer did not point at.
  • Never changes a data file.

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.