Loading...
Loading...
Found 16 Skills
Create and configure surveys in PostHog through guided conversation. Use this skill when a user wants to create a survey, collect user feedback, run NPS/CSAT/CES/PMF surveys, gather product feedback, or understand user sentiment. The skill guides Product Managers through survey design by matching their goals to proven templates (or creating custom surveys), then configuring targeting and scheduling before creating via PostHog MCP tools.
Design system feedback for user actions including confirmations, status updates, and notifications.
Capture user corrections and feedback after any skill runs, persist them as learned instructions, and silently apply them on future invocations. TRIGGER when: user gives feedback or corrections after a skill runs — e.g. "next time only show top 5", "always use bullet points", "don't include X", "from now on...", "remember to...". Also: "What have you learned about {skill}?", "Show skill tuning", "Clear skill tuning for {skill}"
Analyze user feedback data to identify segments with sentiment scores, JTBD, and product satisfaction insights. Use when analyzing user feedback at scale, running sentiment analysis on reviews or surveys, or identifying satisfaction patterns.
Help users de-risk new product bets by testing core assumptions, building low-fidelity prototypes, and gathering high-signal evidence before investing heavy engineering resources.
Toast notifications, alerts, feedback messages, and their timing. Use when adding user feedback, success messages, or alerts.
Focused Signals scout for PostHog projects running surveys. Watches active surveys for score regressions (NPS / CSAT / rating drops), response-volume drops, abandonment spikes, and targeting drift, AND aggregates open-text responses into recurring themes the team should know about (clusters of complaints, praise, feature requests). Emits findings only when a theme or anomaly clears the confidence bar; otherwise writes durable memory and closes out empty. Self-contained peer in the signals-scout-* fleet — no dependencies on other skills.
Pendo platform help — product analytics, in-app guides, session replay, NPS/CSAT surveys, feature adoption tracking, Leo AI. Use when Pendo guides aren't showing, feature tagging is tedious, analytics data looks wrong, users aren't completing onboarding, NPS scores are flat, need help with Pendo API or aggregation queries, setting up Pendo for the first time, or comparing Pendo to Appcues or WalkMe. Do NOT use for in-app messaging strategy across platforms (use /sales-in-app-messaging) or general customer feedback strategy (use /sales-customer-feedback).
When something goes wrong, the user must be able to recover or try again. Toasts, inline errors, banners, and notification patterns each have a specific role. Use when designing error states, success confirmations, async feedback, in-place editing, or any system that communicates state changes to the user.
Report user activity and submit feedback to Glean. Use when logging user interactions or providing relevance feedback on search results.
Design and implement microinteractions, motion design, transitions, and user feedback patterns. Use when adding polish to UI interactions, implementing loading states, creating gesture-based interactions, designing hover/focus states, building notification/toast systems, adding scroll-triggered animations, implementing drag-and-drop, or creating delightful user experiences.
Asks for user feedback after each task or cron job completion and runs a recursive learning flow. If output is good, asks what was good until 10 approvals; if needs improvement, asks why/how/what via multiple choice plus optional examples, uses web search and iterative thinking to resolve, and caps iterations by severity (slight 5, medium 10, severe 20). Keeps feedback non-intrusive. Use when completing discrete tasks or cron jobs for the user.