authoring-scouts — Claude Code skill: what it does, how to install
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.
no license 196 installs ★ 101 updated 2026-11-16
npx skills add PostHog/ai-plugin --skill authoring-scouts -a claude-codeWhat authoring-scouts does
This skill instructs your coding assistant on constructing and updating PostHog Signals scouts. A scout runs on a set schedule, inspects metrics within a designated PostHog workspace, and pushes insights directly to the Signals inbox or connected Slack destinations. You can write fresh scouts for bespoke telemetry or adjust existing canonical scouts when standard alerts turn noisy.
Work begins with discovery calls. Agents run posthog:scout-project-profile-get alongside posthog:read-data-schema to confirm that required event names actually arrive from real users. Drafting instructions for nonexistent telemetry fails instantly, so schema checks happen before generating files.
The harness recently migrated its tool names from signals-scout-* to scout-*. If an environment returns errors for the updated prefixes, the skill directs the agent to query the tool registry and fall back to the older naming scheme.
What it helps with
- author custom Signals scouts for untracked business funnels
- tighten thresholds and disqualifiers on noisy canonical scouts
- route structured evaluation reports straight into Slack
- verify workspace event schemas before setting up scout configurations
Example prompts for the agent
- Author a Signals scout that monitors payment failure events
- Tune my scout schedule and alert thresholds for web analytics
- Set up structured report output to Slack for this scout
How to install authoring-scouts
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill authoring-scouts -a claude-code2Manually: put the files in place
~/.claude/skills/authoring-scouts/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/authoring-scouts/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill authoring-scouts -a codex2Manually: put the files in place
.agents/skills/authoring-scouts/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill authoring-scouts -a cursor2Manually: put the files in place
.cursor/skills/authoring-scouts/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/ai-plugin skills/authoring-scouts2Manually: put the files in place
.github/skills/authoring-scouts/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill authoring-scouts -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/ai-plugin --path skills/authoring-scoutsManually: put the files in place
.devin/skills/authoring-scouts/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill authoring-scouts -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about authoring-scouts
How to install authoring-scouts in Claude Code?
Run npx skills add PostHog/ai-plugin --skill authoring-scouts -a claude-code in your terminal shell.
What does authoring-scouts do?
It guides your assistant through writing SKILL.md prompts, managing scout configs, and validating PostHog telemetry before launching scheduled monitors.
What happens if scout tools fail with unknown command errors?
Scout tooling recently switched names from signals-scout-* to scout-*; inspect your catalog and call the legacy prefix if the newer one is not exposed yet.