Context Layer Consolidation

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

Keep the context wiki coherent using the deterministic lint report queue

Instructions onlyProductivity & Workflow
AI-generated overview

Maintains a context wiki by working a lint report queue to fix links, duplicates, and unsupported content.

What it does
This skill guides an agent through consolidating a Markdown context wiki on a working branch. It starts from a deterministic lint report, then edits sourced pages under org/, areas/, decisions/, and existing Space pages to remove unsupported synthesis, mark expired priorities and superseded decisions, merge near-duplicates, and repair or retain ghost links. It finishes by re-running the lint check and naming every deletion in the commit message.
When to use it
Use it when a context wiki has accumulated drift and a lint report queue needs to be worked down. It fits periodic maintenance runs where edits must stay evidence-led and bounded to sourced content.
Requirements
Requires a context wiki repository with the described directory structure and a lint script invoked as scripts/lint; the skill itself ships no scripts and is instructions only. It assumes a working branch and commit access.

Context layer consolidation

Start with scripts/lint --report. Work the queue on the current dream branch.

Only edit sourced Markdown content under org/, areas/, decisions/, and existing Space pages. Never edit repository instructions, generated indexes, or scripts/; report structural failures in the run summary for the server to repair.

  • Remove unsupported synthesis.
  • Remove expired priorities unless historically significant; mark those status: historical.
  • Mark replaced decisions superseded and link their replacement.
  • Merge near-duplicates and leave a wikilink from the old subject.
  • Resolve disagreements only with evidence; leave the rest explicit.
  • Repair or intentionally retain ghost links, add sources, and split oversized pages.
  • Name every deletion in the commit message.

Keep this bounded and evidence-led. Run scripts/lint after editing.

Source and attribution

Source:PostHog/ai-plugininskills/context-layer-consolidationat 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 Productivity & Workflow

Github Issue Creator

microsoft

Featured

Turns raw notes, error logs, dictation, or screenshots into structured GitHub-flavored markdown issue reports.

Productivity & WorkflowOct 8, 2026

Notion Spec To Implementation

openai

Featured

Turns Notion specs into implementation plans, linked tasks, and progress updates inside Notion.

Productivity & WorkflowOct 8, 2026

Notion Research Documentation

openai

Featured

Researches Notion pages and synthesizes findings into cited briefs, comparisons, or reports published back to Notion.

Productivity & WorkflowOct 8, 2026

Notion Meeting Intelligence

openai

Featured

Prepares meeting agendas and pre-reads using Notion context and research, tailored to attendees and meeting type.

Productivity & WorkflowOct 8, 2026

Linear

openai

Featured

Guides an agent through managing Linear issues, projects, cycles and team workflows via the Linear MCP server.

Productivity & WorkflowOct 8, 2026

Define Goal

openai

Featured

Turns a vague intention into a concrete, measurable goal with verification evidence and scope bounds.

Productivity & WorkflowOct 8, 2026