overscore-cli
ovs, the command line for Overscore: query your data, build and deploy Python models,
send results to the systems your team works in, from a terminal or from a coding agent like Claude Code.
uv tool install overscore-cli # or: pip install overscore-cli
ovs login # approve this computer in the browser; it makes ~/Overscore/<company>
Then open the folder it names in Claude Code. It holds the rules and the skills your agent reads (AGENTS.md, which a
CLAUDE.md imports, and .agents/skills/), overscore.toml with your address, and models/ and files/; the key stays in the
keychain. ovs guide lists every command.
No browser or keychain (a server, a scheduled job)? Make a key on Settings, Agents in Overscore and set
OVERSCORE_KEY=ovs_... and OVERSCORE_URL=https://<you>.overscore.tech instead.
ovs init [folder] makes a folder of your own the same way; --for claude|codex|cursor|gemini|agents|all writes another
agent's layout (CLAUDE.md and .claude/skills, .cursor/rules, GEMINI.md). Data going in names its dataset every time:
ovs load quickbooks invoices invoices.csv.
A Python model, start to finish
ovs pull sales.leads # a sample, for local runs
# write models/lead_scores/model.py and model.toml
ovs model run lead_scores --local # runs here, on the sample
ovs upload put lead_model files/lead_model.pkl # the fitted model it reads
ovs model push lead_scores # saved and run in Overscore; prints the run's log
ovs destination add webhook "Their CRM" https://crm.example.com/in
ovs sync add scores_out --from lead_scores --key lead_id --to "Their CRM"
ovs sync run scores_out
A model's script imports its helper: from overscore_model import rows, read, file, output, log.
The folder as a checkout
ovs pull # every model, saved query, metric and dashboard as files: models/, saved_queries/, metrics/, dashboards/
ovs status # what changed here since the pull, what changed in Overscore, what is new on either side
ovs push # every changed file back, each push a version; "pull first" when it changed in Overscore since the pull
Every command prints JSON when its output is not a terminal ({"success": true, ...}, or
{"success": false, "error": "..."} with exit code 1), so agents can read it.
1 maintainer
Metadata
1 maintainer
Release files for overscore-cli 0.1.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| overscore_cli-0.1.14-py3-none-any.whl | Python 3 | none | any | Details |
Release files / overscore_cli-0.1.14-py3-none-any.whl
| Download URL | overscore_cli-0.1.14-py3-none-any.whl |
|---|---|
| Size | 182.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c227ef882bb4adfdc4bd75966db671f097c637a1dac9b365f296fe4618be878
|
|
BLAKE2b-256 checksum How to use checksums |
dd86c7672f3a4dd82b6015ff9ff414182cf56940c029162d3ef7b75653ba3dd1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.24 {"installer":{"name":"uv","version":"0.12.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for overscore-cli 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
