app-health

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.

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.

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.

Run a guide-review pass over the Guide Signals Pendo has already produced — list the archive, deactivate, and anomaly signals for an app, show each with its evidence and how old it is, then let the user mute a signal or deactivate/archive the guide. Use this skill whenever someone wants to review their guides, clean up stale or declining guides, see which guides Pendo recommends archiving or deactivating, triage guide signals or anomalies, or snooze a signal — even if they don't say "signals" explicitly. Nothing is computed here; the skill reads what the weekly job produced and never changes a guide without an explicit choice.

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 types /pendo-guides: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.

Answer questions about how Orchestrate journeys and emails are doing, read-only. Use when someone asks whether a journey is set up or working as intended, why fewer people got an email than expected or who was missed, whether a journey changed what people did, what Orchestrate achieved over a period (including a QBR, renewal or exec slide), or whether people are getting too many messages. Not for creating or editing journeys (use orchestrate-journeys).

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Teach the user a new skill or concept, within this workspace.

No description in the SKILL.md.

No description in the SKILL.md.

Ask which skill or flow fits your situation. A router over the skills in this repo.

No description in the SKILL.md.

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.