it-dainb

Mission interview workflow that elicits all mission settings and launches a validated run via evor_init_run

Start the live FastAPI + SSE dashboard for the active Evor mission on port 8756

Scan an existing ML workspace to produce a starting-point report; pre-fills the evor-setup interview

Check environment health and .evor integrity; auto-repair obvious issues

Inspect accumulated Gotchas (failures + hardware limits) and the hardware capability profile

Evor MCP tool catalog, run lifecycle, artifact schemas, and native-tool guide. Auto-loads when operating an evor run — setting up/running/resuming/inspecting a mission, recording nodes/evals, launching or watching training, reading/writing tick artifacts, citing papers, emitting/querying signals, or changing any evor state.

Generate a final Evor mission report with tree visualization, frontier table, and static HTML export

Load and validate the mission contract, set active run state, and invoke the Evor tick loop

Use drail CLI for ALL code navigation — reading files, finding classes/functions/symbols, searching text, tracing callers/inheritance, listing files, mapping codebases, and scanning directories. Use drail instead of the Read tool, Grep tool, Glob tool, grep, find, and cat for source code files. Trigger this skill whenever any agent needs to read code, find definitions, search symbols, trace call chains, check file dependencies, explore a codebase, or list files. Replaces all code-reading and code-searching tools with explicit, AST-aware, token-efficient alternatives. Use drail whenever code exploration, code reading, symbol search, class lookup, inheritance tracing, dependency inspection, or codebase understanding is involved.