Name: hex
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

hex

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

67%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 content is actionable and well-structured with a genuine validation feedback loop around connection readiness, but it carries some explanatory padding and a dangling step reference. It is competent and usable without being exemplary.

Suggestions

Trim motivational padding ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens') to tighten conciseness.

Resolve the dangling 'skip to Step 2' reference by labeling the searching/running section as Step 2.

Consider moving the clientAction state matrix and proxy flag table into a reference file so the overview stays lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, but contains padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens and make communication more secure', fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Concrete, executable commands appear throughout (install, login, connection ensure, action run, request with a full flag table), but placeholders like CONNECTION_ID and the absence of a complete end-to-end worked example leave minor gaps.	4 / 5
Workflow Clarity	A clear install-to-run sequence exists with a state-based polling/validation feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the dangling 'skip to Step 2' reference is never labeled, leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized into clear sections (Overview, Working with Hex, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, though some inline material (the proxy flag table, clientAction state detail) could justify a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

62%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 cleanly answers both what the skill does and when to use it, anchored to a specific app, but its action verbs are generic and it lacks richer trigger-term variations. It is solid but not exemplary.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Hex-specific actions such as 'run SQL cells, query projects, trigger schedules, fetch app outputs'.

Expand the trigger clause with natural variations, e.g. 'Use when the user wants to query Hex projects, run Hex cells, or interact with Hex data apps'.

Mention recognizable Hex objects (projects, cells, connections, data apps) in the description to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the Hex domain plus two-to-three actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete operations, matching the anchor for 1-2 named actions with limited concreteness.	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Hex data') are present; the when-clause is explicit but could be more specific, so it sits above 3 but below 5.	4 / 5
Trigger Term Quality	Relevant keywords appear ('Hex', 'data', 'records', 'workflows') but common variations and synonyms a user might say are missing, fitting the 'some relevant keywords' anchor rather than comprehensive coverage.	3 / 5
Distinctiveness Conflict Risk	Naming a specific app ('Hex integration') gives a clear niche with minimal conflict risk, though the generic action verbs ('manage data') create minor overlap risk with adjacent data skills.	4 / 5
	Total	14 / 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/hex/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.