SKILL.md · 48000
eral runs is usually the highest-signal edit you can apply; a one-off may not be worth it.
Treat suggestions as input, not instructions — the owner decides.
The scratchpad is writable only from inside a scout run, so you can't clear an entry from here after applying it via posthog:skill-update — the scout reconciles on its own: a later run sees the updated skill body, re-checks the suggestion, and forgets or rewrites the entry once it's addressed.
(Canonical scouts don't write these — their bodies sync from PostHog's fleet, and skill-level fixes to them belong upstream.)
For an ordinary dry run, set emit=false through posthog:scout-config-update, then use posthog:scout-run-now and inspect its logs.
Restore the intended emit setting when applying the final run posture.
Repo contributors get a faster loop — hogli sync:skill and the harness's local run path; see references/lifecycle-and-testing.md.
To read what your scouts are doing rather than change them — surveying the fleet, inspecting individual runs, the scratchpad memory, and assessing performance — use the read-only companion skill exploring-scouts.
Keep the two in sync when the scout config / run / scratchpad surfaces change.
Quality bar for a v1 scout
- A named, cheap signal-vs-noise discriminator anchored near the top (on a measurement scout, the rubric and sampling recipe take this slot).
- A quick close-out so a quiet run is cheap (don't pay for deep exploration when the watched surface is at baseline or absent) — except on a measurement scout, which exits early only when the window held no eligible items, since its ordinary judgments are the denominator.
- 2–4 concrete explore patterns with the actual queries/tools to run — starting points, not a rigid checklist.
- Disqualifiers listing this project's known noise (single-user quirks, dev-env bursts, allowlisted entities).
- A Decide section calibrated against the report contract — author 1:1 only for a finding the scout would own end-to-end, set
suggested_reviewers, and write memory instead when a candidate is below the bar. - A checks step where the findings are the kind whose fix shows up in data later — list the report's open checks first, then pick
metric_thresholdoragentby whether one number settles the claim. - A feature-forward body: no rollout state, no backlog, no project-only facts, no harness mechanics the prompt already carries.
- Save-memory guidance using the scratchpad prefixes so the scout gets smarter each run.
- A lean body (push depth into
references/) — every line is a recurring token cost on every run. - A tight frontmatter
description— a sentence or two naming the surface and the shapes it watches. Every scout's description loads into the caller's AI plugin together, so wordy descriptions waste token budget and get truncated; skip the fleet-wide boilerplate (report bar, durable memory, self-contained peer).