What is heatmap-analyst?

An analyst for website interaction data from Humblytics. It examines clicks on page elements, average page scrolling, and bounce or exit signals to identify possible user-experience problems.

Use it to investigate weak calls to action, high bounce or exit rates, content hierarchy, and layout friction using Humblytics data.

Raw interaction numbers do not explain which page elements are being ignored or where visitors may lose interest. This turns the available signals into ranked recommendations while making clear what the data cannot show.

heatmap-analyst — Skill for Claude Code and Codex by Humblytics

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Humblytics/humblytics-marketing-skills --skill heatmap-analyst

Clone the repo

git clone --depth 1 https://github.com/Humblytics/humblytics-marketing-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/heatmap-analyst/github.svg)](https://agentmods.dev/skills/humblytics/humblytics-marketing-skills/heatmap-analyst)

Your own site

<a href="https://agentmods.dev/skills/humblytics/humblytics-marketing-skills/heatmap-analyst"><img src="https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/heatmap-analyst/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/humblytics/humblytics-marketing-skills/heatmap-analyst"><img src="https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/heatmap-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 128 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,794 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00128	$0.02794
Opus 5.5	$0.00051	$0.01118
Sonnet 5.5	$0.00026	$0.00559
Haiku 4.5	$0.00013	$0.00279

Measured 2mo ago against content hash d13ce0800c1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

heatmap-analyst scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/heatmap-analyst/SKILL.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Heatmap Analyst

Purpose

Analyze Humblytics click-engagement data (element/target-level clicks, a single page-level scroll proxy, and bounce/exit signals) to diagnose UX friction and generate prioritized design recommendations. Live data comes from the Humblytics MCP (the click and page tools — get_clicks_details, get_clicks_breakdown, get_page_details, get_pages_breakdown, get_entry_exit_pages). This skill turns the interaction data Humblytics actually exposes into specific, ranked improvements for layout, CTAs, and content hierarchy.

Scope note — what Humblytics does and does not give you. Humblytics provides element/target-level click counts (with UTM breakdown), a single average scroll percentage per page, and bounce/exit signals. It does NOT provide pixel-level click heatmaps (x/y coordinates), a 25/50/75/100 scroll-depth distribution, rage-click detection, dead-zone maps, or per-device click segmentation. Anything in that second list requires a dedicated heatmap tool (e.g. Hotjar, Microsoft Clarity) — do not promise it from Humblytics. See "NOT available via Humblytics" below.

When to Use

A page has a high bounce rate and you need to understand why
CTAs are present but click-through rate is below benchmark
You want to verify that the important content is actually being seen
Users are reporting confusion or friction on a specific page
You're auditing a page before a redesign or A/B test
Investigating whether traffic from a specific source behaves differently on-page

Setup

This skill reads live data through the Humblytics MCP (server humblytics) — see the repo README to connect it. Once connected, the skill calls mcp__humblytics__* tools; the MCP handles auth, base URL, and property resolution, so there are no keys to paste or .env files to source here. Never paste API keys into chat — the key lives once in the MCP connection headers, not in transcripts.

The MCP auto-resolves the property for a single-property key (the common case). For a multi-property key, call list_properties and pass the chosen propertyId to each tool.

Read the full file on GitHub · 168 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 168 lines · 128 tokens per session scan A d13ce0800c1b

Subscribe to this mod's changes

heatmap-analyst is a skill published in the GitHub repository Humblytics/humblytics-marketing-skills (85 stars, last pushed 1mo ago), licensed MIT. It adds 128 tokens to every session and 2,794 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Analytics and metrics Claude Code Design and UX ab-testing agent-skills attribution claude

heatmap-analyst next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
heatmap-analystHumblytics/humblytics-marketing-skills	Skill	85	1mo ago	MIT	A	128	Claude Code, Codex
building-canvasesPostHog/posthog	Skill	41k	yesterday	none	A	148	Claude Code, Codex
composing-grid-canvasesPostHog/posthog	Skill	41k	yesterday	none	A	136	Claude Code, Codex
formatting-slack-messagesPostHog/posthog	Skill	41k	yesterday	none	A	66	Claude Code, Codex
visualizing-change-over-timePostHog/posthog	Skill	41k	yesterday	none	A	169	Claude Code, Codex
styling-sidebar-productsPostHog/posthog	Skill	41k	yesterday	none	A	137	Claude Code, Codex
quill-codePostHog/posthog	Skill	41k	yesterday	none	A	84	Claude Code