SKILL.md
Improve System — the measured improvement loop
Mine the system's own correction history for recurring failure patterns, trend the rejection-rate metric, and propose targeted edits. Propose, never auto-apply. This is the auto-research loop adapted for non-measurable work: chat-history corrections are the proxy signal, qa-rejection rate is the trend metric (video-insights improvement #5, 2026-06-12).
Scope boundary
/system-auditfinds specific bugs and drift to fix once./improve-systemfinds recurring behavioural patterns across runs and turns them into standing rules./li curateconsolidates agent overlays into skill diffs (3+ run threshold). Do not duplicate it: when a pattern's evidence lives only in overlays, note "route via CURATE" instead of drafting the diff here. This skill's distinct ground is the QA logs, the rejection-rate metric, and session-history corrections./grade-systemgrades overall quality posture. This skill measures corrections and spend; it grades nothing.- Model-routing questions are not adjudicated here from logs alone — see "Routing questions" below.
- An improvement loop without a metric is a ritual. Every run reports the metric, even when it proposes nothing.