/
Pendo
Bring Pendo analytics into Cursor with skills for account health, feature adoption, session replays, and feedback analysis
Skills4
account-healthPrepare for a customer call by synthesizing engagement, sentiment, and feedback from Pendo analytics. Use this skill whenever someone asks about account health, wants to prepare for a customer call, needs an account health report, asks about engagement or usage for a specific customer, or wants a summary of how an account is doing. Also trigger when users mention preparing for a QBR, checking on a customer, or reviewing an account before a meeting — even if they don't say "account health" explicitly.
feature-adoptionAnalyze feature adoption rates, identify power users vs laggards, and track adoption trends using Pendo analytics. Use this skill whenever someone asks about feature adoption, feature usage, who's using a feature, adoption rates, feature rollout progress, or wants to understand how a specific feature is performing. Also trigger when users mention tracking a feature launch, finding champions or power users of a feature, identifying accounts that haven't adopted a feature, comparing adoption across segments, or analyzing usage trends over time — even if they don't say "adoption" explicitly. If someone asks "who's using X" or "how is feature Y doing", this is the right skill.
feedback-analysisAnalyze customer feedback using Pendo's feedback tools — cluster themes, extract insights, and surface churn/frustration risks. Use whenever the user asks about feedback trends, top complaints, feature requests, Voice of the Customer, churn risks, or what customers are saying about a topic or account. Triggers on phrases like "feedback report", "what are customers asking for", "any red flags in sentiment", or "what's the feedback looking like". Requires Pendo connector.
session-replayFind and surface relevant session replays for debugging, UX research, and understanding user behavior. Use this skill whenever someone asks about session replays, wants to watch how users interact with their product, needs to debug a user issue by seeing what happened, or wants to find sessions with frustration signals like rage clicks or errors. Also trigger when users mention watching recordings, finding replays for a specific visitor or page, investigating UX problems, or looking for sessions with high activity — even if they don't say "session replay" explicitly.