← ClaudeAtlas

pynecore-clilisted

Use the `pyne` command-line interface that ships with PyneCore (`pynesys-pynecore[cli]`) correctly and non-interactively. Covers every built-in command of PyneCore 6.12 with the exact format of each argument and option: `pyne run` on a data file or provider stream (date range, chart timeframe and bar magnifier, security data, outputs, viz, profiling, `--live`, `--broker`), `pyne data download / convert-from / convert-to / aggregate / map`, `pyne plugin list / info`, `pyne debug ast`, `pyne benchmark`, `pyne broker resume`, the global options that regenerate demo and config files, shell completion, and `PYNE_*` environment variables. Use whenever a task runs or composes a `pyne ...` command, asks which flag or value format an option takes, what pyne writes into the workdir (demo files, `api.toml`, plugin configs, script `.toml`, output CSVs, logs), or why a pyne command prompts, aborts or hangs in an agent shell.
theonetrade/pynecore-skills · ★ 2 · Data & Documents · score 78
Install: claude install-skill theonetrade/pynecore-skills
# The `pyne` CLI `pyne` is the console script of `pynesys-pynecore[cli]` (entry point `pynecore.cli:app`, a Typer application). It lives in the environment's `bin/` (`Scripts\` on Windows); there is no `python -m pynecore` and no `--version` flag. This skill describes the CLI as installed, from its own `--help` pages and the PyneCore documentation; `scripts/cli_help.py` re-reads the installed CLI and reports every command or option that differs from `references/commands.md`. ## 1. Find it, call it, keep it quiet ```bash <project>/.venv/bin/pyne --help # a venv project (also venv/, env/) uv run pyne --help # a uv project python3 <skill>/scripts/cli_help.py # which pyne, version, command tree with options python3 -c "import importlib.metadata as m; print(m.version('pynesys-pynecore'))" # the version python -c "from pynecore.cli import app; app()" run demo demo # the same CLI without the console script ``` Rules for an agent shell: - **Global options go before the command**: `pyne --workdir DIR run SCRIPT DATA`, never after. - Set `PYNE_NO_LOGO=1` (or `PYNE_QUIET=1`) and `NO_COLOR=1`; `COLUMNS=160` widens the help panels so option names are not wrapped. Progress bars and spinners are suppressed when stdout is not a terminal; a live run prints a heartbeat line every 30 s instead. - **Prompts abort without a terminal** (`Aborted.`, exit 1): creating a missing workdir, a download whose `--from` lies before th