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.
Install
With your agent
Install OMGSkills skill "fullstorydev/fullstory-skills:skills/comparisons" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/fullstorydev/fullstory-skills /tmp/fullstory-skills && ln -s /tmp/fullstory-skills/skills/comparisons ~/.claude/skills/comparisonsFrom README
Comparisons When the user asks to compare A vs B, the right mechanism depends on what the comparison axis is. Use the decision table below to classify it — the user doesn't need to know this distinction exists. Event/session properties → dimensionality If the comparison axis describes the context of an individual event at the moment it fired — not the user who triggered it — use dimensionality. Common examples: device type, browser, OS, page URL, element. But the rule is the principle, not the list: if the property travels with the event, not the user, it belongs here. Express it as a single topn metric with the comparison axis as the grouping dimension. Example: "rage clicks on mobile vs desktop" → fullstory:buildmetric(query="rage clicks by device type", outputtype="topn"). The result table shows mobile and desktop as separate rows.
More from this repo
friction-analysis
Finds where users struggle on a page or flow and whether a suspected problem is real.
general-analysis
Fullstory analytics workflow — the default way to answer any question about user behavior.
session-review
Used when diagnosing user-reported issues, investigating bugs, analyzing user behavior, or validating UI correctness...