← ClaudeAtlas

pynecore-docslisted

Read the complete PyneCore documentation offline from the copy bundled in this skill. Use whenever a PyneCore / Pyne question needs an exact API signature, parameter list, setting name, CLI flag, file format or behaviour detail that memory cannot guarantee: `ta.*`, `strategy.*`, `request.security`, `input.*`, `ScriptRunner`, `pyne run` / `pyne data` options, the symbol `.toml`, live mode, bar magnifier, profiling, internals. The skill carries every documentation page (about 110 Markdown files), a topic map, a page inventory, a grep/print tool, a version check against the installed runtime and a script that refreshes the snapshot from a PyneCore release. No network and no editor installation are needed.
theonetrade/pynecore-skills · ★ 2 · Data & Documents · score 78
Install: claude install-skill theonetrade/pynecore-skills
# PyneCore documentation, offline The full PyneCore documentation lives in this skill's `docs/` folder (PyneCore's own Markdown pages, Apache-2.0, see `docs/LICENSE` and `docs/NOTICE`). `docs/MANIFEST.json` records which PyneCore version the snapshot describes. Nothing outside the repository is read. ## 1. Find and open pages ```bash python3 <skill>/scripts/find_docs.py # docs path, documented version vs installed runtime python3 <skill>/scripts/find_docs.py --list # every page with its title python3 <skill>/scripts/find_docs.py --grep "process_orders_on_close" # search all pages python3 <skill>/scripts/find_docs.py --grep "exit\(" --context 2 python3 <skill>/scripts/find_docs.py --page reference/lib/strategy.md # absolute path python3 <skill>/scripts/find_docs.py --page reference/lib/strategy.md --print python3 <skill>/scripts/find_docs.py --online reference/lib/strategy.md # URL of the same page online ``` `--root <project>` points the version check at a project's interpreter (`.venv`, `venv`, `.pyneide/venv`, or `VIRTUAL_ENV`). Pages can also be opened directly: `<skill>/docs/<section>/<page>.md`. ## 2. Version check `find_docs.py` prints the documented version (from `MANIFEST.json`) and the installed `pynesys-pynecore` version. When they differ and the question concerns a recently changed feature, confirm against the installed package (`pyne run --help`, `inspect.signature(...)`, `runner.script.settable_fields()`) before r