fullstory

Plugin fullstory from marketplace fullstory in fullstorydev/fullstory-skills. Commands read from the repo's manifest — 12 days ago.

Skills (5)

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

• friction-analysis

  Finds where users struggle on a page or flow and whether a suspected problem is real. Ranks Fullstory's frustration and error signals, separates real problems from buttons people are meant to click many times, measures how many users each problem affects, and uses session replays to show what happen

• general-analysis

  Fullstory analytics workflow — the default way to answer any question about user behavior. Use whenever someone asks how many, what percentage, which pages, whether something is trending, where users drop off, what users did before or after an action, or how two cohorts compare — and also when they

• idea-generation

  Finds product improvement ideas a team has not already considered. Searches the metrics, segments and funnels the team already built, builds the ones that are missing, measures how many users each idea affects against a baseline, and pulls session replays as evidence. Returns 3 to 5 ranked proposals

• session-review

  Use when diagnosing user-reported issues, investigating bugs, analyzing user behavior, or validating UI correctness using Fullstory session recordings.

Subagents (1)

• 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:get_session_events directly in the main context. Pass the session_id (or session URL) from the session lis

MCP servers (1)

• fullstory

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

Similar plugins