fullstory-analysislisted
Install: claude install-skill teamzz111/fullstory-analysis-skill
# Fullstory Analysis
Fullstory captures what users do. It does not tell you why. This skill is the bridge:
a repeatable way to go from "conversion dropped" to "here is the broken thing, here
is the evidence, here is what it costs us."
## The core discipline
Most Fullstory work fails the same way: someone watches ten interesting sessions,
finds a story they like, and presents it as a finding. Ten sessions out of two
million is an anecdote wearing a lab coat.
The rule for this skill: **quantitative first, replay second, always.**
Narrow with metrics until the population is small and well-defined. Only then watch
replays — and watch them to find the *mechanism*, not to find the problem. The
funnel tells you where users die. The replay tells you what killed them.
## Workflow
### 1. Turn the question into a measurable one
The request will usually be vague ("checkout feels broken", "users hate the new
onboarding"). Convert it before touching the tool:
- **What flow?** Named steps, in order, with the URLs or screens that define each.
- **What population?** New vs returning, plan tier, device, browser, geography.
- **What window?** And what's the comparison window — before a release, same weekday last month?
- **What's the loss?** Sessions, users, or dollars. If nobody can say, the finding won't get prioritized later.
If the answer to any of these is unknown, ask. Guessing the flow definition wastes
the entire investigation.
### 2. Build the funnel
Define each step by the