Dairy Data Tools

A dairy's own DairyComp and EZfeed records, read by your AI assistant.

Attach a farm's exports. Ask in plain words. Get each pen's numbers, worked out by tested scripts, not guessed.

Quick start · Other apps · What's in it · Your files

Free, for dairy vets, nutritionists and consultants. By Pádraig Lucey, MVB, MPVM, Ph.D. (Dairy Data Science).

Quick start

1. Add it to Claude

In the Claude app (desktop or claude.ai, on a paid plan):

1. Settings > Capabilities: turn on Code execution and file creation. The scripts run in Claude's own sandbox.
2. Customize > Plugins > Add marketplace: enter padge01/dairy-data-tools, then add Dairy Data Tools.

Coming soon to Claude's plugin directory, for one-click install.

2. Ask

Attach the farm's DairyComp and EZfeed exports (or this kit's sample herd) and ask, for example:

How is pen 21 doing? Did the ration change on 28 Sep work, or is it just the season?

You get the figures, where each came from and what it's out of, and a card like this one:

No DairyComp export yet? Ask "What do I type in DairyComp to export what you need?". It writes the SHOW commands from the farm's own item list.

Other apps

What's in it

Ask in plain words; the right skill picks itself. No commands to learn.

Plain Python, checked number for number against the author's earlier R version: every count says what it's out of, milk is shown as a spread, and the farm is compared with itself, never with published targets.

A sample herd (sample-herd/): a made-up California dairy's exports, to try every skill before using a real farm's.

Its neighbours, separate tools from the same place: BESTPRED (USDA's best prediction of 305-day and mature-equivalent milk; in this marketplace, and at https://bestpred.dairydatascience.com/mcp) and the Dairy Ration Lab (a free ration balancer).

What it does with your files

• The scripts read the export files where they are. They change nothing, keep nothing, and send nothing over the internet. They use Python's standard library only.
• In Claude's chat the files you attach and the scripts run in Claude's own code sandbox. What the agent reads goes to the AI company as part of the conversation, as anything you attach does, unless you run a model on your own computer.
• Event remarks, protocols and technician names are left out of what the scripts report, because they are free text typed on the farm and could contain anything, including instructions aimed at an agent.
• Nothing reads DairyComp's own files or backups, and no figure DairyComp calculates for itself (such as 305-day or mature-equivalent milk) is used: the kit works from raw records.

Good to know

• Weights are in pounds. Pens are compared with themselves and with the farm's other pens, never with published targets.
• It's a teaching and planning tool, not veterinary or nutrition advice: check anything before it changes what cows are fed.
• DairyComp 305 and EZfeed are Valley Ag Software's products; this project isn't affiliated with them.

Cite it

If it helps your work, please cite it: Lucey, P. (2026). Dairy Data Tools [software]. Zenodo. https://doi.org/10.5281/zenodo.23493936 (every version; 0.2.0 is https://doi.org/10.5281/zenodo.23493937). GitHub's "Cite this repository" button gives the same reference.

Licence

Code under Apache-2.0 (LICENSE); the skills' text under CC BY 4.0 (LICENSE-skills.md). Questions and fixes: issues.

Working on it

• plugins/dairy-data-tools/: the plugin people install (skills, sample herd, README, licences).
• tools/dairy.py, tools/dairytools/ and the ration-change scripts in tools/: the one copy of the code; python tools/sync_scripts.py copies it into each skill and writes this README. pyproject.toml builds the same code as the dairy-data-tools package on PyPI.
• tools/make_sample_herd.py: writes the sample herd (fixed seeds, same files every run).
• tests/: python -m pytest -q tests (made-up files with known answers, the sample herd, the directory's file limits).