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 happened. Use when someone asks where users are struggling, what is broken on a page or flow, for top pain points or a friction audit, why users give up at a step, whether a rage click is real, whether pages feel slow, whether people keep retrying, re-typing or going back and forth, whether a mobile app keeps crashing, or whether a problem from support tickets is widespread or affects only a few people.
Install
With your agent
Install OMGSkills skill "fullstorydev/fullstory-skills:skills/friction-analysis" 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/friction-analysis ~/.claude/skills/friction-analysisFrom README
Friction Analysis Goal Find where users struggle and report problems the team can act on. Every finding needs: A confirmation. Frustration signals find leads; a Step 3 check confirms one before it becomes a finding. An explanation of what happened, from replay. A size: how many users were affected, out of how many. Related Skills general-analysis: metrics, segments, and count or trend questions with nothing suspected broken. comparisons: structuring an A vs B comparison; decides which signals are worth comparing. session-review: full diagnosis of a single session. idea-generation: what to build next, not what is broken. For a Fullstory Opportunities list, call fullstory:getopportunities and stop. Step 1: Match the Depth to the Question | If the question is like | Do this | |---|---| | "Is this rage click real?" | Run the Step 3 checks on that one element, then give a short, direct answer.
More from this repo
comparisons
How to structure A vs B comparisons in Fullstory — when to use dimensionality (event/session properties) vs separate...
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...