Syncmeta
pawurb/hotpath-rs
Sync changes from the hotpath, hotpath-macros and hotpath-drain crates to their meta counterparts (hotpath-meta, hotpath-macros-meta and hotpath-drain-meta).
Guide for using the Grafana MCP to monitor and diagnose the capture service (rust/capture) in production.
Install Monitoring Capture Service
$ npx skills add PostHog/posthog --skill monitoring-capture-service -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog monitoring-capture-service --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/monitoring-capture-service .claude/skills/monitoring-capture-service && 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 "monitoring-capture-service" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/monitoring-capture-service into .claude/skills/monitoring-capture-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-capture-service", 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/monitoring-capture-serviceType 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 monitoring-capture-service -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog monitoring-capture-service --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/monitoring-capture-service .agents/skills/monitoring-capture-service && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "monitoring-capture-service" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/monitoring-capture-service into .agents/skills/monitoring-capture-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-capture-service", 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 monitoring-capture-service -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog monitoring-capture-service --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/monitoring-capture-service .cursor/skills/monitoring-capture-service && 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 "monitoring-capture-service" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/monitoring-capture-service into .cursor/skills/monitoring-capture-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-capture-service", 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/monitoring-capture-service--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 monitoring-capture-service -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog monitoring-capture-service --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/monitoring-capture-service .gemini/skills/monitoring-capture-service && 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 "monitoring-capture-service" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/monitoring-capture-service into .gemini/skills/monitoring-capture-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-capture-service", 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 monitoring-capture-serviceInstalls 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 monitoring-capture-service -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/monitoring-capture-service .github/skills/monitoring-capture-service && 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 "monitoring-capture-service" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/monitoring-capture-service into .github/skills/monitoring-capture-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-capture-service", 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 monitoring-capture-service -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 monitoring-capture-service --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/monitoring-capture-service .opencode/skills/monitoring-capture-service && 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 "monitoring-capture-service" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/monitoring-capture-service into .opencode/skills/monitoring-capture-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-capture-service", 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
monitoring-capture-service- GitHub stars
- 40k
- Token cost
- ~5k tokens
- SKILL.md length
- 1,510 words
- Files
- 2 (incl. references)
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Guide for using the Grafana MCP to monitor and diagnose the capture service (rust/capture) in production.
- Works in 4 steps: list_prometheus_metric_names —… → Pick a metric, then… → list_prometheus_label_values — discover… → …
- Investigating latency
- SKILL.md covers Environment context, Observability landscape, Stable waypoints and Discovery workflows, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Monitoring Capture Service is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Guide for using the Grafana MCP to monitor and diagnose the capture service (rust/capture) in production. Use when investigating latency, event loss, Kafka backpressure, Redis issues, rate limiting, Envoy proxy issues, or any capture health question. Covers prod-us and prod-eu environments.
Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/investigation-playbooks.md`).
It sits in DevOps & Cloud, covering Monitoring and alerting, Rate limiting and Event-driven systems. It works with Grafana, Model Context Protocol, Redis and Rust. 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
- Investigating latency
- Kafka backpressure
- Envoy proxy issues
- Any capture health question
Example prompts
- “/monitoring-capture-service”
Requirements
- Node.js
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- list_prometheus_metric_names — datasourceUid: "victoriametrics", regex: "capture_.*" to enumerate app metrics
- Pick a metric, then list_prometheus_label_names scoped to it — see available dimensions
- list_prometheus_label_values — discover actual values for a label
- query_prometheus with PromQL — always scope by namespace (or container) and set a time range
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
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.
Context cost
Monitoring Capture Service loads about 5k tokens when it runs, and up to ~7.4k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 1,510 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 1,510 words (~4,951 tokens).
“The capture service (rust/capture/) is PostHog's Rust HTTP ingestion endpoint. It receives events from SDKs, applies quota/rate limits, and produces to Kafka. Five deployments run the same binary with different CAPTURE_MODE configs, each in its own K8s namespace.”
- name
- monitoring-capture-service
Files
SKILL.md and 1 other file (references) in .agents/skills/monitoring-capture-service of PostHog/posthog.
- SKILL.md
- references/investigation-playbooks.md
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
Monitoring Capture Service 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 |
|---|---|---|---|---|---|---|
| Monitoring Capture Service this skillPostHog/posthog | 40k | — | ~5k | Automated safety check: Pass | Custom licence | |
| Syncmetapawurb/hotpath-rs | 1.9k | — | ~1.2k | Automated safety check: Notes | MIT | |
| Ops Reporthaacked/dotfiles | 134 | — | ~8k | Automated safety check: Notes | None | |
| FoundatioFoundatioFx/Foundatio | 2.1k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Proto Backend Moduleaide-family/moon | 253 | — | ~4.1k | Automated safety check: Pass | None | |
| Archestra Dev Observabilityarchestra-ai/archestra | 4.4k | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
Ops Report
haacked/dotfiles
Generate a 24-hour operational health report for a PostHog service by querying Grafana dashboards and Prometheus metrics.
Foundatio
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
Proto Backend Module
aide-family/moon
Implements backend modules from proto definitions for goddess, marksman, and rabbit apps.
Archestra Dev Observability
archestra-ai/archestra
A skill your agent uses when changing Archestra tracing, metrics, OpenTelemetry, Tempo, Grafana, Prometheus, LLM/MCP spans, observability labels, or local observability setup.
Frontmcp Observability
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
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
Categories
Questions about Monitoring Capture Service
What does Monitoring Capture Service do?
Guide for using the Grafana MCP to monitor and diagnose the capture service (rust/capture) in production. Monitoring Capture Service is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Guide for using the Grafana MCP to monitor and diagnose the capture service (rust/capture) in production.
When should I use Monitoring Capture Service?
Monitoring Capture Service fits situations like: investigating latency; kafka backpressure; envoy proxy issues; any capture health question.
How do I install Monitoring Capture Service in Claude Code?
Run `npx skills add PostHog/posthog --skill monitoring-capture-service -a claude-code`. Or copy the skill folder (.agents/skills/monitoring-capture-service in PostHog/posthog) into .claude/skills/monitoring-capture-service in your project. Claude Code loads it when a task matches its description.
How do I install Monitoring Capture Service in Codex?
Run `npx skills add PostHog/posthog --skill monitoring-capture-service -a codex`. Or copy the skill folder (.agents/skills/monitoring-capture-service in PostHog/posthog) into .agents/skills/monitoring-capture-service in your project. Codex loads it when a task matches its description.
Can I use Monitoring Capture Service 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 monitoring-capture-service -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monitoring-capture-service, .gemini/skills/monitoring-capture-service, .github/skills/monitoring-capture-service and .opencode/skills/monitoring-capture-service in your project.
What does Monitoring Capture Service need to run?
SKILL.md names no scripts, command-line tools or credentials: Monitoring Capture Service is instructions for the agent only. Our summary lists: Node.js.
Does Monitoring Capture Service 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 Monitoring Capture Service 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 Monitoring Capture Service use?
Monitoring Capture Service 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 Monitoring Capture Service use?
About 5k tokens (SKILL.md is roughly 20k 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 2.5k tokens, read only when the agent opens those files.
What are the alternatives to Monitoring Capture Service?
Skills that share tags, products or a category with Monitoring Capture Service: Syncmeta (pawurb/hotpath-rs, 1.9k stars), Ops Report (haacked/dotfiles, 134 stars), Foundatio (FoundatioFx/Foundatio, 2.1k stars) and Proto Backend Module (aide-family/moon, 253 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Monitoring Capture Service?
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.