working-with-scouts
Working with Signals scouts
A scout is a scheduled agent that wakes on its own interval, looks at one PostHog project, and either writes a finding into the Signals inbox as a report or closes out empty. Think of the fleet as a team of junior analysts you've hired to watch things for you: they work unattended, they hold a high evidence bar, and — critically — they get better the more you work with them. Every dismissal reason you write, every note you leave, every report you act on feeds back into what they do next.
This skill is the operating manual for that working relationship: how to delegate a watching job, how to act on what comes back, and how to steer the fleet so it converges on what your team actually cares about. Three sibling skills carry the mechanics — reach for them when a workflow below hands off:
| Skill | Covers |
|---|---|
authoring-scouts |
Writing, editing, and tuning scouts: skill bodies, config, the notes write side, the test loop |
exploring-scouts |
Read-only observability: the fleet roster, run history, scratchpad memory, health assessment |
inbox-exploration |
The inbox itself: triaging, drilling into, acting on, and resolving / dismissing / snoozing reports |