RADAR SKILLI · GITHUB
Przydatne Agent Skills, ocenione według realnego użycia.
Porównuj zweryfikowane Skills: ich zastosowanie, zawartość pakietu, liczbę instalacji i wiarygodność źródła.
- ZAKRES KATALOGU
- ZWERYFIKOWANE
- Skills
- 5771
- repozytoria
- 824
- ostatnia synchronizacja
- 8 wrz 2026
posthogresolving-ingestion-warnings
Diagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data). Use when a user asks why events are missing, dropped, or undercounted, why identify/alias calls don't work or accounts stay duplicated, why person or group properties aren't updating or profiles look inflated, why recordings have gaps, heatmaps are empty, LLM token counts are missing, why cookieless events vanish, or whenever the ingestionwarning health check fires. Explains severity triage (error = dropped, warning = modified, info = intentional) and routes all warning types — size limits and enrichment, merges and distinct IDs, $processpersonprofile, timestamps, cookieless, heatmaps, transformations, session replay — to per-issue reference files with code-level causes and per-SDK fixes.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsetting-up-a-data-warehouse-source
Guide the user through connecting a new data warehouse source — Postgres, MySQL, Stripe, Hubspot, MongoDB, Salesforce, BigQuery, Snowflake, and so on. Use when the user wants to "connect Stripe", "import data from Postgres", "add a new data source", "sync my warehouse tables", or wants to pick sync methods for each table. Walks through source-type discovery, credential validation, table discovery, per-table synctype selection, and the final create call. Also covers picking a good prefix and what to do right after creation.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsetting-up-data-catalog
Populates and maintains a project's data catalog (semantic layer): canonical metrics, trust marks (certifications) on warehouse tables/views, and reviewed table relationships. Use when asked to set up / seed / bootstrap the data catalog or semantic layer, to catalog a project's metrics, to certify or deprecate data sources, to propose or review table joins, or to work through the proposal review queue. To use an existing catalog to answer a business-number question, see querying-posthog-data instead. Trigger terms: data catalog, semantic layer, canonical metric, certify table, deprecate source, relationship proposal, metric drift, review queue.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsetting-up-support-slack-locally
Connect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back. Use when the user wants to test the conversations Slack integration locally, hits "Support Slack OAuth client ID is not configured", gets a white screen or "Network error" on the OAuth callback, or asks how to set SUPPORTSLACKAPPCLIENTID / a tunnel for supporthog Slack events. Covers the Slack app + scopes, the SUPPORTSLACK dynamic settings, and the key split: localhost for OAuth and the UI, a public tunnel only for inbound events.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals
How to query the documentembeddings table for raw signal data using HogQL. Use when you need to perform semantic search over signals, fetch every signal that contributed to a specific report, or list signal types. For browsing the curated report layer (the Inbox) — listing reports, filtering by status/source, drilling into a single report by ID — use the inbox-exploration skill first; drop into this skill afterwards if the user wants the underlying observations.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-ai-observability
Signals scout for PostHog AI observability. Watches LLM traces for cost, latency, error, volume, and eval-performance regressions.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-conversations
Signals scout for PostHog Conversations (support inbox). Watches $conversation ticket- lifecycle events for SLA breach steps, first-response latency blowouts, backlog imbalance, and channel or assignment concentration.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-customer-analytics-billing-and-usage
Signals scout for per-account product-mix shifts. Watches each staked account's usage and forecasted MRR per product for one product dropping or spiking against its own baseline while the account total holds.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-data-warehouse
Signals scout for warehouse imports. Watches external data sources, sync schemas, webhook push channels, and materialized views for failures, silent staleness, and row-volume cliffs, and suggests materialization candidates from recurring query-log hot spots.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-error-tracking
Signals scout for PostHog error tracking. Watches $exception bursts, stuck loops, multi- fingerprint clusters, and status regressions.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-experiments
Signals scout for PostHog A/B experiments. Watches running experiments for validity threats — sample ratio mismatch, contamination, exposure stalls, mid-run flag mutations — and lifecycle drift.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-health-checks
Signals scout over PostHog's own health checks. Bundles the project's active health issues by kind, weights them by blast radius, and surfaces the ones worth acting on.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-inbox-validation
Follow-up Signals scout for the inbox itself. Re-measures the problems behind recently resolved reports after a soak window and reports when a fix didn't hold, plus a gated escalation check on dismissed reports.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-insight-alerts
Signals scout over the project's configured insight alerts. Reads each alert's recent firing history and surfaces the firings a human likely missed.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-mcp-tool-calls
Signals scout for PostHog MCP tool calls. Watches $mcptoolcall telemetry for tools that need improvement — broad-reach failure rates, retry hammering, slow or context-bloating responses — grouped by owning product category, each with a fix suggestion.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-replay-vision
Signals scout for PostHog Replay Vision scanners. Watches that enabled scanners keep observing (throughput and quota cliffs) and that aggregate score shifts and recurring themes get surfaced.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-skills-store
Skill-hygiene scout for the team's PostHog skills store. Watches recently-changed and most- used skills for authoring violations — vague descriptions, bloated bodies, dead file links, kitchen-sink scope, committed secrets.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsignals-scout-tasks
Signals scout for PostHog Tasks. Watches delivery health — failing runs clustered by repository and error class, retry storms — and, on a slower rotation, recurring demand across human-authored tasks. Skips the scout fleet's own runs.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsuggesting-data-imports
Use when the user asks about revenue, payments, subscriptions, billing, CRM deals, support tickets, ad spend, production database tables, or other data PostHog does not collect natively — or wants to join or correlate PostHog product events with that external business data. Also use when a query fails because a table does not exist or returns no results for expected external data. The data warehouse can import from SaaS tools (Stripe, Hubspot, Zendesk, etc.), ad platforms, production databases (Postgres, MySQL, BigQuery, Snowflake), and other arbitrary data sources. Covers checking existing sources, identifying the right source type, and guiding the setup.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogsuppressing-noisy-errors
Create PostHog error tracking suppression rules to drop high-volume, low-value errors at ingestion. Use when the user asks "stop capturing this error", "drop browser extension errors", "ignore ResizeObserver loops", "suppress bot-driven errors", or wants to reduce ingestion cost from noisy unactionable errors. Identifies suppression candidates, scopes the filter tightly, decides between full suppression and sampling, and confirms the rule before creating it. Suppressed errors are dropped permanently — this skill defaults to caution.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogtriaging-error-issues
Triage PostHog error tracking issues during a daily or on-call review. Use when the user asks "what's broken?", "what new errors do we have?", "show me top errors today", "what should I look at this morning", or wants a prioritized list of active issues to work on. Surfaces new and high-impact issues, ranks by users affected and recency, points at linked replays, and proposes next actions (investigate, assign, suppress, merge).
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogturning-engineering-analytics-into-insights
Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL. Covers discovering per-team GitHub warehouse tables via engineering-analytics-sources, replicating curated column semantics in HogQL, reading exposed engineeringanalytics warehouse views where product logic is involved (CI cost, fingerprinted failure lines, commit attribution), saving queries with insight-create, and scheduling delivery with subscriptions-create. Use when asked to "save this as an insight", "put CI health / merge times on a dashboard", "email me PR throughput weekly", "chart CI cost", "track time to first review", "subscribe to these numbers", "alert on CI success rate", or "what data/tables/views does engineering analytics read". For ad-hoc CI and merge questions use diagnosing-ci-and-merge-bottlenecks; to investigate one specific CI failure use investigating-ci-failures.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogunderstanding-billing-usage
Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exceptions, survey responses, synced rows, logs, AI events, AI credits, or Inbox credits. Starts from Billing usage/spend tools, then routes to customer-visible product MCP surfaces for deeper investigation.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz
posthogvalidating-and-publishing-canvases
Validate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expectedcurrentversionid, staging a draft build and promoting it, waiting out the queued build, and recovering from a 409 versionconflict or a 429 capacity limit without overwriting concurrent work. Use whenever a canvas edit is ready to save, a draft build is wanted, a canvas publish or build returns diagnostics or a conflict, or a task needs to understand canvas version history.
- instalacje
- 1
- GitHub Stars
- 80
- Aktualizacja
- 4 wrz