Context Layer Health Check

by PostHog469d1773e9cbNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Semantic review of context wiki quality after deterministic consolidation

Instructions onlyAI & Agents
AI-generated overview

Reviews a context wiki for contradictory claims, stale priorities, duplicates and gaps, then records findings and remaining work.

What it does
Performs a semantic quality review of a context wiki after deterministic consolidation, using recent wiki-miss lines from merge history as the priority signal. It looks for contradictory active claims, unsupported conclusions, repeated low-value activity, stale priorities, near-duplicate subjects, concepts without an owning page, and sources worth backfilling. It fixes what the evidence supports, leaves unresolved conflicts as Disagreement markers, and records remaining work in a run summary. It finishes by running the lint script and its report mode.
When to use it
Use after a wiki consolidation pass when the wiki's semantic quality needs checking rather than its structure. Suitable for finding contradictions, unsupported claims, duplication and coverage gaps, and for logging what could not be resolved.
Requirements
Instructions only; no scripts ship with the skill. It expects a context wiki repository with merge history containing wiki-miss lines, and lint tooling at scripts/lint supporting a --report flag. It must not edit AGENTS.md, CLAUDE.md, generated indexes, scripts/, or Space paths.

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.

Source and attribution

Source:PostHog/ai-plugininskills/context-layer-health-checkat commit469d177

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from PostHog/ai-plugin

Writing Simplified Technical English

PostHog

Applies ASD-STE100 simplified technical English rules to make agent-written prose unambiguous and actionable.

Writing & ContentOct 8, 2026

Working With Task Comments

PostHog

Reads and interprets comments on PostHog tasks, artifacts, and canvases through the PostHog MCP exec dispatcher.

Productivity & WorkflowOct 8, 2026

Working With Skills

PostHog

Guides agents in using PostHog's skill-* MCP tools to discover, read, create, update, and refactor skills.

AI & AgentsOct 8, 2026

Working With Scouts

PostHog

Operating manual for delegating watching jobs to PostHog Signals scouts, acting on their reports, and steering the fleet over time.

AI & AgentsOct 8, 2026

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.

Awaiting classificationOct 8, 2026

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.

Awaiting classificationOct 8, 2026

More in AI & Agents

Skill Development

anthropics

Featured

Guides creation of Claude Code plugin skills, covering structure, descriptions, progressive disclosure and validation.

AI & Agents37Kupdated today

Plugin Structure

anthropics

Featured

Guides the structure, manifest, and component layout of Claude Code plugins.

AI & Agents37Kupdated today

Command Development

anthropics

Featured

Guides creation of Claude Code slash commands, covering structure, YAML frontmatter, arguments and plugin features.

AI & Agents37Kupdated today

Claude Md Improver

anthropics

Featured

Audits CLAUDE.md files in a repository, scores their quality, and applies approved targeted improvements.

AI & Agents37Kupdated today

Google Cloud Solution Agentic Ai Data Science Workflow

google

Featured

Guides design of a multi-product agentic data science architecture on Google Cloud, from requirements to deployment and validation.

AI & Agents21Kupdated today

Google Cloud Solution Agentic Ai Borderless Data Lakehouse

google

Featured

Guides design of a borderless multicloud open data lakehouse on Google Cloud, from requirements discovery to deployment and validation.

AI & Agents21Kupdated today