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日