working-with-scouts

Delegate, steer, and calibrate PostHog Signals scouts that watch projects and file inbox reports.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill working-with-scouts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: working-with-scouts
Source: https://github.com/PostHog/posthog-foss/tree/main/products/signals/skills/working-with-scouts
Command: npx skills add https://github.com/PostHog/posthog-foss --skill working-with-scouts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PostHog Signals scouts are scheduled agents that watch a project and write findings into the Signals inbox, but getting value from them requires knowing how to delegate watches, act on reports, and steer the fleet over time. This Skill is the operating manual for that human–scout working relationship.

Core Features & Use Cases

  • Fleet readiness checks: Verify project enrollment, roster status, emit eligibility, and paused or dry-run scouts before delegating any watching job.
  • Delegation guidance: Choose the cheapest path for a watch job — a note, a config tune, a skill edit, or a new custom scout — with worked recipes for common asks like watching a new event or quieting a noisy fleet.
  • Feedback and calibration loops: Turn dismissals, notes, and report outcomes into steering signals, run periodic fleet health reviews, and promote recurring steers into permanent policy.
  • Use Case: A user says "have a scout watch our EU signup funnel this week" — the Skill routes this to a time-boxed note on the product-analytics scout rather than authoring a new agent.

Quick Start

Ask the assistant to check whether your PostHog project is enrolled for Signals scouts and list what each scout in the fleet currently watches.

Frequently Asked Questions about working-with-scouts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a PostHog scout to watch something specific?

First check the roster with scout-config-list to see if a canonical scout already covers the surface. If so, leave a note pointing its attention; only author a custom scout when nothing covers the surface or you need a recurring judged metric.

Why did my PostHog scout stop running or reporting?

Common causes are a paused or dry-run config, a drained enrollment, or auto-pause after reports went unengaged. Check scout-config-list for enabled and emit flags, and look at pause_reason and status fields before deeper debugging.

How do I reduce noise from PostHog Signals scouts?

Dismiss noisy reports with specific evidence-bearing notes, which are forwarded to the filing scout as steering. If noise persists, leave a general note, then edit the skill body to add disqualifiers or raise thresholds, or slow the run interval.

Can a PostHog scout watch external sites outside PostHog?

Yes, by authoring a custom scout with network_access set to full, since the sandbox defaults to a trusted-domain allowlist. Prefer pointing scouts at warehouse-synced data when available, and treat fetched external content as untrusted.

What happens to dismissal notes on scout reports?

Dismissal notes are forwarded to the scout that filed the report and read as prior context on future runs, provided the dismisser has scout-steering access. They expire after about 30 days unless the scout folds them into scratchpad memory.