Telemetry Analytics
OpenHands/OpenHands
This skill should be used when the user asks to "add tracking", "add a PostHog event", "change telemetry consent", "instrument onboarding", "debug analytics", or changes telemetry.ts…
Work with PostHog Signals scouts: scheduled agents that monitor a project and write reports into the Signals inbox.
Install Working With Scouts
$ npx skills add PostHog/posthog --skill working-with-scouts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog working-with-scouts --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/signals/skills/working-with-scouts .claude/skills/working-with-scouts && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "working-with-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/working-with-scouts into .claude/skills/working-with-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-scouts", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog/tree/master/products/signals/skills/working-with-scoutsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog --skill working-with-scouts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog working-with-scouts --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/products/signals/skills/working-with-scouts .agents/skills/working-with-scouts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "working-with-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/working-with-scouts into .agents/skills/working-with-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-scouts", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill working-with-scouts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog working-with-scouts --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/products/signals/skills/working-with-scouts .cursor/skills/working-with-scouts && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "working-with-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/working-with-scouts into .cursor/skills/working-with-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-scouts", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog.git --path products/signals/skills/working-with-scouts--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog --skill working-with-scouts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog working-with-scouts --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/products/signals/skills/working-with-scouts .gemini/skills/working-with-scouts && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "working-with-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/working-with-scouts into .gemini/skills/working-with-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-scouts", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog working-with-scoutsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog --skill working-with-scouts -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/products/signals/skills/working-with-scouts .github/skills/working-with-scouts && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "working-with-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/working-with-scouts into .github/skills/working-with-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-scouts", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill working-with-scouts -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog working-with-scouts --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/products/signals/skills/working-with-scouts .opencode/skills/working-with-scouts && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "working-with-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/working-with-scouts into .opencode/skills/working-with-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-scouts", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
working-with-scouts- GitHub stars
- 40k
- Token cost
- ~8.7k tokens
- SKILL.md length
- 4,468 words
- Files
- 2 (incl. references)
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Work with PostHog Signals scouts: scheduled agents that monitor a project and write reports into the Signals inbox.
- Works in 5 steps: Delegate — decide what the fleet should… → Receive — reports land in the inbox,… → Act — verify the finding, fix it (or… → …
- Assign monitoring work
- SKILL.md covers First: is the fleet running?, The working loop, Delegating a job and Acting on what comes back, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Working With Scouts is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Work with PostHog Signals scouts: scheduled agents that monitor a project and write reports into the Signals inbox. Use to assign monitoring work, schedule quality scoring, find which scout covers a surface, act on reports, reduce noise, investigate missing findings, or improve the fleet through feedback and calibration. Also covers follow-up checks that verify whether a reported problem stays fixed. Use authoring-scouts for edits, exploring-scouts for run observability, and inbox-exploration for report triage…
Its SKILL.md is about 8.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/delegation-recipes.md`).
It sits in DevOps & Cloud, covering Email management, Performance reviews and Observability. It works with PostHog. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…
When your agent uses it
- Assign monitoring work
- Schedule quality scoring
- Find which scout covers a surface
- Investigate missing findings
Example prompts
- “work with my scouts”
- “get more out of scouts”
- “have a scout watch X”
- “/working-with-scouts”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Delegate — decide what the fleet should watch, and get the right scout watching it.
- Receive — reports land in the inbox, routed to a suggested reviewer when the scout could name one.
- Act — verify the finding, fix it (or decide not to), and record the outcome on the report.
- Feed back — the outcome and your written reasons flow back to the scout, along with any notes you leave.
- Calibrate — periodically review fleet health and promote recurring steers into permanent policy.
What it can do on your machine
Read from SKILL.md and the folder at commit 812e5c6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
posthog.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Working With Scouts loads about 8.7k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 193 tokens; SKILL.md has 4,468 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 4,468 words (~8,744 tokens).
“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…”
- name
- working-with-scouts
- metadata.owner_team
- signals
Files
SKILL.md and 1 other file (references) in products/signals/skills/working-with-scouts of PostHog/posthog.
- SKILL.md
- references/delegation-recipes.md
Open the folder on GitHubat commit 812e5c6
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Working With Scouts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Working With Scouts this skillPostHog/posthog | 40k | — | ~8.7k | Automated safety check: Pass | Custom licence | |
| Telemetry AnalyticsOpenHands/OpenHands | 90k | — | ~305 | Automated safety check: Pass | MIT | |
| Temps Best Practicesgotempsh/temps | 828 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Posthog Observabilityjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Posthog Operationsshepherdjerred/monorepo | 112 | — | ~321 | Automated safety check: Pass | GPL-3.0 | |
| Sentry Miniapp SDKlizhiyao/sentry-miniapp | 687 | — | ~5.1k | Automated safety check: Pass | MIT |
Similar skills
Temps Best Practices
gotempsh/temps
Best-practices reference for preparing and instrumenting applications on Temps.
Posthog Observability
jeremylongshore/tons-of-skills-marketplace
Observe a PostHog integration through application-side delivery metrics, ingestion warnings, billing volume, destination logs, and status evidence.
Posthog Operations
shepherdjerred/monorepo
Query or manage this repository's PostHog analytics, schema, dashboards, insights, feature flags, experiments, replay, and observability through toolkit posthog.
Sentry Miniapp SDK
lizhiyao/sentry-miniapp
Full Sentry SDK setup for Mini Programs — error monitoring, tracing, offline cache, source maps.
AI Observability Langchain Python
Jwuthri/Tracely-ai
PostHog AI Observability integration for LangChain (Python). An agent skill from Jwuthri/Tracely-ai.
More from PostHog/posthog
All 252 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Categories
Questions about Working With Scouts
What does Working With Scouts do?
Work with PostHog Signals scouts: scheduled agents that monitor a project and write reports into the Signals inbox. Working With Scouts is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Work with PostHog Signals scouts: scheduled agents that monitor a project and write reports into the Signals inbox.
When should I use Working With Scouts?
Working With Scouts fits situations like: assign monitoring work; schedule quality scoring; find which scout covers a surface; investigate missing findings.
How do I install Working With Scouts in Claude Code?
Run `npx skills add PostHog/posthog --skill working-with-scouts -a claude-code`. Or copy the skill folder (products/signals/skills/working-with-scouts in PostHog/posthog) into .claude/skills/working-with-scouts in your project. Claude Code loads it when a task matches its description.
How do I install Working With Scouts in Codex?
Run `npx skills add PostHog/posthog --skill working-with-scouts -a codex`. Or copy the skill folder (products/signals/skills/working-with-scouts in PostHog/posthog) into .agents/skills/working-with-scouts in your project. Codex loads it when a task matches its description.
Can I use Working With Scouts in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill working-with-scouts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/working-with-scouts, .gemini/skills/working-with-scouts, .github/skills/working-with-scouts and .opencode/skills/working-with-scouts in your project.
What does Working With Scouts need to run?
SKILL.md names no scripts, command-line tools or credentials: Working With Scouts is instructions for the agent only.
Does Working With Scouts access the network?
SKILL.md names 1 domain. As links in the text: posthog.com. This is read from the text; nothing was executed.
Is Working With Scouts safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Working With Scouts use?
Working With Scouts has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Working With Scouts use?
About 8.7k tokens (SKILL.md is roughly 35k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.
What are the alternatives to Working With Scouts?
Skills that share tags, products or a category with Working With Scouts: Telemetry Analytics (OpenHands/OpenHands, 90k stars), Temps Best Practices (gotempsh/temps, 828 stars), Posthog Observability (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Posthog Operations (shepherdjerred/monorepo, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Working With Scouts?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,200 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.
Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.