fullstory-reatlat

Plugin fullstory-reatlat from marketplace fullstory-marketplace in reatlat/fullstory-claude-plugin. Commands read from the repo's manifest — 12 days ago.

Skills (46)

• a11y-analyzer

  Accessibility analysis from session data — keyboard-only navigation patterns, focus order issues, screen reader compatibility, and accessibility regressions. Use when auditing a11y compliance, investigating accessibility bugs, or validating inclusive design.

• annotation-ops

  Create and manage Fullstory timeline annotations — deploy markers, experiment start/end, incident windows, and release notes. Use when the user wants to mark a deploy, experiment, incident, or any notable event on the Fullstory timeline.

• anomaly-detector

  Proactive anomaly detection — scan metrics for statistical outliers, sudden changes, and unexpected patterns. Use when the user wants to know if something unusual happened, when a metric changed unexpectedly, or for automated health monitoring.

• api-monitor

  Monitor API call patterns from session data — endpoint latency, error rates, popular endpoints, and API-driven UX issues. Use when investigating backend performance impact on UX, API errors affecting users, or endpoint usage patterns.

• benchmark-analyzer

  Establish performance baselines and benchmarks — compare current metrics to historical averages, set targets, and track progress over time. Use when setting KPIs, establishing baselines, or measuring against goals.

• campaign-tracker

  Track marketing campaign performance — UTM-tagged traffic, landing page conversion, campaign cohort behavior, and ROI signals. Use when analyzing campaign performance, measuring landing page effectiveness, or comparing marketing channels.

• changelog-detective

  Detect what changed in the product by comparing before and after a deploy or date — find new behaviors, new errors, changed user flows, and unexpected side effects that weren't in the release notes. Use after a deploy or when the user suspects something changed but doesn't know what.

• cohort-compass

  Advanced cohort management — build, compare, and track user cohorts over time. Use when working with persistent user groups (enterprise vs free, new vs returning, by country or plan) across multiple analyses.

• comparisons

  How to structure A vs B comparisons in Fullstory — when to use dimensionality (event/session properties) vs separate segments (user-level properties), and why the distinction matters for correctness.

• customer-360

  Full 360-degree view of a specific customer — sessions, purchases, errors, support interactions, engagement history. Use when support needs context on a customer, sales wants to understand a prospect's behavior, or you need to investigate an escalated issue.

• dashboard-builder

  Build and manage recurring dashboard views of key metrics — set up daily/weekly monitoring with saved metrics and segments. Use when the user wants to create a recurring dashboard, set up KPI monitoring, or establish a baseline.

• deploy-radar

  Post-deploy validation — check errors, conversion, and frustrations before and after a deploy timestamp. Use when the user deploys code and wants to know if anything broke.

• error-forensics

  Investigate JavaScript errors, console errors, network failures, and crashes in production. Use when debugging user-reported issues, tracking error frequency, finding sessions with specific errors, or determining whether a bug is widespread or isolated.

• experiment-analyzer

  A/B test and experiment analysis — measure statistical impact, segment breakdowns, and before/after comparisons. Use when the user is running an experiment, wants to know if a variant won, or needs to measure the impact of a change.

• feature-adoption

  Track feature adoption — who's using the new feature, how deeply, are they sticking with it, and what's blocking adoption. Use when launching a new feature, measuring feature engagement, or understanding feature usage patterns.

• form-analyzer

  Form field-level analysis — abandonment by field, validation errors, time-to-complete, and which fields cause users to leave. Use when investigating form performance, signup drop-off, or checkout form friction.

• frustration-hunter

  Finds and ranks user frustration signals — rage clicks, dead clicks, form abandonment, error spikes. Use when asking "what's frustrating users", "where are users struggling", or "what's the biggest UX problem right now". Uses Fullstory's opportunity detection, then drills into sessions for root caus

• funnel-doctor

  Conversion funnel analysis — find where users drop off, quantify the loss, and diagnose why. Use when asking about conversion rates, funnel abandonment, checkout completion, signup flow performance, or "where are we losing users.

• general-analysis

  Fullstory analytics workflow. Use when answering a question that requires measuring user behavior — counts, rates, trends, breakdowns, or cohort comparisons. Builds segments and metrics, computes results, then investigates sessions to explain what the numbers mean.

• heatmap-generator

  Generate click and interaction heatmaps from session data — visualize where users click, tap, and hover on any page. Use when asking "what do users click on most", "are users clicking non-clickable elements", or "where should we place the CTA".

• incident-responder

  Structured incident response workflow — detect, investigate, communicate, and resolve using session data as evidence. Use when an incident is declared, a production issue is reported, or the on-call engineer needs session evidence.

• jira-bug-reporter

  Create detailed bug reports from session evidence — auto-populate Jira tickets with session URLs, error messages, device info, and reproduction steps. Use when the user wants to file a bug from a Fullstory session.

• journey-builder

  Build, compute, and update Fullstory Journey objects from natural language — visualize common user paths, find drop-off points, and compare journey variants. Use when asking about user flows, path analysis, journey maps, or "what paths do users take.

• lifecycle-analyzer

  Analyze the user lifecycle — new, active, at-risk, and churned users. Use when understanding user progression, identifying at-risk users, or measuring lifecycle conversion rates.

• metric-auditor

  Audit existing metrics and segments for staleness, duplicates, bad configuration, and naming issues. Use when the user wants to clean up their Fullstory account, find redundant objects, or understand what already exists.

• mobile-analyzer

  Mobile-specific UX analysis — touch interactions, viewport issues, scroll behavior, mobile vs desktop patterns, and responsive design validation. Use when investigating mobile experience, responsive design bugs, or mobile conversion rates.

• nps-proxy

  Behavioral proxy for user satisfaction — use frustration signals, engagement patterns, and conversion behavior as a real-time NPS alternative. Use when the user wants to measure satisfaction but doesn't have survey data in Fullstory.

• onboarding-tutor

  Interactive onboarding guide for new Fullstory MCP users — teaches the mental model, walks through first queries, and explains how to use each skill. Use when a new team member needs to learn how to use Fullstory through Claude.

• page-performance

  Page-level performance analysis — load times, errors by page, device breakdown, and page-to-page navigation patterns. Use when asking about specific page health, comparing pages, or finding pages with performance issues.

• persona-builder

  Build behavioral user personas from session data — identify distinct user types by their actual behavior, not demographics. Use when the team needs data-driven personas, wants to understand who their users really are, or needs to align product decisions to real user behavior.

• predictive-alerts

  Proactive alerting based on trend analysis — predict when a metric will cross a threshold and alert before it happens. Use when setting up early warning systems, monitoring for regressions, or creating proactive alert rules.

• privacy-auditor

  Audit Fullstory session capture for PII leaks, verify privacy rules, and check recording block rules. Use when the user is concerned about privacy compliance, wants to verify masking rules, or needs to find sessions that may contain sensitive data.

• query-translator

  Translate vague business questions into precise Fullstory queries — help users who know what they want to ask but not how to express it. Use when the user says "I want to know X but I'm not sure how to ask Fullstory.

• quick-stats

  Lightning-fast answers to simple numeric questions — "how many users yesterday", "what's the conversion rate", "how many sessions today". Use when the question is a single number, no analysis needed. Skips the full general-analysis workflow.

• report-deck

  Turn Fullstory research findings into a presentation-ready report — slide structure, speaker notes, and export to PPTX or PDF. Use when the user asks for a deck, slides, presentation, or report from their analytics.

• retention-analyzer

  User retention analysis — N-day retention, cohort stickiness, returning vs new user patterns, and churn signals. Use when asking about retention rates, user stickiness, churn analysis, or "are users coming back?

• revenue-impact

  Attach revenue estimates to UX issues and conversion problems. Use when the user wants to know what a friction point or conversion drop is costing in dollars.

• scroll-depth-analyzer

  Analyze how far users scroll on key pages — content visibility, where users stop reading, and whether important content is being seen. Use when evaluating page layout, content effectiveness, or CTA placement.

• segment-wizard

  Interactive guided segment building for non-technical users — helps construct complex user cohorts with validation and preview. Use when a non-analyst user needs to build a segment but doesn't know how to express it in a query.

• session-playlist

  Curate playlists of Fullstory sessions for team review — bundle related sessions with notes, timestamps, and context. Use when sharing session evidence with the team, preparing for a bug review, or creating a highlight reel of user behavior.

• session-review

  Review Fullstory sessions with the GA review tools. Use for user-reported bugs, network failures, console errors, behavior analysis, and visual UI verification from a session URL or trace.

• session-search

  Search across sessions by user properties, device, browser, custom events, or page — find the needle in the haystack. Use when you need to find specific sessions without a pre-built metric or segment.

• slack-reporter

  Format Fullstory findings for Slack — structured summaries with key stats, session links, and action items ready to paste into team channels. Use when the user wants to share findings with their team in Slack.

• user-journey

  Trace a specific user's journey across sessions — what they did, where they struggled, and what happened before and after a reported issue. Use when investigating a specific user, reproducing a bug report, or understanding a high-value customer's experience.

• webhook-health

  Monitor FullStory webhook delivery — success rates, errors, latency, and webhook-driven integration health. Use when troubleshooting webhook failures, monitoring integration health, or verifying webhook configuration.

• weekly-digest

  Automated weekly summary of what changed in your product — top frustrations, new errors, trends up/down, conversion changes. Use when asking "what changed this week", "give me the weekly recap", or "what's new since last week.

Subagents (3)

• batch-session-reader

  Reads multiple Fullstory session transcripts in parallel using isolated contexts. Use when you need to investigate 3+ sessions from get_sessions results. Pass an array of {device_id, session_id, task} objects. Returns all results at once, much faster than sequential loading.

• session-context

  Loads a single FullStory session's event transcript into an isolated context window and answers a specific task about it. Always use this agent when reading session events — never call fullstory:review-summary directly in the main context. Pass device_id, session_id, and a focused task question. Ret

• session-replay

  Inspect Fullstory session screenshots and component trees in isolation with the GA review tools. Zoom into network and console errors, compare snapshots, and return focused visual evidence. Pass session_url and a task.

MCP servers (1)

• fullstory

  connects to: https://api.fullstory.com/mcp/fullstory

Similar plugins