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
公式

composing-grid-canvases

Compose PostHog grid canvases — widget grids (including the user's home canvas) built from reusable component canvases. Use when a task asks to add, fill, move, resize, or remove a widget on a grid or home canvas, to compose a whole canvas of widgets from one ask, to build a reusable widget/component, or when a placement id or grid canvas id is the target. Covers the component store search → configure → fork → build ladder, the component placement contract (size, configSchema), the placement lif

1時間の導入数
1
GitHub Stars
96
更新日
10月31日
posthog
公式

consuming-endpoints-from-client-code

Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api/openapi-ts, sending the right auth header, shaping the variables payload (HogQL codename vs insight breakdown property), handling rate-limit and materialised-endpoint error responses. Use when the user says "how do I call my endpoint", "generate a client for this", or "what auth header do I use".

1時間の導入数
1
GitHub Stars
96
更新日
10月31日
posthog
公式

designing-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時間の導入数
1
GitHub Stars
96
更新日
10月31日
posthog
公式

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

1時間の導入数
1
GitHub Stars
96
更新日
10月31日