Static marketing site for vybestack.dev plus the vybescore/ dashboard that visualizes LLxprt evaluation results.
index.html,vybestack.css,assets/: main landing pageblog/: markdown posts + rendered HTML (kept up to date via.github/workflows/build-blog.yml)vybescore/: published VybeScore dashboard generated from theacoliver/evalsrepo
The workflow in .github/workflows/publish-vybescore.yml runs every 6 hours (and on manual dispatch) to:
- Check out this repo and
acoliver/evals - Install the latest
@vybestack/llxprt-codeCLI plus evaluation dependencies - Run
npm run eval:allinside the evals repo using env-driven LLxprt configs - Build the dashboard artifacts via
npm run build:vybes - Merge the previously published dashboard (copied from
vybescore/) with the new results, ensuring historical runs stay invybes-*.json, and sync the refreshedpublic/folder tovybescore/before committing
Configure these repository secrets before enabling the workflow:
| Secret | Purpose |
|---|---|
SYNTHETIC_KEY |
API key for the Synthetic GLM 4.6 provider (fed to llxprt --key) |
CEREBRAS_KEY |
API key for the Cerebras Qwen 3 provider |
ZAI_KEY |
API key for the ZAI GLM 4.6 provider |
Custom Repository variables can override non-sensitive CLI args, e.g. SYNTHETIC_BASEURL, CEREBRAS_MODEL, etc. Defaults mirror the values described in acoliver/evals/README.md.
Kick off Publish VybeScore from the Actions tab (workflow_dispatch) after updating evals or secrets. The dispatch form lets you choose a single LLxprt config if you need to re-run a specific provider.
Use scripts/publish-vybescore.sh to run the same sequence locally:
export SYNTHETIC_KEY=...
export CEREBRAS_KEY=...
export ZAI_KEY=...
# assumes acoliver/evals is checked out at ../doevals/evals
./scripts/publish-vybescore.shEnvironment variables:
| Variable | Description |
|---|---|
EVALS_DIR |
Path to the acoliver/evals checkout (defaults to ../doevals/evals) |
LLXPRT_CONFIGS |
Comma-separated config list (defaults to all LLxprt profiles) |
LLXPRT_EVAL_ARGS |
Extra flags appended to npm run eval:all (e.g. --max-passes 1) |
SKIP_EVALS |
Set to 1 to skip running npm run eval:all and only rebuild/publish |
After the script finishes, review and commit the refreshed vybescore/ artifacts.