sar-evaluate

name

sar-evaluate

description

Rank an incident's current findings by confidence for a mid-search review. Use when the user asks to "evaluate findings", "check triage progress", "rank the current hits", "show top candidates", or "snapshot the leads so far" — e.g. "how's triage going on incident013", "give me the top 20 leads right now". Read-only and safe to run concurrently with sar-triage — the script never writes to findings.jsonl, manifest.json, or profile.json, so an independent agent can keep triaging while this skill answers "what do we have so far".

sar-evaluate

Produce a ranked, read-only snapshot of an incident's triage state. Unlike sar-report, this skill does not render the full ground-team deliverable — it gives a quick ranked view you can run anytime, including while another agent is still triaging.

Inputs

• Incident id — e.g. incident013. Reads runs/<incident_id>/manifest.json and runs/<incident_id>/findings.jsonl.
• Top N (optional) — how many findings to surface. Default 20.
• Min confidence (optional) — filter below this. Default 0.0 (include everything, even clear).

If findings.jsonl is missing or empty, sar-triage hasn't produced anything yet — report that and exit.

Concurrency contract

Safe to run while sar-triage is in flight. Specifically:

• This skill only reads findings.jsonl. The triage appender uses flock + atomic per-line writes, so a concurrent reader sees a consistent prefix of committed findings.
• Malformed or partially-flushed lines (unlikely, but possible under I/O pressure) are silently skipped by the loader.
• Nothing in this skill touches , , or any other file the triage agent might re-read.