Skip to content
TrustedSkillsbeta
Back to all skills

Ingestion Pipeline Doctor Nodejs

Official
posthog·vlatest·backend

Diagnoses and optimizes Node.js ingestion pipelines in Posthog to improve data collection efficiency and reliability.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add posthog/posthog --skill ingestion-pipeline-doctor-nodejs -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

posthog

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned posthog/posthog at edc1585d12.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
edc1585d12
Manifest
.agents/skills/ingestion-pipeline-doctor-nodejs/SKILL.md
Scanned
1 file, 72 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The ingestion-pipeline-doctor-nodejs skill diagnoses and fixes issues within Node.js based ingestion pipelines, specifically those used by PostHog. It analyzes logs, identifies error patterns, and suggests corrective actions to ensure data is flowing correctly into the system. The tool helps maintain data integrity and performance of the PostHog platform.

When to use it

  • Data Loss: When you suspect data loss in your PostHog instance due to pipeline errors.
  • Performance Degradation: When ingestion pipeline performance slows down, impacting real-time analytics.
  • Error Investigation: To quickly pinpoint the root cause of specific error messages appearing in PostHog's logs related to data ingestion.
  • Proactive Maintenance: As part of a regular maintenance routine to identify and address potential issues before they impact users.

Key capabilities

  • Log analysis for Node.js ingestion pipelines
  • Error pattern identification
  • Diagnostic suggestions & corrective actions
  • PostHog specific pipeline support

Example prompts

  • "Analyze the PostHog ingestion logs from the last 24 hours and identify any recurring errors."
  • "What are the most common causes of data loss in our Node.js ingestion pipelines?"
  • "Suggest a fix for this error message: 'Error: Connection refused' appearing in the PostHog ingestion pipeline."

Tips & gotchas

This skill is specifically designed for PostHog users and requires familiarity with their ingestion pipeline architecture. Incorrect configuration or lack of access to relevant logs will hinder its effectiveness.