posthog-debugger

Complete set of all PostHog skills for agents and power users

79 skills · hooks

Skills for integrating PostHog analytics into your application

33 skills

Skills for implementing PostHog feature flags across frameworks

18 skills

Skills for setting up PostHog error tracking across frameworks

16 skills

Skills for setting up PostHog log capture

8 skills

Skills for monitoring LLM usage with PostHog

2 skills

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer

8 skills · 1 MCP server

Connect Claude Code directly to your CockroachDB clusters for hands-on database work — explore schemas, write optimized SQL, debug queries, and manage distributed database clusters. This plugin provides 14 tools across two active MCP backends (self-hosted MCP Toolbox and managed CockroachDB Cloud MCP Server), three specialized agents (DBA, Developer, Operator), 32 skills across 6 operational domains, and built-in safety hooks.

34 skills · 3 agents · 3 MCP servers · hooks

Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams

6 skills · 7 commands · 4 agents

Plan, build, and debug Zoom integrations across REST APIs, Meeting SDK, Video SDK, webhooks, bots, and MCP workflows. Search meetings, retrieve recordings, access transcripts, and design AI-powered Zoom experiences.

44 skills · 3 MCP servers

Answer questions about past agent runs from the recording, not from memory. Three read-only stdlib scripts over the session transcripts Claude Code and Codex already write: a finder that locates the run by repo, time window, touched file or command text; a timeline that numbers every step with its exit code, lists every file changed (flagging changes the agent never mentioned) and walks back from any step with each causal edge labelled recorded or inferred by a named rule; and a claim checker that tests a summary's claims (ran, passed, edited, not-edited, read) against the run and catches tests that passed before a later edit and exit codes that belong to the last command of a pipe. Secrets are always redacted. A UserPromptSubmit hook gives the agent this session's transcript path when a prompt asks about past work. Ships cs-run-forensics agent, /cs-run-forensics and /cs-check-claims commands and 3 cited references.

1 skill · 2 commands · 1 agent · hooks