triage-calibration
SolidDaily triage accuracy calibration — use during scheduled calibration runs to verify triage classification accuracy against few-shot examples and adjust confidence thresholds
Install
Quality Score: 82/100
Skill Content
Details
- Author
- WingedGuardian
- Repository
- WingedGuardian/GENesis-AGI
- Created
- 5 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
triage-dailies
Drive the dailies morning triage ritual over an overnight batch of AI-generated video takes. Check judge health, open with the failure dossier and cost, review audited regen takes first, look at multi-frame evidence behind every doubtful verdict, record the human's rulings as gold labels, surface judge disagreement patterns, recalibrate when the gold set can carry it, and close with a plan for tonight. Use when the user says /morning-triage, "morning triage", "triage the overnight batch", "review last night's takes", "what happened overnight", or "run dailies on the batch".
feedback-triage
Triage a tool's accumulated dogfooding feedback reports into a leverage-ordered improvement backlog — reconcile what already shipped, cluster findings by underlying cause rather than symptom, assign each cluster a disposition (attack this tool, route out to the tool that owns it, or decline), apply a promotion gate (reinforced across reports, specific, actionable), and emit a triage document with a status-tracked promotion table. Use on "triage the feedback backlog", "cluster the feedback reports", "what should this tool fix next", "promote the recurring feedback", or "/feedback-triage". Explicitly invoked maintenance — never run proactively; it reads a whole corpus. If the tool's binding registers its own triage template (e.g. keel's reflection-triage), follow that template. Not for consolidating journal entries into guidance (that is consolidate-knowledge), not for a corpus of one report with no prior triage (nothing to cluster yet — a 1-report delta over an existing baseline IS a valid later pass), not for
triage-followups
After a run completes, walk the GitHub issues that run auto-filed (review non-blocking findings + improvement ideas from the evidence-out seam, AND any issue a task filed for work it deliberately cut) ONE AT A TIME with the human — explaining each from its source finding/rationale and the code it points at — and decide keep / close / promote / edit. The human triage gate the auto-filing seams deliberately do not have. Runs after any completed run (batch or single-task); re-runnable later.