From oh-my-evor
Start the live FastAPI + SSE dashboard for the active Evor mission on port 8756
How this skill is triggered — by the user, by Claude, or both
Slash command
/oh-my-evor:evor-dashboard [run-id][run-id]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<Purpose>
<Use_When>
/evor-dashboard<Do_Not_Use_When>
evor-report.evor/active-run.json absent) — redirect to /evor-setup
</Do_Not_Use_When>Call evor_state_read to get run_dir from the active run. If a run-id argument was provided, call evor_state_read with the provided run-id to get run_dir.
If no active run is found: print "No active run found. Start a mission with /evor-setup first." and stop.
lsof -i :8756 2>/dev/null | grep LISTEN
If a server is already listening on port 8756: print "Dashboard already running at http://localhost:8756 (run-id: <run_id>)" and open the browser (Step 4). Do not start a second server.
Launch the server in the background. Call evor_state_read to get the log path from the active run state, then:
EVOR_RUN_DIR=<run_dir> uvicorn evor.dashboard.server:app \
--host 0.0.0.0 \
--port 8756 \
--reload \
--reload-dir <run_dir> \
2><log_path> &
Wait up to 5 seconds for the server to become ready:
for i in 1 2 3 4 5; do
curl -s http://localhost:8756/health && break
sleep 1
done
If health check fails after 5 attempts: print "Dashboard failed to start. Check the server log for details." and stop.
Attempt to open the dashboard in the default browser:
xdg-open http://localhost:8756 2>/dev/null || open http://localhost:8756 2>/dev/null || true
Print:
Dashboard running at: http://localhost:8756
Run ID: <run_id>
Mission: <mission_id>
Available views:
/ — Evolution tree (D3 DAG, frontier highlighted)
/telemetry — Live training curves (Chart.js, SSE stream)
/frontier — Frontier table (best-so-far nodes)
/health — Server health check
Press Ctrl+C or run /evor-dashboard --stop to shut down.
If the user passes --stop as an argument:
pkill -f "uvicorn evor.dashboard.server:app"
Print: "Dashboard server stopped."
<Tool_Usage>
evor_state_read — read active-run.json to resolve run_dirBash — lsof, uvicorn background launch, curl health check, xdg-open/open
</Tool_Usage>npx claudepluginhub it-dainb/oh-my-evorGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.