pleasefixai/pendo-analytics

Prepare 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.

Generate a shareable health report for one application, summarizing engagement, acquisition, retention, average time, stickiness, frustration signals, and survey scores into a verdict and next steps. Use this skill whenever someone asks how healthy an app is, wants an app health report, wants an overall picture of how an application is doing, or asks about an app's engagement, retention, stickiness, or friction at the application level — even if they don't say "app health" explicitly. This is app-level (a whole application), not account-level — for a single customer account use account-health, and for a single feature use feature-adoption.

Use when planning a product feature, fix, or prioritization task where Pendo usage data, signals, issues, or customer feedback could ground the plan in real product behavior — e.g. "plan a fix for the pricing-page dropoff", "what should I build next", "improve the welcome flow". Skip for pure code refactors, infra, or tooling work.

Analyze 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.

Analyze 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.

Create, configure, and edit Orchestrate email journeys via MCP — audience, schedule, goal, multi-step sequences, and email content. Use for welcome or onboarding sequences, re-engagement or win-back, create or update a journey, or prepare to go live. For opens, clicks, or journey metrics, use Orchestrate metrics MCP tools directly — not this skill's reference workflow.

Creates production-ready Pendo in-app guides as HTML/CSS/JS files, drawing on guide type best practices, org-specific content guidelines, and user-provided context. Trigger this skill whenever a user invokes pendo-analytics:pendo-guide-creator or uses natural language like "create a guide", "build a Pendo guide", "write a walkthrough", "make an announcement guide", "create an alert", "build a poll", or "write an in-app message". Also trigger when the user describes a guide use case — e.g. "I want to onboard new users", "we're launching a feature and want to notify users in-app", or "I need to collect feedback in the product." Always use this skill proactively when any Pendo guide creation is requested, even if the request is casual or incomplete — the skill handles gathering missing context from the user.

Triage issues captured in a Pendo session replay by fetching devlogs, mapping errors to the local codebase, proposing fixes, and prompting for a pull request. Accepts either a replay URL directly or a ticket reference (e.g. Jira key or URL, GitHub issue URL, etc.) and will pull the replay link from the ticket. Use whenever someone hands off a user-reported bug — via a replay link or a ticket that contains one — and asks to investigate, diagnose, debug, triage, or fix it. Requires Pendo connector; uses whatever ticketing MCP or CLI is available (Atlassian, gh, etc.) when a ticket is supplied.

Find 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.