posthog/ai-plugin

context-layer-health-check

Semantic review of context wiki quality after deterministic consolidation

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/posthog/ai-plugin --skill context-layer-health-check

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Context layer health check

Read recent wiki-miss: lines from git log --merges and use them as the priority signal. Review for contradictory active claims, unsupported conclusions, repeated low-value activity, stale priorities the report cannot detect, near-duplicate subjects, concepts without an owning page, and sources worth backfilling.

Fix what evidence supports. Leave unresolved conflicts as **Disagreement:** markers and record remaining work in the run summary. Finish with scripts/lint and scripts/lint --report.

Do not edit AGENTS.md, CLAUDE.md, generated indexes, scripts/, or Space paths. The server owns wiki structure and tooling.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
posthog
公式

exploring-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時間の導入数
2
GitHub Stars
98
更新日
11月6日
posthog
公式

exploring-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

1時間の導入数
2
GitHub Stars
98
更新日
11月6日
posthog
公式

instrument-integration

Add PostHog SDK integration to your application. Use when setting up PostHog for the first time or reviewing PRs that need PostHog initialization. Covers SDK installation, provider setup, and basic configuration for any framework.

1時間の導入数
2
GitHub Stars
98
更新日
11月6日
posthog
公式

investigating-error-issue

Investigates a single PostHog error tracking issue end-to-end. Use when the user provides an issue ID or pastes an issue URL (/error-tracking/ ) and wants to understand the error — who it affects, what triggers it, when it started, whether it correlates with a release, browser, OS, or feature flag, and what the next step should be. Pulls aggregated metrics, sample exception events, segment breakdowns, linked replays, and synthesizes a hypothesis-grade summary in one pass.

1時間の導入数
2
GitHub Stars
98
更新日
11月6日