Name: hotjar
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

hotjar

Hotjar integration. Manage data, records, and automate workflows. Use when the user wants to interact with Hotjar data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/hotjar/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete, copy-paste-ready CLI commands and a well-structured connection workflow including state-validation checkpoints, though it opens with unnecessary explanatory padding and could offload some detail to reference files.

Suggestions

Trim the introductory paragraph that explains what Hotjar is and who uses it; Claude already knows this and it adds tokens without guidance value.

Fix the step numbering — the body references 'Step 2' but no Step 1/Step 2 labels exist — so the connection flow reads as a coherent numbered sequence.

Consider moving the proxy options table and action inputSchema/outputSchema detail into a short reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what Hotjar is and its audience ('typically used by product managers, UX designers, and marketers') is padding Claude already knows, and prose like 'so you can focus on the integration logic rather than auth plumbing' could be trimmed, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Commands are fully executable and copy-paste ready across install, auth, connection, action search/run, and proxy, with flags and a clear options table, matching the 'fully executable; copy-paste ready commands covering common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with validation checkpoints (poll --wait, state checks for READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-auth feedback loop, but the orphaned 'Step 2' reference and unlabeled first step are minor gaps, fitting the 'clear sequence with most checkpoints; minor validation gaps' anchor.	4 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections (Overview, Working with Hotjar, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references, though the ~160-line single file could move the proxy options or action-schema detail into a reference, fitting the 'good structure; most content appropriately placed; minor organization gaps' anchor.	4 / 5
	Total	16 / 20 Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description correctly uses an explicit 'Use when' trigger and names a distinct niche (Hotjar), but its action list is generic rather than Hotjar-specific and omits the natural feature terms users would say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Hotjar capabilities such as 'pull heatmap data, fetch session recordings, and export survey responses'.

Expand the trigger clause to mention the natural feature terms users say, e.g. 'Use when the user wants to work with Hotjar heatmaps, session recordings, surveys, or feedback.'

Drop the vague 'Manage data, records' phrasing in favor of named Hotjar resources to sharpen specificity and reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Hotjar) but the listed actions — 'Manage data, records, and automate workflows' — are generic and not concrete Hotjar-specific operations, matching the 'names domain but actions minimal or generic' anchor.	2 / 5
Completeness	Both a 'what' (Hotjar integration; manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Hotjar data') are present, though the trigger clause could be more specific, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	The natural keyword 'Hotjar' and 'data' appear in 'Use when the user wants to interact with Hotjar data', but common user variations like heatmaps, session recordings, and surveys are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named service Hotjar gives it a clear niche with minimal conflict risk, though the generic action verbs leave minor overlap with other data-integration skills, fitting the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/hotjar/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.