Process Inbox
telegramdesktop/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox.
Install Exploring Scouts
$ npx skills add PostHog/posthog --skill exploring-scouts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog exploring-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/exploring-scouts .claude/skills/exploring-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 "exploring-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/exploring-scouts into .claude/skills/exploring-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-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/exploring-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 exploring-scouts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog exploring-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/exploring-scouts .agents/skills/exploring-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 "exploring-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/exploring-scouts into .agents/skills/exploring-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-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 exploring-scouts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog exploring-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/exploring-scouts .cursor/skills/exploring-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 "exploring-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/exploring-scouts into .cursor/skills/exploring-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-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/exploring-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 exploring-scouts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog exploring-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/exploring-scouts .gemini/skills/exploring-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 "exploring-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/exploring-scouts into .gemini/skills/exploring-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-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 exploring-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 exploring-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/exploring-scouts .github/skills/exploring-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 "exploring-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/exploring-scouts into .github/skills/exploring-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-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 exploring-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 exploring-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/exploring-scouts .opencode/skills/exploring-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 "exploring-scouts" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/exploring-scouts into .opencode/skills/exploring-scouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-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
exploring-scouts- GitHub stars
- 40k
- Token cost
- ~11k tokens
- SKILL.md length
- 5,818 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox.
- Works in 2 steps: scout-config-list — the roster. → scout-runs-list once with a small limit…
- A user wants to understand what scouts they have
- SKILL.md covers Output handling: expect to…, Start here: is the fleet even…, Workflow: survey the fleet and Workflow: understand one scout…, plus 7 more sections
- Runs Python scripts from its folder; calls python
What it does
Exploring Scouts is an agent skill from PostHog/posthog, published by the product's own GitHub organization. How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to understand what scouts they have, how each one is behaving, and whether the fleet is actually working. Covers surveying the fleet and its schedules, reading recent scout runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory the fleet has built up, tracing a run to the reports it wrote or edited, reading the…
Its SKILL.md is about 11k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/assessing-performance.md`, `references/scout-data-model.md` and `scripts/assess_health.py`).
It sits in Productivity & Automation, covering Email management. 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
- A user wants to understand what scouts they have
- How each one is behaving
- Whether the fleet is actually working
- What are my scouts doing
Example prompts
- “what are my scouts doing”
- “how is my <x scout performing”
- “show me recent scout runs”
- “/exploring-scouts”
Requirements
- Python 3
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- scout-config-list — the roster.
- scout-runs-list once with a small limit and pick the newest run per skill_name (runs come back newest-first across the whole fleet, so one…
What it can do on your machine
Read from SKILL.md and the folder at commit 10f9ad7. 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
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Exploring Scouts loads about 11k tokens when it runs, and up to ~25k if it reads all its reference files. Until then it costs about 248 tokens; SKILL.md has 5,818 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); the scripts in this folder 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 5,818 words (~11,262 tokens).
“A scout is a scheduled agent that wakes on its own interval, looks at one PostHog project, decides what's genuinely worth surfacing, and either writes it into the Signals inbox as a report or closes out empty (a real, valid…”
- name
- exploring-scouts
- metadata.owner_team
- signals
Files
SKILL.md and 5 other files (scripts, references) in products/signals/skills/exploring-scouts of PostHog/posthog.
- SKILL.md
- references/assessing-performance.md
- references/scout-data-model.md
- scripts/assess_health.py
- scripts/fleet_survey.py
- scripts/render_run_report.py
Open the folder on GitHubat commit 10f9ad7
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
Exploring 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 |
|---|---|---|---|---|---|---|
| Exploring Scouts this skillPostHog/posthog | 40k | — | ~11k | Automated safety check: Pass | Custom licence | |
| Process Inboxtelegramdesktop/tdesktop | 33k | 2 repos | ~4.5k | Automated safety check: Pass | GPL-3.0 | |
| Continuetelegramdesktop/tdesktop | 33k | 2 repos | ~9.4k | Automated safety check: Pass | GPL-3.0 | |
| Garden Inboxpaperclipai/paperclip | 99k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Career-Ops Gmail Lead Plugincareer-ops-hq/career-ops | 74k | — | ~233 | Automated safety check: Notes | MIT | |
| Skill CompassEvol-ai/SkillCompass | 216 | 1 repos | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Continue
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
Garden Inbox
paperclipai/paperclip
Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.
Career-Ops Gmail Lead Plugin
career-ops-hq/career-ops
Pulls job leads from a Gmail label into the career-ops pipeline, extracting job URLs from DMARC-passing emails and de-duplicating against existing leads.
Skill Compass
Evol-ai/SkillCompass
Evaluate skill quality, find the weakest dimension, and apply directed improvements.
Atomicmail
Atomic-Mail/atomic-mail-agentic
Read and write email through the Atomic Mail from an AI agent.
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 Exploring Scouts
What does Exploring Scouts do?
How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Exploring Scouts is an agent skill from PostHog/posthog, published by the product's own GitHub organization. How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox.
When should I use Exploring Scouts?
Exploring Scouts fits situations like: A user wants to understand what scouts they have; how each one is behaving; whether the fleet is actually working; what are my scouts doing.
How do I install Exploring Scouts in Claude Code?
Run `npx skills add PostHog/posthog --skill exploring-scouts -a claude-code`. Or copy the skill folder (products/signals/skills/exploring-scouts in PostHog/posthog) into .claude/skills/exploring-scouts in your project. Claude Code loads it when a task matches its description.
How do I install Exploring Scouts in Codex?
Run `npx skills add PostHog/posthog --skill exploring-scouts -a codex`. Or copy the skill folder (products/signals/skills/exploring-scouts in PostHog/posthog) into .agents/skills/exploring-scouts in your project. Codex loads it when a task matches its description.
Can I use Exploring 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 exploring-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/exploring-scouts, .gemini/skills/exploring-scouts, .github/skills/exploring-scouts and .opencode/skills/exploring-scouts in your project.
What does Exploring Scouts need to run?
Going by SKILL.md and its folder, Exploring Scouts needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Exploring Scouts access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Exploring 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Exploring Scouts use?
Exploring 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 Exploring Scouts use?
About 11k tokens (SKILL.md is roughly 45k 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 14k tokens, read only when the agent opens those files.
What are the alternatives to Exploring Scouts?
Skills that share tags, products or a category with Exploring Scouts: Process Inbox (telegramdesktop/tdesktop, 33k stars), Continue (telegramdesktop/tdesktop, 33k stars), Garden Inbox (paperclipai/paperclip, 99k stars) and Career-Ops Gmail Lead Plugin (career-ops-hq/career-ops, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Exploring Scouts?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,182 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 8, 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.