Who it is forA developer or researcher who wants to confirm a benchmark selection before committing to a paid or slow evaluation.
The problemBenchmark runs can be large and consume model quota, so it is hard to verify task selection and settings first.
The outcomeA printed preview of resolved task references, candidate hash, and run settings, without starting any execution.
What you need first
- Python 3.12 or newer and git
- Docker Engine with Compose and Buildx, or Docker Desktop, for benchmark runs
- Codex CLI on PATH and access to a model for candidate runs
- Harbor 0.18.0 installed through the harbor extra for benchmark runs
Steps
git clone https://github.com/Danielxu0208/rsi_eval.gitcd rsi_evalpython3.12 -m venv .venvsource .venv/bin/activatepython -m pip install -e .rsi-eval listrsi-eval preview --config examples/evaluate.json
Prompt for your agent
Clone https://github.com/Danielxu0208/rsi_eval, install it with `python -m pip install -e .` in a Python 3.12 virtual environment, then run `rsi-eval preview --config <config-path>` for the benchmark config I choose. Report the resolved task references and candidate hash. Verify that the preview ran without Docker or a model call.
Caveat. Preview only confirms the plan; real evaluations still need Docker, the Harbor extra, and Codex setup described in the README.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page