analytics-insights
Skill1 starsChanged 37 days agoMITView on GitHub
Turn analytics, funnels, heatmaps and session recordings into behaviour patterns and testable hypotheses, triangulated with research. Use when someone shares analytics data, funnel drop offs, heatmaps, scrollmaps or session recordings and asks what is going on or what to fix.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- teachskillofskills-ai/DigitalMarketingPro-techshutheir own version, first seen Oct 11, 2026
- hyperfx-ai/marketing-skillstheir own version, first seen Jun 3, 2026
- nirholas/XActionstheir own version, first seen Feb 24, 2026
- indranilbanerjee/digital-marketing-protheir own version, first seen Feb 12, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- indranilbanerjee/digital-marketing-pro★ 934same name
- nirholas/XActions★ 648same name
- hyperfx-ai/marketing-skills★ 112same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- accessibility-researchSkill
- ai-browser-walkthroughSkill
- card-sort-tree-testSkill
- competitive-analysisSkill
- diary-studySkill
- interview-guideSkill
- jobs-to-be-doneSkill
- journey-mapSkill
- research-planSkill
- research-readoutSkill
- screener-surveySkill
- stakeholder-interviewsSkill
- survey-designSkill
- synthetic-usersSkill
- usability-test-analysisSkill
- usability-test-planSkill
- user-personasSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Write hypotheses,: not conclusions: "Because a quarter of mobile clicks land on things that aren't links, we believe people expect the …
- Distinctive: line 25
Don't explain the why from numbers alone.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Analytics insights
Analytics tells you what people do and where. Research tells you why. Use one to aim the other.
Steps
- Start from a question: "Where do people drop out of the quote flow?" not "What do the numbers say?"
- Check the data first: date range, tracking gaps, bots and internal traffic excluded, sample size per segment. Note anything that makes it unreliable.
- Find the pattern: funnel steps with the biggest drop, pages where people leave, segments that behave differently (device, new or returning, source).
- Look closer: heatmaps for clicks on things that aren't links and content nobody reaches; session recordings for rage clicks, back and forth, and hesitation. Watch at least ten sessions of the problem step.
- Write hypotheses, not conclusions: "Because a quarter of mobile clicks land on things that aren't links, we believe people expect the cards to be tappable." Each one says how to test it (a usability test, an A/B test, an interview question).
- Triangulate with research and support tickets where possible.
Output
The question, data caveats, the top three patterns with numbers and screenshots, and a hypothesis plus test for each.
Don't
- Don't explain the why from numbers alone. Don't compare periods without checking for seasonality or tracking changes. Don't include anything that identifies a person.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

