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…
Signals scout over PostHog's own health checks. An agent skill from PostHog/posthog.
Install Signals Scout Health Checks
$ npx skills add PostHog/posthog --skill signals-scout-health-checks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog signals-scout-health-checks --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/signals-scout-health-checks .claude/skills/signals-scout-health-checks && 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 "signals-scout-health-checks" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-health-checks into .claude/skills/signals-scout-health-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-health-checks", 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/signals-scout-health-checksType 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 signals-scout-health-checks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog signals-scout-health-checks --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/signals-scout-health-checks .agents/skills/signals-scout-health-checks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "signals-scout-health-checks" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-health-checks into .agents/skills/signals-scout-health-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-health-checks", 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 signals-scout-health-checks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog signals-scout-health-checks --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/signals-scout-health-checks .cursor/skills/signals-scout-health-checks && 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 "signals-scout-health-checks" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-health-checks into .cursor/skills/signals-scout-health-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-health-checks", 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/signals-scout-health-checks--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 signals-scout-health-checks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog signals-scout-health-checks --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/signals-scout-health-checks .gemini/skills/signals-scout-health-checks && 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 "signals-scout-health-checks" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-health-checks into .gemini/skills/signals-scout-health-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-health-checks", 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 signals-scout-health-checksInstalls 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 signals-scout-health-checks -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/signals-scout-health-checks .github/skills/signals-scout-health-checks && 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 "signals-scout-health-checks" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-health-checks into .github/skills/signals-scout-health-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-health-checks", 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 signals-scout-health-checks -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 signals-scout-health-checks --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/signals-scout-health-checks .opencode/skills/signals-scout-health-checks && 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 "signals-scout-health-checks" agent skill from https://github.com/PostHog/posthog/tree/master/products/signals/skills/signals-scout-health-checks into .opencode/skills/signals-scout-health-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signals-scout-health-checks", 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
signals-scout-health-checks- GitHub stars
- 40k
- Token cost
- ~5.8k tokens
- SKILL.md length
- 2,945 words
- Files
- 1
- Skills in repo
- 254
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Signals scout over PostHog's own health checks. An agent skill from PostHog/posthog.
- Works in 5 steps: Critical first → Kind clusters → one bundled finding → Weight by real blast radius → …
- DevOps & Cloud work in your project
- SKILL.md covers Quick close-out: is anything…, How a run works, Untrusted data — payload fields and Disqualifiers (skip these), plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Signals Scout Health Checks is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Signals scout over PostHog's own health checks. Bundles the project's active health issues by kind, weights them by blast radius, and surfaces the ones worth acting on.
Its SKILL.md is about 5.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: PostHog Signals agent (Claude sandbox). Read-only analytics + signalscoutinternal:write (scratchpad) + signalscoutreport:write (report channel), plus the…
It sits in DevOps & Cloud. 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
- DevOps & Cloud work in your project
Example prompts
- “s own health checks. Bundles the project”
- “Use the signals-scout-health-checks skill to signal scout over PostHog's own health checks. An agent skill from PostHog/posthog”
- “/signals-scout-health-checks”
Requirements
- Compatibility (from SKILL.md): PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + signal_scout_report:write (report channel), plus the health-issues read tools and analytics tools in the MCP tools section.
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Critical first
- Kind clusters → one bundled finding
- Weight by real blast radius
- Agent-fixability triage
- Cross-product correlation
What it can do on your machine
Read from SKILL.md and the folder at commit c012c8d. 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
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.
Compatibility
PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + signal_scout_report:write (report channel), plus the health-issues read tools and analytics tools in the MCP tools section.
From compatibility in the SKILL.md frontmatter.
Context cost
Signals Scout Health Checks loads about 5.8k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 2,945 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 2,945 words (~5,803 tokens).
“You are a focused setup-health scout. PostHog runs its own scheduled health checks and persists what they find as health issues — each with a kind (which check found it), a severity (critical / warning / info), a status (active…”
- name
- signals-scout-health-checks
- compatibility
- PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + signal_scout_report:write (report channel), plus the health-issues read tools and analytics tools in the MCP tools section.
- scout-display-name
- Health checks
- metadata.owner_team
- signals
- metadata.scope
- health_checks
Files
Just SKILL.md in products/signals/skills/signals-scout-health-checks of PostHog/posthog.
Open the folder on GitHubat commit c012c8d
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 8, 2026.
Compare with similar skills
Signals Scout Health Checks 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 |
|---|---|---|---|---|---|---|
| Signals Scout Health Checks this skillPostHog/posthog | 40k | — | ~5.8k | Automated safety check: Pass | Custom licence | |
| Telemetry AnalyticsOpenHands/OpenHands | 91k | — | ~305 | Automated safety check: Pass | MIT | |
| Temps Best Practicesgotempsh/temps | 833 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Posthog CI Integrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2k | Automated safety check: Pass | MIT | |
| Posthog Deploy Integrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2k | Automated safety check: Pass | MIT | |
| Posthog Incident Runbookjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Temps Best Practices
gotempsh/temps
Best-practices reference for preparing and instrumenting applications on Temps.
Posthog CI Integration
jeremylongshore/tons-of-skills-marketplace
Build repository-specific PostHog CI gates for SDK initialization, typed capture tests, release annotations, and secret boundaries.
Posthog Deploy Integration
jeremylongshore/tons-of-skills-marketplace
Deploy a PostHog application integration with correct regional hosts, reverse-proxy coverage, server lifecycle, and rollback checks.
Posthog Incident Runbook
jeremylongshore/tons-of-skills-marketplace
Triage a production PostHog integration incident while preserving application availability and evidence.
Posthog Migration Deep Dive
jeremylongshore/tons-of-skills-marketplace
Plan and execute a controlled historical migration into PostHog with identity mapping, timestamp validation, dual-write evidence, and rollback boundaries.
More from PostHog/posthog
All 254 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 Signals Scout Health Checks
What does Signals Scout Health Checks do?
Signals scout over PostHog's own health checks. An agent skill from PostHog/posthog. Signals Scout Health Checks is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Signals scout over PostHog's own health checks.
When should I use Signals Scout Health Checks?
Signals Scout Health Checks fits situations like: devOps & Cloud work in your project.
How do I install Signals Scout Health Checks in Claude Code?
Run `npx skills add PostHog/posthog --skill signals-scout-health-checks -a claude-code`. Or copy the skill folder (products/signals/skills/signals-scout-health-checks in PostHog/posthog) into .claude/skills/signals-scout-health-checks in your project. Claude Code loads it when a task matches its description.
How do I install Signals Scout Health Checks in Codex?
Run `npx skills add PostHog/posthog --skill signals-scout-health-checks -a codex`. Or copy the skill folder (products/signals/skills/signals-scout-health-checks in PostHog/posthog) into .agents/skills/signals-scout-health-checks in your project. Codex loads it when a task matches its description.
Can I use Signals Scout Health Checks 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 signals-scout-health-checks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/signals-scout-health-checks, .gemini/skills/signals-scout-health-checks, .github/skills/signals-scout-health-checks and .opencode/skills/signals-scout-health-checks in your project.
What does Signals Scout Health Checks need to run?
SKILL.md names no scripts, command-line tools or credentials: Signals Scout Health Checks is instructions for the agent only. Compatibility (from SKILL.md): PostHog Signals agent (Claude sandbox). Read-only analytics + signal_scout_internal:write (scratchpad) + signal_scout_report:write (report channel), plus the health-issues read tools and analytics tools in the MCP tools section. .
Does Signals Scout Health Checks 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 Signals Scout Health Checks 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 Signals Scout Health Checks use?
Signals Scout Health Checks 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 Signals Scout Health Checks use?
About 5.8k tokens (SKILL.md is roughly 23k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Signals Scout Health Checks?
Skills that share tags, products or a category with Signals Scout Health Checks: Telemetry Analytics (OpenHands/OpenHands, 91k stars), Temps Best Practices (gotempsh/temps, 833 stars), Posthog CI Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Posthog Deploy Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Signals Scout Health Checks?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,209 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 10, 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.