mostlyright-data
Browse datasets built by our community or create your own with agents that find the sources and configure the pipeline. Mostly Right treats a successful run as one readable dataset version; publishing that version does not by itself prove that catch-up or scheduled refresh is running.
mostlyright-data is the command-line client. It probes sources, registers one recipe document,
starts and follows hosted dataset runs, reads what they delivered, and downloads the datasets after
they finish.
Requirements
Use CPython 3.13.
Install
python -m pip install mostlyright-data
That is the whole install. There is no second profile and no lane to choose: every mr-data
command sends its work to the backend, and it works on Linux, macOS, and Windows.
It also carries the mr-data-build agent skill, which Claude Code and Codex read to author a
recipe without rediscovering the contract a run at a time. The first mr-data command you run
places it in your agent's skill directory; there is nothing to install by hand. A skill you have
edited yourself is never replaced, and MOSTLYRIGHT_SKILL_AUTOINSTALL=0 switches the placement
off.
Sign in
mr-data login
mr-data whoami
login stores a device key on the current machine. whoami checks that key.
Check the installation
mr-data --version
mr-data --help
Build a dataset
mr-data probe SOURCE_ID "does this feed carry city grain before 2021"
mr-data recipe RECIPE.json
mr-data run RECIPE_ID --sample --max-rows 50000
mr-data checks RUN
mr-data download RUN --output ./out
probe asks one registered source one question; the session behind it is opened, reused and closed
for you. recipe registers one document and prints the identifiers the server derived from it.
run starts a run and mr-data status RUN, mr-data runs, and mr-data watch RUN report on it.
The current Harness worker executes unwindowed sample and full runs. It refuses a stated run
window, and it does not execute refresh, backfill, promotion catch-up, or scheduled warehouse
continuation. mr-data promote TABLE_ID is still the human-gated publication request, but claim a
table is live and current only when the deployed Studio and warehouse services return that evidence.
There is no local execution
There used to be. A second product lane built datasets on your own machine, and mr-data carried
about fifty commands for making, running, serving, indexing, checking and signing a build here.
That lane is gone: the engine it ran now ships only inside the backend's worker images.
mr-data --help lists every command this product has. A name that is not on it is not a command
and says so. The distribution still publishes a [local] extra — that is the engine's dependency
closure, which the backend's worker image installs — and installing it makes no command run that
does not run without it.
Documentation
Use mr-data --help for the full command list and options. Commands that support
--json write one JSON object.
--output may use a relative path.
Behavior and limits
- Weather Reader versions 1 and 2 accept one extracted GRIB2 record and refuse a multi-record GFS or HRRR file. Version 3 reads a bounded collection and selects exactly one sealed record.
- Hosted credential-free acquisition supports one single-address public HTTPS object. Bounded collections have no hosted route, and the route they used to have was the deleted local one.
- A keyed stream venue is named by a credential reference the backend holds, never by a value. No command flag takes a secret as an argument. Venues reached over an actual WebSocket are covered; a venue whose credential comes from an interactive human login, or that is not WebSocket at all, is not.
Verification
make test-fast
make test-fast is non-authoritative and is useful while editing. make verify is required
before review or merge.
Development
uv sync --locked --extra dev
The test suite drives the execution engine in-process, and requires Linux for the worker-boundary tests. The client itself is tested on Linux, macOS, and Windows.
1 maintainer
Release files for mostlyright-data 0.10.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mostlyright_data-0.10.7.tar.gz | 32.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mostlyright_data-0.10.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 65.8 MB
Release files / mostlyright_data-0.10.7.tar.gz
| Download URL | mostlyright_data-0.10.7.tar.gz |
|---|---|
| Size | 32.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a8ee6cb8eabfb97a57ce258f0df04c2134693a35f5b28331517429941f4194f
|
|
BLAKE2b-256 checksum How to use checksums |
c3e8b41beb12f0239d11038522cc8f8dc742b815305dd82a2376f4fb2a03a200
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency logRelease files / mostlyright_data-0.10.7-py3-none-any.whl
| Download URL | mostlyright_data-0.10.7-py3-none-any.whl |
|---|---|
| Size | 33.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
928045382f25ca1c31d9130563576488ea94c9027187d09ec1a6d8164c76d945
|
|
BLAKE2b-256 checksum How to use checksums |
1cc7ac2e77fd73ff858b5c07e0aa77232a81e3ae81d7d980eef0839022e54081
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency log
