AGENTIC MEMORY

Skills

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

← Back to Skills

creating-surveys

Creates and launches PostHog surveys through MCP, including NPS/CSAT popovers, hosted feedback forms, and headless surveys. Guides survey type selection, audience targeting, draft review, and launch readiness. Use when asked to create a survey or form, or before calling survey-create. For investigating an existing survey's delivery or responses, use debugging-surveys instead.

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--creating-surveys 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 · 3

references/examples.md

Minimal survey drafts

These inputs use posthog:survey-create and omit start_date so they stay drafts. Adapt the questions to the request. Verify any event names and audience rules against the project before adding them.

In-app NPS

{
  "name": "Product recommendation feedback",
  "type": "popover",
  "enable_partial_responses": true,
  "questions": [
    {
      "type": "rating",
      "question": "How likely are you to recommend this product?",
      "display": "number",
      "scale": 10
    },
    {
      "type": "open",
      "question": "What is the main reason for your score?",
      "optional": true
    }
  ]
}

This has no audience restriction. Add the user's intended display conditions and targeting before launch.

In-app CSAT after an action

{
  "name": "Export satisfaction",
  "type": "popover",
  "enable_partial_responses": true,
  "questions": [
    {
      "type": "rating",
      "question": "How satisfied are you with this export?",
      "display": "emoji",
      "scale": 5
    },
    {
      "type": "open",
      "question": "What would make it better?",
      "optional": true
    }
  ],
  "conditions": {
    "events": { "values": [{ "name": "export_completed" }] }
  }
}

Replace export_completed with an event the project already captures at that moment. The survey shows only after the event fires, which is when the person can answer.

Hosted feedback form

{
  "name": "Product feedback form",
  "type": "external_survey",
  "questions": [
    {
      "type": "open",
      "question": "What could make this product easier to use?"
    }
  ]
}

Hosted forms do not need a URL display condition, cohort, or linked feature flag. Only enable iframe embedding when requested.

Headless feedback form

{
  "name": "In-app feedback definition",
  "type": "api",
  "questions": [
    {
      "type": "open",
      "question": "What would you like us to improve?"
    }
  ]
}

The application must render this form and capture the survey's events. Use the returned survey and question IDs in that implementation; do not invent them.