How do I install the Integration Astro Hybrid skill?

Run npx skillmds add posthog-skills/integration-astro-hybrid in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Integration Astro Hybrid safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Integration Astro Hybrid?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Integration Astro Hybrid free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Integration Astro Hybrid?

posthog (@posthog-skills) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Integration Astro Hybrid by posthog-skills

Name: Integration Astro Hybrid
Rating: 4.5 (4 reviews)
Author: posthog

File contents

PostHog integration for Astro (Hybrid)

This skill helps you add PostHog analytics to Astro (Hybrid) applications.

Workflow

Follow these steps in order to complete the integration:

basic-integration-1.0-begin.md - PostHog Setup - Begin ← Start here
basic-integration-1.1-edit.md - PostHog Setup - Edit
basic-integration-1.2-revise.md - PostHog Setup - Revise
basic-integration-1.3-conclude.md - PostHog Setup - Conclusion

Reference files

references/EXAMPLE.md - Astro (Hybrid) example project code
references/astro.md - Astro - docs
references/identify-users.md - Identify users - docs
references/basic-integration-1.0-begin.md - PostHog setup - begin
references/basic-integration-1.1-edit.md - PostHog setup - edit
references/basic-integration-1.2-revise.md - PostHog setup - revise
references/basic-integration-1.3-conclude.md - PostHog setup - conclusion

The example project shows the target implementation pattern. Consult the documentation for API details.

Key principles

Environment variables: Always use environment variables for PostHog keys. Never hardcode them.
Minimal changes: Add PostHog code alongside existing integrations. Don't replace or restructure existing code.
Match the example: Your implementation should follow the example project's patterns as closely as possible.

Framework guidelines

Always use the is:inline directive on PostHog script tags to prevent Astro from processing them and causing TypeScript errors
Use PUBLIC_ prefix for client-side environment variables in Astro (e.g., PUBLIC_POSTHOG_PROJECT_TOKEN)
Create a posthog.astro component in src/components/ for reusable initialization across pages
Import the PostHog component in a Layout and wrap all pages with that layout
Use posthog-node in API routes under src/pages/api/ for server-side event tracking
Store the posthog-node client instance in a singleton pattern (src/lib/posthog-server.ts) to avoid creating multiple clients
In Astro 5, use output static (the default) with an adapter - pages are prerendered by default
Use export const prerender = false to opt specific pages into SSR when they need server-side rendering
Only pages that need server-side PostHog tracking (like API-backed forms) should opt out of prerendering

Identifying users

Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. If both frontend and backend code exist, pass the client-side session and distinct ID using X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers to maintain correlation.

Error tracking

Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries.

---name: integration-astro-hybriddescription: PostHog integration for Astro hybrid rendering with both static and server-rendered pages--- # PostHog integration for Astro (Hybrid) This skill helps you add PostHog analytics to Astro (Hybrid) applications. ## Workflow Follow these steps in order to complete the integration: 1. `basic-integration-1.0-begin.md` - PostHog Setup - Begin ← **Start here** 2. `basic-integration-1.1-edit.md` - PostHog Setup - Edit 3. `basic-integration-1.2-revise.md` - PostHog Setup - Revise 4. `basic-integration-1.3-conclude.md` - PostHog Setup - Conclusion ## Reference files - `references/EXAMPLE.md` - Astro (Hybrid) example project code - `references/astro.md` - Astro - docs - `references/identify-users.md` - Identify users - docs - `references/basic-integration-1.0-begin.md` - PostHog setup - begin - `references/basic-integration-1.1-edit.md` - PostHog setup - edit - `references/basic-integration-1.2-revise.md` - PostHog setup - revise - `references/basic-integration-1.3-conclude.md` - PostHog setup - conclusion The example project shows the target implementation pattern. Consult the documentation for API details. ## Key principles - **Environment variables**: Always use environment variables for PostHog keys. Never hardcode them. - **Minimal changes**: Add PostHog code alongside existing integrations. Don't replace or restructure existing code. - **Match the example**: Your implementation should follow the example project's patterns as closely as possible. ## Framework guidelines - Always use the is:inline directive on PostHog script tags to prevent Astro from processing them and causing TypeScript errors - Use PUBLIC_ prefix for client-side environment variables in Astro (e.g., PUBLIC_POSTHOG_PROJECT_TOKEN) - Create a posthog.astro component in src/components/ for reusable initialization across pages - Import the PostHog component in a Layout and wrap all pages with that layout - Use posthog-node in API routes under src/pages/api/ for server-side event tracking - Store the posthog-node client instance in a singleton pattern (src/lib/posthog-server.ts) to avoid creating multiple clients - In Astro 5, use output static (the default) with an adapter - pages are prerendered by default - Use export const prerender = false to opt specific pages into SSR when they need server-side rendering - Only pages that need server-side PostHog tracking (like API-backed forms) should opt out of prerendering ## Identifying users Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. If both frontend and backend code exist, pass the client-side session and distinct ID using `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` headers to maintain correlation. ## Error tracking Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries.

Frequently asked questions