# general-analysis

> Claude/Codex skill by [@fullstorydev](https://omgskills.com/library/fullstorydev/index.md) · 11 stars · Updated 2026-10-22

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 describe a business question that needs numbers behind it without ever saying "metric", "funnel", or "segment". Covers building and computing metrics, segments, funnels, and journeys, verifying that what got built is what was actually asked for, and pulling sessions to explain why the numbers look the way they do. Not for reviewing one specific session, or for setting up capture and instrumentation.

## Install

```sh
git clone https://github.com/fullstorydev/fullstory-skills /tmp/fullstory-skills && ln -s /tmp/fullstory-skills/skills/general-analysis ~/.claude/skills/general-analysis
```

## From README

Fullstory Analytics When to use Use this skill whenever answering the question takes a number out of Fullstory — a count, rate, percentage, breakdown, trend, drop-off, what users did before or after an action, or one cohort against another. That includes business questions that never name a primitive ("is checkout getting worse?", "which accounts are struggling?"). Pulling sessions is in scope when they're evidence for a number you computed. Skip when One specific session. A session URL, a named user, "what happened to this person" — that's the session-review skill. Instrumentation and capture. Defining events, custom properties, privacy rules, or installing the snippet. This skill reads data that already exists; it can't make Fullstory record something new. Account and product configuration. Users, permissions, integrations, data export . No Fullstory data in the loop. A number the user already has, or one that lives in another system. Handing off isn't an exit.

## Links

- HTML page: https://omgskills.com/library/fullstorydev/fullstory-skills/skills/general-analysis/
- GitHub: https://github.com/fullstorydev/fullstory-skills
- Author: [@fullstorydev](https://omgskills.com/library/fullstorydev/index.md)

## More from this repo

- [comparisons](https://omgskills.com/library/fullstorydev/fullstory-skills/skills/comparisons/index.md) — How to structure A vs B comparisons in Fullstory — when to use dimensionality (event/session properties) vs separate...
   - [@fullstorydev](https://omgskills.com/library/fullstorydev/index.md) · 11 stars
- [friction-analysis](https://omgskills.com/library/fullstorydev/fullstory-skills/skills/friction-analysis/index.md) — Finds where users struggle on a page or flow and whether a suspected problem is real.
   - [@fullstorydev](https://omgskills.com/library/fullstorydev/index.md) · 11 stars
- [session-review](https://omgskills.com/library/fullstorydev/fullstory-skills/skills/session-review/index.md) — Used when diagnosing user-reported issues, investigating bugs, analyzing user behavior, or validating UI correctness...
   - [@fullstorydev](https://omgskills.com/library/fullstorydev/index.md) · 11 stars