Local Platform E2E
computesdk/benchmarks
Stand up benchmarks-platform locally (Postgres + MinIO + ClickHouse in docker) and run a real @benchsdk/runner benchmark against it, with no cloud or provider credentials.
Debug the signals pipeline locally end-to-end. An agent skill from PostHog/posthog.
Install Debugging Signals Pipeline
$ npx skills add PostHog/posthog --skill debugging-signals-pipeline -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog debugging-signals-pipeline --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/.agents/skills/debugging-signals-pipeline .claude/skills/debugging-signals-pipeline && 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 "debugging-signals-pipeline" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/debugging-signals-pipeline into .claude/skills/debugging-signals-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-signals-pipeline", 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/.agents/skills/debugging-signals-pipelineType 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 debugging-signals-pipeline -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog debugging-signals-pipeline --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/.agents/skills/debugging-signals-pipeline .agents/skills/debugging-signals-pipeline && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugging-signals-pipeline" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/debugging-signals-pipeline into .agents/skills/debugging-signals-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-signals-pipeline", 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 debugging-signals-pipeline -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog debugging-signals-pipeline --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/.agents/skills/debugging-signals-pipeline .cursor/skills/debugging-signals-pipeline && 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 "debugging-signals-pipeline" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/debugging-signals-pipeline into .cursor/skills/debugging-signals-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-signals-pipeline", 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 .agents/skills/debugging-signals-pipeline--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 debugging-signals-pipeline -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog debugging-signals-pipeline --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/.agents/skills/debugging-signals-pipeline .gemini/skills/debugging-signals-pipeline && 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 "debugging-signals-pipeline" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/debugging-signals-pipeline into .gemini/skills/debugging-signals-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-signals-pipeline", 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 debugging-signals-pipelineInstalls 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 debugging-signals-pipeline -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/.agents/skills/debugging-signals-pipeline .github/skills/debugging-signals-pipeline && 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 "debugging-signals-pipeline" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/debugging-signals-pipeline into .github/skills/debugging-signals-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-signals-pipeline", 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 debugging-signals-pipeline -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 debugging-signals-pipeline --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/.agents/skills/debugging-signals-pipeline .opencode/skills/debugging-signals-pipeline && 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 "debugging-signals-pipeline" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/debugging-signals-pipeline into .opencode/skills/debugging-signals-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-signals-pipeline", 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
debugging-signals-pipeline- GitHub stars
- 40k
- Token cost
- ~2.4k tokens
- SKILL.md length
- 495 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Debug the signals pipeline locally end-to-end. An agent skill from PostHog/posthog.
- Works in 3 steps: agentsh network denials — DENY… → No log content at all — sandbox failed… → Claude API errors — check if…
- A signal isnt reaching the inbox
- SKILL.md covers Pipeline flow, Emitting test signals, Monitoring Temporal workflows and Reading sandbox agent logs, plus 4 more sections
- Calls curl, python and docker; needs ANTHROPIC_API_KEY
What it does
Debugging Signals Pipeline is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Debug the signals pipeline locally end-to-end. Covers emitting test signals from fixtures, monitoring Temporal workflows via the REST API, reading sandbox agent logs from object storage, inspecting Docker sandbox containers, and diagnosing common failures (stale ClickHouse embeddings, agentsh network denials, inactivity timeouts). Use when a signal isn't reaching the inbox, a signal-report-summary workflow fails, or a sandbox task run times out.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering, covering Embeddings, Data warehousing and Containers. It works with ClickHouse, Docker, Temporal and 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 signal isnt reaching the inbox
- A signal-report-summary workflow fails
- A sandbox task run times out
Example prompts
- “/debugging-signals-pipeline”
Requirements
- Python 3
- Docker
- A credential in ANTHROPIC_API_KEY
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- agentsh network denials — DENY host.docker.internal means the MCP server URL is blocked
- No log content at all — sandbox failed to start, check Docker container logs.
- Claude API errors — check if ANTHROPIC_API_KEY is valid.
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
Shell commands in SKILL.md call:
curlpythondockerpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl and docker, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
ANTHROPIC_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debugging Signals Pipeline loads about 2.4k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 495 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:158
use:** `CLICKHOUSE_DATABASE` not set in `.env`. The cleanup command uses `sync_execute` - NoteMentions a .env fileSKILL.md:162
** Add `CLICKHOUSE_DATABASE=posthog` to `.env` and restart workers. - NoteMentions a .env fileSKILL.md:206
grep CLICKHOUSE_DATABASE .env
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 495 words (~2,398 tokens).
“Always clean up before re-emitting to avoid stale embeddings causing phantom report matches.”
- name
- debugging-signals-pipeline
Files
Just SKILL.md in .agents/skills/debugging-signals-pipeline of PostHog/posthog.
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
Debugging Signals Pipeline 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 |
|---|---|---|---|---|---|---|
| Debugging Signals Pipeline this skillPostHog/posthog | 40k | — | ~2.4k | Automated safety check: Notes | Custom licence | |
| Local Platform E2Ecomputesdk/benchmarks | 126 | — | ~3k | Automated safety check: Notes | MIT | |
| Cloud SaaS Modechmonitor/chmonitor | 299 | — | ~2.5k | Automated safety check: Notes | GPL-3.0 | |
| Funnelcake Deployment Workflowdivinevideo/divine-mobile | 266 | — | ~3.6k | Automated safety check: Pass | MPL-2.0 | |
| Clickhouse Local Dev Loopjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.5k | Automated safety check: Notes | MIT | |
| Dlsps Useropen-edge-platform/edge-ai-libraries | 169 | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cloud SaaS Mode
chmonitor/chmonitor
Work on chmonitor's Cloud (SaaS) vs self-hosted (OSS) behaviour from ONE codebase.
Funnelcake Deployment Workflow
divinevideo/divine-mobile
Deploy funnelcake (api + relay) to ANY environment (production, staging, poc) on GKE via ArgoCD.
Clickhouse Local Dev Loop
jeremylongshore/tons-of-skills-marketplace
Run ClickHouse locally with Docker, configure test fixtures, and iterate fast.
Dlsps User
open-edge-platform/edge-ai-libraries
Deploy and operate DL Streamer Pipeline Server — a microservice that wraps DL Streamer pipelines behind a REST API for containerized, no-code operation.
Backend Dev Guidelines
langfuse/langfuse
Build or review Langfuse backend code. An agent skill from langfuse/langfuse.
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
Questions about Debugging Signals Pipeline
What does Debugging Signals Pipeline do?
Debug the signals pipeline locally end-to-end. An agent skill from PostHog/posthog. Debugging Signals Pipeline is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Debug the signals pipeline locally end-to-end.
When should I use Debugging Signals Pipeline?
Debugging Signals Pipeline fits situations like: A signal isnt reaching the inbox; A signal-report-summary workflow fails; A sandbox task run times out.
How do I install Debugging Signals Pipeline in Claude Code?
Run `npx skills add PostHog/posthog --skill debugging-signals-pipeline -a claude-code`. Or copy the skill folder (.agents/skills/debugging-signals-pipeline in PostHog/posthog) into .claude/skills/debugging-signals-pipeline in your project. Claude Code loads it when a task matches its description.
How do I install Debugging Signals Pipeline in Codex?
Run `npx skills add PostHog/posthog --skill debugging-signals-pipeline -a codex`. Or copy the skill folder (.agents/skills/debugging-signals-pipeline in PostHog/posthog) into .agents/skills/debugging-signals-pipeline in your project. Codex loads it when a task matches its description.
Can I use Debugging Signals Pipeline 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 debugging-signals-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-signals-pipeline, .gemini/skills/debugging-signals-pipeline, .github/skills/debugging-signals-pipeline and .opencode/skills/debugging-signals-pipeline in your project.
What does Debugging Signals Pipeline need to run?
Going by SKILL.md and its folder, Debugging Signals Pipeline needs the command-line tools its instructions call (curl, python, docker and python3) and credentials named ANTHROPIC_API_KEY. Our summary lists: Python 3; Docker; A credential in ANTHROPIC_API_KEY.
Does Debugging Signals Pipeline access the network?
SKILL.md contains no URLs. Its commands use curl and docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Debugging Signals Pipeline safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Debugging Signals Pipeline use?
Debugging Signals Pipeline 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 Debugging Signals Pipeline use?
About 2.4k tokens (SKILL.md is roughly 9.6k 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 Debugging Signals Pipeline?
Skills that share tags, products or a category with Debugging Signals Pipeline: Local Platform E2E (computesdk/benchmarks, 126 stars), Cloud SaaS Mode (chmonitor/chmonitor, 299 stars), Funnelcake Deployment Workflow (divinevideo/divine-mobile, 266 stars) and Clickhouse Local Dev Loop (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 Debugging Signals Pipeline?
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.