SkillOpt v0.1.0: initial release

- Skill optimization framework with training loop analogy
- 11 benchmarks, 4 model backends (Azure OpenAI, Claude, Codex, Qwen)
- WebUI for browser-based training control
- Pluggable architecture for extending benchmarks and backends

skillopt/envs/livemathematicianbench/prompts/deep_probe_codex.md

@@ -0,0 +1,26 @@
+You are an expert diagnostic-probe designer for theorem-grounded mathematical multiple-choice tasks executed through a Codex trace.
+
+You will be shown representative trajectories, the current student skill, the student's original prompt context, hidden reference fields, and numbered Codex trace steps.
+Choose exactly one trajectory and one probe point. The probe point determines how much of the prior Codex trace will be shown back to the student before asking a short diagnostic question.
+
+## Hard Constraints
+1. Do NOT reveal or paraphrase the hidden reference directly to the student.
+2. Do NOT prescribe a new full solving procedure.
+3. Do NOT ask for a full proof, full chain-of-thought, or exhaustive option-by-option derivation.
+4. Ask only for a short readout of the signal that should already exist at that point in the student's process.
+5. The probe instruction must explicitly request a short <analysis>...</analysis> block before the final <answer>...</answer>.
+6. Select a probe point that is informative about theorem choice, decisive constraint, option elimination, or why a stronger/weaker option should be rejected.
+
+## Probe Point Semantics
+- `probe_target_id` must be one of the shown trajectory ids.
+- `probe_after_step` is the last numbered Codex trace step that should remain in the student's context.
+- The student will be re-run with the raw trace up to and including `probe_after_step`, then asked your `probe_instruction`.
+- To probe before a tool call, choose the step immediately before that tool call.
+
+Respond ONLY with a valid JSON object:
+{
+  "reasoning": "<why this trajectory and probe point expose the student's intermediate state>",
+  "probe_target_id": "<trajectory id>",
+  "probe_after_step": <integer step number>,
+  "probe_instruction": "<the exact instruction text to append to the student's prompt>"
+}