Context Layer Health Check

作者 PostHog469d1773e9cb無授權條款收錄於 2026年10月8日更新於 2026年10月8日

Semantic review of context wiki quality after deterministic consolidation

僅含說明AI & Agents

AI 產生的概覽

審查情境 wiki 中互相矛盾的論述、過時優先順序、重複與缺口，並記錄發現與待辦工作。

功能: 在確定性整併之後，對情境 wiki 進行語意品質審查，並以合併歷史中最近的 wiki-miss 行作為優先順序訊號。它會尋找互相矛盾的現行論述、缺乏支持的結論、重複的低價值活動、報告無法偵測的過時優先順序、近似重複的主題、沒有歸屬頁面的概念，以及值得回填的來源。它會修正證據支持的問題，將未解決的衝突保留為 Disagreement 標記，並把待辦工作記錄在執行摘要中。最後執行 lint 指令碼及其報告模式。
適用情境: 適用於 wiki 整併之後，需要檢查語意品質而非結構的時候。適合找出矛盾、缺乏依據的論述、重複與涵蓋缺口，並記錄無法解決的事項。
執行需求: 僅為說明文件，不附指令碼。需要帶有合併歷史的情境 wiki 儲存庫，其中包含 wiki-miss 行，並需要位於 scripts/lint、支援 --report 參數的 lint 工具。不得編輯 AGENTS.md、CLAUDE.md、產生的索引、scripts/ 或 Space 路徑。

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.

來源與署名

來源：PostHog/ai-plugin位於skills/context-layer-health-check提交469d177

授權條款：無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 PostHog/ai-plugin 的技能

Writing Simplified Technical English

PostHog

套用 ASD-STE100 簡化技術英語規則，讓代理撰寫的文字語意明確、方便執行。

Writing & Content2026年10月8日

Working With Task Comments

PostHog

透過 PostHog MCP exec 調度器讀取並解讀 PostHog 任務、成品和畫布上的留言。

Productivity & Workflow2026年10月8日

Working With Skills

PostHog

指導代理使用 PostHog 的 skill-* MCP 工具來探索、讀取、建立、更新與重構技能。

AI & Agents2026年10月8日

Working With Scouts

PostHog

說明如何把監看工作委派給 PostHog Signals 偵察代理、處理其回報，並長期調校整個代理團隊的操作手冊。

AI & Agents2026年10月8日

Validating And Publishing Canvases

PostHog

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 expected_current_version_id, staging a draft build and promoting it, waiting out the queued build, and recovering from a 409 version_conflict 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.

待分類2026年10月8日

Understanding Billing Usage

PostHog

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.

待分類2026年10月8日

Context Layer Health Check

Context layer health check

來源與署名

更多來自 PostHog/ai-plugin 的技能

Writing Simplified Technical English

Working With Task Comments

Working With Skills

Working With Scouts

Validating And Publishing Canvases

Understanding Billing Usage

更多AI & Agents技能

Skill Development

Plugin Structure

Command Development

Claude Md Improver

Google Cloud Solution Agentic Ai Data Science Workflow

Google Cloud Solution Agentic Ai Borderless Data Lakehouse