Posthog Webhooks Events
jeremylongshore/tons-of-skills-marketplace
Build and verify PostHog realtime webhook destinations and bounded private-API or HogQL event queries.
Author error tracking alerts that fire when an issue is created, reopened, or starts spiking.
Install Authoring Error Tracking Alerts
$ npx skills add PostHog/posthog --skill authoring-error-tracking-alerts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog authoring-error-tracking-alerts --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/error_tracking/skills/authoring-error-tracking-alerts .claude/skills/authoring-error-tracking-alerts && 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 "authoring-error-tracking-alerts" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/authoring-error-tracking-alerts into .claude/skills/authoring-error-tracking-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "authoring-error-tracking-alerts", 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/error_tracking/skills/authoring-error-tracking-alertsType 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 authoring-error-tracking-alerts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog authoring-error-tracking-alerts --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/error_tracking/skills/authoring-error-tracking-alerts .agents/skills/authoring-error-tracking-alerts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "authoring-error-tracking-alerts" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/authoring-error-tracking-alerts into .agents/skills/authoring-error-tracking-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "authoring-error-tracking-alerts", 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 authoring-error-tracking-alerts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog authoring-error-tracking-alerts --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/error_tracking/skills/authoring-error-tracking-alerts .cursor/skills/authoring-error-tracking-alerts && 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 "authoring-error-tracking-alerts" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/authoring-error-tracking-alerts into .cursor/skills/authoring-error-tracking-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "authoring-error-tracking-alerts", 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/error_tracking/skills/authoring-error-tracking-alerts--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 authoring-error-tracking-alerts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog authoring-error-tracking-alerts --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/error_tracking/skills/authoring-error-tracking-alerts .gemini/skills/authoring-error-tracking-alerts && 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 "authoring-error-tracking-alerts" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/authoring-error-tracking-alerts into .gemini/skills/authoring-error-tracking-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "authoring-error-tracking-alerts", 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 authoring-error-tracking-alertsInstalls 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 authoring-error-tracking-alerts -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/error_tracking/skills/authoring-error-tracking-alerts .github/skills/authoring-error-tracking-alerts && 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 "authoring-error-tracking-alerts" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/authoring-error-tracking-alerts into .github/skills/authoring-error-tracking-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "authoring-error-tracking-alerts", 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 authoring-error-tracking-alerts -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 authoring-error-tracking-alerts --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/error_tracking/skills/authoring-error-tracking-alerts .opencode/skills/authoring-error-tracking-alerts && 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 "authoring-error-tracking-alerts" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/authoring-error-tracking-alerts into .opencode/skills/authoring-error-tracking-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "authoring-error-tracking-alerts", 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
authoring-error-tracking-alerts- GitHub stars
- 40k
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,251 words
- Files
- 3 (incl. references)
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Author error tracking alerts that fire when an issue is created, reopened, or starts spiking.
- Works in 5 steps: Confirm intent → Dedupe against existing alerts → Pick the integration → …
- The user asks to set up error notifications
- SKILL.md covers When to use this skill, When not to use this skill, Tools and Trigger events — pick exactly…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Authoring Error Tracking Alerts is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack/webhook/Linear, or evaluate which error events are worth alerting on. Covers trigger-event selection, integration choice, dedup against existing alerts, and shipping with the canonical message body shape.
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/block-templates.md` and `references/event-triggers.md`).
It sits in Backend & APIs, covering Webhooks. It works with Slack 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
- The user asks to set up error notifications
- Route exceptions to Slack/webhook/Linear
- Evaluate which error events are worth alerting on
Example prompts
- “/authoring-error-tracking-alerts”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Confirm intent
- Dedupe against existing alerts
- Pick the integration
- Create the alert
- Verify
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 (its code samples are json).
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
Authoring Error Tracking Alerts loads about 2.8k tokens when it runs, and up to ~6.7k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 1,251 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,251 words (~2,751 tokens).
“Authoring an error tracking alert is a routing problem, not a measurement problem. The trigger events already exist and fire on real conditions in the ingestion pipeline — your job is to pick the right trigger for the user's intent…”
- name
- authoring-error-tracking-alerts
Files
SKILL.md and 2 other files (references) in products/error_tracking/skills/authoring-error-tracking-alerts of PostHog/posthog.
- SKILL.md
- references/block-templates.md
- references/event-triggers.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
Authoring Error Tracking Alerts 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 |
|---|---|---|---|---|---|---|
| Authoring Error Tracking Alerts this skillPostHog/posthog | 40k | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Posthog Webhooks Eventsjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Channel Debug Corevercel-labs/vercel-openclaw-archived | 117 | — | ~2k | Automated safety check: Notes | MIT | |
| Frontmcp Channelsagentfront/frontmcp | 146 | — | ~3.7k | Automated safety check: Pass | Apache-2.0 | |
| Add OAuth Integrationrome-os/rome | 725 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Chat SDK Botslobehub/lobehub | 83k | — | ~1.5k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Channel Debug Core
vercel-labs/vercel-openclaw-archived
Channel webhook triage for vercel-openclaw Slack/Telegram/Discord/WhatsApp issues: prove deployment state, collect admin readiness endpoints, build evidence-first handoff before fixes.
Frontmcp Channels
agentfront/frontmcp
A skill your agent uses when pushing real-time notifications or events into Claude Code (or another MCP client) sessions, or building two-way chat bridges.
Add OAuth Integration
rome-os/rome
Add a new Rome-managed OAuth integration for a third-party service so a user can delegate access by clicking Connect, and Rome can act on the service with the delegated token (the GitHub/Slack model…
Chat SDK Bots
lobehub/lobehub
Builds chat bots once for Slack, Teams, Google Chat, Discord, GitHub and Linear with the Chat SDK, covering event handlers, cards, modals, streaming and state adapters.
Workspace API
friday-platform/friday-studio
Create, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYDURL.
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 Authoring Error Tracking Alerts
What does Authoring Error Tracking Alerts do?
Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Authoring Error Tracking Alerts is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Author error tracking alerts that fire when an issue is created, reopened, or starts spiking.
When should I use Authoring Error Tracking Alerts?
Authoring Error Tracking Alerts fits situations like: the user asks to set up error notifications; route exceptions to Slack/webhook/Linear; evaluate which error events are worth alerting on.
How do I install Authoring Error Tracking Alerts in Claude Code?
Run `npx skills add PostHog/posthog --skill authoring-error-tracking-alerts -a claude-code`. Or copy the skill folder (products/error_tracking/skills/authoring-error-tracking-alerts in PostHog/posthog) into .claude/skills/authoring-error-tracking-alerts in your project. Claude Code loads it when a task matches its description.
How do I install Authoring Error Tracking Alerts in Codex?
Run `npx skills add PostHog/posthog --skill authoring-error-tracking-alerts -a codex`. Or copy the skill folder (products/error_tracking/skills/authoring-error-tracking-alerts in PostHog/posthog) into .agents/skills/authoring-error-tracking-alerts in your project. Codex loads it when a task matches its description.
Can I use Authoring Error Tracking Alerts 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 authoring-error-tracking-alerts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/authoring-error-tracking-alerts, .gemini/skills/authoring-error-tracking-alerts, .github/skills/authoring-error-tracking-alerts and .opencode/skills/authoring-error-tracking-alerts in your project.
What does Authoring Error Tracking Alerts need to run?
SKILL.md names no scripts, command-line tools or credentials: Authoring Error Tracking Alerts is instructions for the agent only.
Does Authoring Error Tracking Alerts 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 Authoring Error Tracking Alerts 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 Authoring Error Tracking Alerts use?
Authoring Error Tracking Alerts 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 Authoring Error Tracking Alerts use?
About 2.8k tokens (SKILL.md is roughly 11k 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 4k tokens, read only when the agent opens those files.
What are the alternatives to Authoring Error Tracking Alerts?
Skills that share tags, products or a category with Authoring Error Tracking Alerts: Posthog Webhooks Events (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Channel Debug Core (vercel-labs/vercel-openclaw-archived, 117 stars), Frontmcp Channels (agentfront/frontmcp, 146 stars) and Add OAuth Integration (rome-os/rome, 725 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Authoring Error Tracking Alerts?
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.