Skip to main content
skill CX Codex

exploring-scouts — Claude Code skill: what it does, how to install

exploring-scouts reads the state of PostHog Signals scouts: which ones a project has, how recent runs went, and where their reports ended up. Read-only.

no license 197 installs ★ 101 updated 2026-11-10

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add PostHog/ai-plugin --skill exploring-scouts -a claude-code
Open on GitHub

What exploring-scouts does

This skill inspects the scouts of PostHog Signals, the agents that wake on a schedule, look at one project and file what they find into the Signals inbox. Handy when you want to know what a scout has been up to, or why a run came back with nothing.

Every call goes through read-only MCP tools. scout-config-list gives the roster and the schedules; from there you can open recent runs, walk through the reasoning of a single run, check the scratchpad memory the fleet keeps, and follow a run to the reports it wrote or edited. Health questions come off the same rows: how often it fires, how many runs succeed, how much noise it makes.

Nothing here writes or tunes a scout, that is what authoring-scouts covers. A zero in emitted_count is not an idle run: the column belongs to an older output channel and stays at zero for scouts that publish reports. If a scout-* name comes back unknown, look for the legacy signals-scout-* name in the tool catalog.

What it helps with

  • see which scouts a project has and when each one fires
  • find out why a run reported nothing
  • follow a run to the reports it created or changed
  • judge a scout's cadence and success rate over time
  • read the memory the fleet built up between runs

Example prompts for the agent

  • What are my scouts doing right now, and on what schedule?
  • Walk me through the last run of my error-tracking scout and what it wrote
  • Why did this scout find nothing on its last run?

How to install exploring-scouts

1Skills CLI (Vercel)

npx skills add PostHog/ai-plugin --skill exploring-scouts -a claude-code

2Manually: put the files in place

~/.claude/skills/exploring-scouts/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/exploring-scouts/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about exploring-scouts

How do I install exploring-scouts in Claude Code?

Run npx skills add PostHog/ai-plugin --skill exploring-scouts -a claude-code. The skill file lands at ~/.claude/skills/exploring-scouts/SKILL.md.

What does exploring-scouts do?

It surveys a project's PostHog Signals scouts: schedules, recent runs, scratchpad memory and the reports they filed. All of it through read-only MCP tools, with no writes.

How is it different from authoring-scouts?

This one only reads and explains: what exists, how it ran, where the reports went. Writing a new scout or tuning an existing one belongs to authoring-scouts.

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set82

The whole set →
checking-deploy-timing checking-deploy-timing tells you when a commit or PR reached prod-us or prod-eu by reading PostHog's hidden deploy annotations and matching them against the merge commit on GitHub. CX Codex +1 200installs setting-up-a-custom-rest-source setting-up-a-custom-rest-source — a skill for Claude Code and Codex that links arbitrary REST APIs to the PostHog data warehouse using a JSON manifest. Activates when importing custom endpoints without native connectors. CX Codex +1 199installs exploring-ai-failures exploring-ai-failures reads real production traces from PostHog and returns a ranked list of the ways your LLM feature breaks. CX Codex +1 198installs resolving-ingestion-warnings resolving-ingestion-warnings walks through PostHog ingestion warnings: dropped events, rejected person merges, oversized payloads. Use it when event counts look low or identify calls misbehave. CX Codex +1 197installs debugging-surveys debugging-surveys investigates why PostHog Surveys fail to appear or record complete answers. Useful for support cases involving targeting, SDK behavior, and stored responses. CX Codex +1 197installs authoring-scouts authoring-scouts is a Claude Code skill for creating, tuning, and testing PostHog Signals scouts that inspect project metrics on a schedule and submit findings. CX Codex +1 196installs creating-online-evaluations creating-online-evaluations — a Claude Code skill that turns production failure modes into continuously-running online evaluations in PostHog. It starts when new generations need automatic scoring against specific errors. CX Codex +1 195installs signals-scout-insight-alerts signals-scout-insight-alerts — a Claude Code skill for reviewing insight alert history in PostHog. It scans recent alert triggers and flags material incidents that missed notifying the team. CX Codex +1 195installs

Project sponsors

Companies that keep this analytics open