스킬 레이더 · GITHUB
실제 사용량으로 검증된 유용한 Agent Skills.
공개 저장소의 검증된 Skills를 기능, 패키지 구성, 설치 수, 출처 근거에 따라 비교할 수 있습니다.
- 카탈로그 범위
- 검증 완료
- Skills
- 5,771
- 저장소
- 824
- 최근 동기화
- 2026. 9. 8.
posthogcontext-layer-consolidation
Keep the context wiki coherent using the deterministic lint report queue
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogcontext-layer-dreaming
Synthesizes recent organizational activity into a durable context wiki. Use when running a nightly or incremental context-layer dream, or when updating sourced organizational context from completed work.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogcontext-layer-health-check
Semantic review of context wiki quality after deterministic consolidation
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogcreating-box-plot-insights
- Creates product analytics or SQL-backed box plot insights in PostHog. Use when a user asks to create, build, or save a box plot, visualize a numeric distribution, compare quartiles or medians across dates or groups, or turn SQL results into a box plot. Chooses between a standard Trends box plot and a SQL insight, validates the distribution data, saves the insight, and verifies it.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogcreating-replay-vision-scanners
Guides agents through creating and safely sizing a Replay Vision scanner: choosing the scanner type (monitor/classifier/scorer/summarizer), shaping the RecordingsQuery that selects sessions, and — crucially — estimating the credits it will spend and checking the org's remaining budget before creating, so a broad scanner doesn't exhaust the budget on its first scheduled sweep.\nTRIGGER when: user asks to create, set up, or configure a Replay Vision scanner, OR when you are about to call vision-scanners-create, OR when widening an existing scanner's query, samplingrate, or samplingmode (or moving it to a pricier model) via vision-scanners-update.\nDO NOT TRIGGER when: only reading scanners or observations, deleting a scanner, or running an existing scanner against a single session on demand (vision-scanners-scan-session). For a one-off question about sessions you already have, use vision-scanners-inline-scan-create rather than creating a scanner — the skill's first section covers when that applies.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogdebugging-mcp-analytics
Debug, support, and build PostHog MCP Analytics — product analytics for MCP servers (the @posthog/mcp and posthog.mcp SDKs plus the mcpanalytics product). Use when MCP analytics data looks wrong or missing ("events aren't showing", "intent clusters are empty", "sessions are missing", "per-tool numbers look wrong"), when writing queries over $mcp events by hand, or when doing feature work on the SDKs, the dashboard and its query runners, the self-instrumented MCP server, the wizard mcp-analytics install command, or the in-app onboarding. Covers the repo map, the $mcp vocabulary and where each property comes from, the rules that silently corrupt metrics when ignored, the end-to-end pipeline and where each stage breaks, and which repo to change. For reading the data rather than fixing it, prefer the exploring-mcp- and improving-mcp-tools skills.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogdebugging-signals-pipeline
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.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogdesigning-email-templates
Author, save, and edit email templates in the PostHog workflows library — compose email design JSON with Liquid personalization and create and round-trip-edit templates over MCP. Use when asked to design, build, update, or fix an email template for workflows, broadcasts, or campaigns.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogdiagnosing-endpoint-performance
Diagnose why a PostHog endpoint is slow or expensive and propose a concrete fix — bump the cache TTL, enable materialisation, restructure variables, or rewrite the query. Use when the user says "this endpoint is slow", "my endpoint times out", "we're hitting the cost cap on this one", or asks "should I materialise this?". Focuses on a single named endpoint, not a project-wide audit.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogdiagnosing-failed-warehouse-syncs
Diagnose why a data warehouse sync is failing and recommend the right recovery action. Use when the user asks "why isn't my Stripe/Postgres/Hubspot sync working?", "this table has been stuck for hours", "the data in the warehouse looks wrong", or wants to troubleshoot a specific source or schema. Covers source-level vs schema-level failures, stuck Running states, credential and schema-drift errors, incremental-field misconfig, CDC prerequisite failures, and the cancel / reload / resync / delete-data recovery actions.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogdiagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling, triggers, ad blockers, and quota/billing scenarios.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogdiagnosing-stacktrace-symbolication
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). The PostHog symbol-set lookup flow is universal across platforms; build-tool and artifact details live in per-platform references (JavaScript is fleshed out, others come as we encounter them). Use when stack frames stay minified or obfuscated after symbols are uploaded, PostHog symbol sets show lastused but frames are not readable, chunk IDs or dSYM UUIDs do not match, "Token not found" appears, uploaded source maps / dSYMs / Proguard mappings look empty, or bundler / symbol-upload configuration needs troubleshooting.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogdownloading-batch-export-files
Export PostHog events, persons, sessions, or the results of a HogQL query on demand and download the resulting files. Use when the user asks to download/export raw PostHog data, export HogQL query results, create a one-off file export, fetch a Parquet or JSONLines export, or use the filedownloadbatchexports API. Covers starting the export with MCP, polling completion, and downloading via the existing REST redirect endpoint.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogexploring-autocapture-events
Guides exploration of $autocapture events captured by posthog-js to understand user interactions, find CSS selectors (especially data-attr attributes), evaluate selector uniqueness, query matching clicks ad-hoc, and create actions. Use when the user asks about autocapture data, wants to find what users are clicking, needs to build actions from click events, asks about elementschain, wants to build a trend or funnel filtered by clicks or other autocapture interactions, asks which properties autocapture sends, or asks how to filter $autocapture events. Only applies to projects using posthog-js autocapture.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogexploring-endpoint-execution-logs
Explore and diagnose a PostHog endpoint's execution logs — error messages, failed runs, cache misses, slow runs, or unexpected row counts during endpoint invocations. Use when the user says "my endpoint is failing", "show me the logs for endpoint X", "what error did endpoint Y produce", "why did endpoint Z return no rows", "is this endpoint hitting cache", or "check the last N runs". Focused on a single named endpoint's runtime log entries, not project-wide auditing or query performance profiling.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogexploring-llm-costs
Investigate LLM spend in PostHog — total cost over time, cost by model, provider, user, trace, or custom dimension, token and cache-hit economics, and cost regressions. Use when the user asks "how much are we spending on LLMs?", "which model / user / feature is most expensive?", "why did cost spike?", wants to build a cost dashboard or alert, or pastes a trace URL and asks about its cost.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogexploring-llm-evaluations
Investigate AI observability evaluations — hog (deterministic code-based), llmjudge (LLM-prompt-based), and sentiment (user-message sentiment). Find existing evaluations, inspect their configuration, run them against specific generations, query individual results, and set up scheduled reports on an evaluation. Use when the user asks to debug why an evaluation is failing, surface common failure modes, compare results across filters, dry-run a Hog evaluator, prototype a new LLM-judge prompt, inspect sentiment classifications, or manage the evaluation lifecycle.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogexploring-llm-traces
Debug and inspect LLM/AI agent traces using PostHog's MCP tools. Use when the user pastes a trace or session URL (e.g. /ai-observability/traces/ or /ai-observability/sessions/ ), asks to debug a trace, figure out what went wrong, check if an agent used a tool correctly, verify context/files were surfaced, inspect subagent behavior, investigate LLM decisions, or analyze token usage and costs. Also use when raw SQL/HogQL against events.properties.$aiinput / $aioutputchoices returns empty — message content lives only on the dedicated posthog.aievents table.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogexploring-mcp-intent-clusters
Explore PostHog MCP intent clusters — agent goals grouped by semantic similarity, with each cluster's tool distribution and error rates, plus the tool-centric pivot (capture rate per intent, discovery rate against the advertised catalog, description fit, tool overlaps). Use when the user asks "what are agents trying to do with the MCP?", "group the intents", "which goals fail most?", "what does each cluster route to?", "when agents have this intent do they find my tool?", "which tools get mixed up?", wants to recompute the clustering, or pastes an MCP analytics intent-clustering URL.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogexploring-mcp-tool-quality
Investigate the quality of PostHog MCP tool calls — error rates, latency, reach, and which tools are failing or slow. Use when the user asks "which MCP tool has the highest error rate?", "what's the slowest tool?", "which tools fail most often?", "how reliable is tool X?", wants a tool-quality matrix, or pastes an MCP analytics tool-quality / dashboard URL and asks what it shows.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogexploring-mcp-tool-usage
Starting point for exploring how a PostHog MCP server's tools are used — routes a broad question to the typed tool that answers it. Use when the user asks "how is my MCP doing?", "what should I look at?", "explore my tool calls", "who uses my MCP tools?", "what are agents doing with the MCP?", or pastes an MCP analytics URL without a specific question. Offers a menu of questions, each backed by a query tool, then hands off to the focused skill.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogexploring-replay-vision-observations
Guides agents through pulling a Replay Vision scanner's observations, reading the findings, and acting on them — summarizing patterns across sessions, drilling into individual recordings, and turning real, corroborated issues into PostHog tasks, insights, or an investigating-replay hand-off.\nTRIGGER when: user wants to pull/read/triage Replay Vision observations, asks \"what has my scanner found\", wants to act on or summarize scanner findings, turn observations into tasks/work, or points at a /replay-vision/ URL.\nDO NOT TRIGGER when: creating or sizing a scanner (use creating-replay-vision-scanners), running a one-off scan you don't then analyse, or authoring a signals scout.
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogexploring-scouts
How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to understand what scouts they have, how each one is behaving, and whether the fleet is actually working. Covers surveying the fleet and its schedules, reading recent scout runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory the fleet has built up, tracing a run to the reports it wrote or edited, and assessing a scout's health and performance over time (cadence, success rate, report rate, signal-to-noise). Read-only and exploratory — to write or tune a scout, use authoring-scouts instead. Trigger on "what are my scouts doing", "how is my scout performing", "show me recent scout runs", "why did this scout find/report nothing", "what has the fleet learned", "explore scout run ", "is my scout working".
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일
posthogfeature-usage-feed
Set up an LLM-judge evaluation that extracts canonical use cases for a PostHog feature at scale and streams the results to a Slack channel as a live feed. Use when someone wants to understand how users are actually using a specific AI/LLM-powered feature in production — what they're investigating, what questions they're trying to answer, and what patterns surface — without manually reading hundreds of traces. Assumes the feature emits $aigeneration and $aievaluation events with $sessionid linkage to the trigger user's recording (the standard setup post the session-summary linkage PRs).
- 설치 수
- 1
- GitHub Stars
- 80
- 업데이트
- 9월 4일