PC

posthog/context-mill

Developer tools

이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기

68 stars 품질 51 트렌드 34

PostHog context and skill assembly for AI agents and LLM tasks

개요

This repo assembles PostHog context for AI agents and LLMs into Agent Skills-compliant packages. Check out /context for details. No problem. Let us know in #team-docs-and-wizard, or fire up a PR to augment the /context and /scripts directories with your preferred transformation. The context mill gathers up-to-date content from multiple sources, packaging PostHog developer docs, prompts, and working example code into a versioned manifest which can be shipped anywhere as a zip file. The PostHog MCP server currently fetches the examples repo manifest and exposes it to any MCP-compatible client as resources and slash commands. This is what currently powers the PostHog wizard. The examples repo effectively acts as a context engine, an assembly line for turning disparate PostHog knowledge into something portable, something AI systems can reliably consume. You can break its context engineering flow into three main stages.

README

원문 README의 일부입니다. 원문 보기.

Welcome to the PostHog context mill

This repo assembles PostHog context for AI agents and LLMs into Agent Skills-compliant packages. Check out /context for details.

Need output in a different format? No problem. Let us know in #team-wizard-and-docs, or fire up a PR to augment the /context and /scripts directories with your preferred transformation.

Have a skill you want to make sure is maintained and distributed via the wizard?

We’d love your pull request!

The context mill gathers up-to-date content from multiple sources, packaging PostHog developer docs, prompts, and working example code into versioned skills which can be shipped anywhere as zip files.

The PostHog wizard downloads skills and menus from the latest release. The PostHog MCP server fetches the skills-mcp-resources.zip bundle and exposes it to any MCP-compatible client as resources. The AI plugin packages skills from here too.

The context mill is a stopgap. The goal is to retire it once the docs themselves package cleanly into skills. See the handbook.

Context engine

The context mill effectively acts as a context engine, an assembly line for turning disparate PostHog knowledge into something portable, something AI systems can reliably consume.

You can break its context engineering flow into three main stages.

1. Context sourcing: The context mill pulls from the entire PostHog developer docs, with pages delivered from posthog.com as raw Markdown. It also includes curated, hand-crafted prompts and working example apps.

2. Context assembly: The context mill transforms and packages the sourced context into zip files and menus, which is meant to be portable and self-contained. We can structure and shape them however we need.

3. Context delivery: The context mill creates a versioned GitHub release, mirrored to context-mill.posthog.com, which any agent or MCP server can consume as skills or resources.

Example apps

We’ve got live, working example code that demonstrates PostHog in action. You can run these yourself to see events flow into your PostHog project.

Example apps are not production-grade

These are more like model airplanes. They’re dramatically simplified to make it easy to see PostHog in action. You shouldn’t use these as starter projects or put them into production. The authentication is fake!

But the leanness makes these useful for agent-driven development. Use these as context to help your agent make better integration decisions about PostHog.

example-apps/
GitHub에서 전체 README 보기

추천 도구

다른 키워드를 입력하거나 필터를 제거해 보세요.

설치

npx skillfish add posthog/context-mill
MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →