AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

posthog-onboarding

Help existing PostHog customers improve their PostHog instance. Triggers on "help [customer] improve their PostHog setup", "audit [company]'s PostHog instance", "create tracking plan for [company]", "design data schema for [customer]", or requests to improve analytics coverage, fix instrumentation gaps, expand PostHog usage, or build better insights for customers already using PostHog. Use when working with a customer who already has PostHog installed.

Original source
posthog
License
MIT
Pinned revision
cac7c80a9e5b73484d18eda1bffb47297c938e0c

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read posthog--posthog-onboarding at revision cac7c80a9e5b73484d18eda1bffb47297c938e0c, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 7

references/writing-style.md

PostHog Writing Style Guidelines

Core Principles

1. Assume Almost Nothing

Make it easy for readers to implement features or solve issues, whether expert or beginner.

2. Get to the Point

  • Don't wait three paragraphs to explain something
  • Start with the explanation and expand later
  • Almost all content can be improved by shortening the intro
  • Don't be boring

3. Make It Easy to Read

  • Use clear structure
  • Most readers scan before committing to read
  • Use headings, but don't over-format

4. Avoid Hedging

Be opinionated. Avoid:

  • "It's complicated"
  • "It depends"

Instead:

  1. Have an opinion
  2. Provide an example
  3. Do research until you can do 1 or 2

Formatting Guidelines

Minimal Formatting

Avoid over-formatting with:

  • Bold emphasis (use sparingly)
  • Headers (use appropriately, not excessively)
  • Lists (see below)
  • Bullet points (see below)

When to Use Lists/Bullets

DON'T use for:

  • Casual conversation or simple questions
  • Reports or explanations (use prose instead)
  • When not explicitly requested

DO use for:

  • When user explicitly asks for it
  • When response is multifaceted and lists are essential for clarity
  • Each bullet should be 1-2 sentences minimum

In prose: Write lists naturally like "some things include: x, y, and z" with no bullets.

Tone

  • Natural and conversational
  • Don't overwhelm with questions (max one per response)
  • Address queries even if ambiguous before asking for clarification
  • No emojis (unless user uses them first, then sparingly)
  • Never curse unless user does (and even then, sparingly)
  • No emotes in asterisks unless user requests it
  • Treat users with kindness, avoid negative assumptions

Style Rules

Language

  • American English (standard)
  • Sentence case for titles: "Documentation style guide" not "Documentation Style Guide"

Capitalization

  • Product names: Capitalize as proper nouns ("Session Replay", "Feature Flags")
  • General terms: Lowercase when not referencing product ("session replay" as industry term)
  • Acronyms: Capitalize ("URLs" not "urls")

Punctuation

  • Oxford comma: "bananas, apples, and oranges"
  • Straight quotes: Not curly quotes or apostrophes
  • British-style en dashes: Use " – " (with spaces) not "—" (no spaces)

Numbers

  • Abbreviate thousands to billions: 10M, 100B (capital letter, no space)
  • Full numbers: use commas (15,000,000)

Links

  • Never use "here" or "click here"
  • All links should have relevant anchor text describing destination

Email-Specific Style

Be Helpful, Not Sales-y

  • Focus on solving their problem
  • Provide specific, actionable guidance
  • Don't pad with fluff

Structure

  1. Brief, friendly greeting
  2. Acknowledge their request
  3. Provide specific help/resources
  4. Clear next steps (if any)
  5. Simple sign-off

Avoid

  • Corporate jargon
  • Overly formal language
  • Excessive pleasantries
  • Long intros before getting to the point