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
- machina-sports/sports-skillstheir own version, first seen Nov 5, 2026
- cooklang/cooklang-skillstheir own version, first seen Oct 13, 2026
- cook-md/cook-mcptheir own version, first seen Oct 8, 2026
- msrv-tech/skillstheir own version, first seen Oct 2, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- machina-sports/sports-skills★ 266same name
- msrv-tech/skills★ 60same name
- cooklang/cooklang-skills★ 9same name
- cook-md/cook-mcp★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- big-reviewSkill
- contractSkill
- cost-reviewSkill
- data-productSkill
- docsSkill
- impactSkill
- incidentSkill
- knowledge-refreshSkill
- migrationSkill
- profileSkill
- pr-reviewSkill
- qualitySkill
- reconcileSkill
- test-dataSkill
- toolkitSkill
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
- Distinctive: line 15
Read the example: one source, one table, the format to follow.
- Distinctive: line 17
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.
- Distinctive: line 19
Read only the documents the data engineer points at: PDFs, handbooks, data dictionaries.
- Distinctive: line 22
Write every table into the metadata file, in the format of the example.
- Distinctive: line 39
Never invents a column, a type or a description.
- Distinctive: line 40
Never reads a document the data engineer did not point at.
- Distinctive: line 41
Never changes a data file.
“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.
Files
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
- Read the example: one source, one table, the format to follow. Table name, description, then every column with its name, type, key and description.
- Point at the data of the source: the exports or the landing files, one file per table.
- 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.
- Take the keys from the profile of the source, never from a guess.
- Read only the documents the data engineer points at: PDFs, handbooks, data dictionaries.
- Take every description from the documents. A description must trace to a document.
- Where the documents say nothing, leave the description empty and list it. Never guess a description.
- Write every table into the metadata file, in the format of the example.
- 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.
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
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.

