Name: height
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

height

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

Quality

61%

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/height/SKILL.md

Quality

Content

60%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 command-dense and actionable with a clear connection-state workflow, but its quality is undermined by a stray refusal paragraph at the top and redundant action-discovery sections. Structure is good for a single-file skill with no bundle.

Suggestions

Delete the opening 'I don't have enough information to do that...' paragraph; it is irrelevant noise that wastes tokens and confuses the skill's purpose.

Merge the redundant 'Searching for actions' and 'Popular actions' sections, which both demonstrate `membrane action list --intent=QUERY`.

Add an explicit validate-before-act checkpoint for destructive or batch actions (e.g., confirm task/list changes before running mutating actions) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body opens with an irrelevant canned refusal ('I don't have enough information to do that. I'm a large language model...') that is pure padding, and the 'Searching for actions' and 'Popular actions' sections repeat the same discovery command, making it noticeably verbose despite otherwise command-focused content.	2 / 5
Actionability	Provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action run, request) that are mostly copy-paste ready; it stops short of 5 because parameters like CONNECTION_ID are placeholders and the 'Height Overview' entity list gives no actionable detail.	4 / 5
Workflow Clarity	Sequences install -> authenticate -> connect -> poll for readiness -> search -> run, with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and error-field guidance; minor gaps (a 'Step 2' reference under a '1b' heading, no pre-run validation for destructive actions) keep it at 4.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline in one well-sectioned file (Overview, Authentication, Connecting, Searching, Proxy, Best practices) with clear headers and easy navigation; it is not a 5 because some reference-like content (the proxy flag table, best practices) could be split out.	4 / 5
	Total	14 / 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 is third-person, names a clear app niche, and includes an explicit 'Use when' trigger, giving it solid completeness and distinctiveness. It is held back by generic action language and limited trigger-term variety.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Height-specific operations (e.g., 'create and assign tasks, manage lists, view requests') to lift specificity.

Add natural synonyms and entity terms users say (tasks, subtasks, lists, Height tickets) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Height integration') and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Height-specific operations, so it is not comprehensive enough for a 4.	3 / 5
Completeness	Explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Height data'); the 'when' is present and explicit but could be more specific with concrete trigger phrases, so it stops short of 5.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Height', 'Height data', 'interact with Height data') but offers few natural synonyms or variations a user would actually say, sitting at the 'some relevant keywords' anchor rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	'Height integration' targets a specific app niche with distinct triggers and low overlap risk; it is not a 5 because the surrounding language ('manage data, records') is somewhat generic and could overlap with other data-management 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/height/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.