Name: human-api
Rating: 60.8 (1 reviews)
Author: membranedev

human-api

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

Quality

71%

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

Quality

Content

82%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 a strongly actionable, well-sequenced guide with executable Membrane CLI commands and a useful connection-state feedback loop; its main weaknesses are minor verbosity and a couple of dangling cross-references that slightly blur the workflow.

Suggestions

Resolve the dangling 'skip to Step 2' reference by labeling the connect/poll subsections consistently (e.g. 'Step 1', 'Step 2') or removing the forward reference.

Trim the product-overview paragraph and the 'so you can focus on the integration logic rather than auth plumbing' aside to reduce token overhead.

Either explain the nested 'Human API Overview' bullet hierarchy (Profile → Sources → Records) or remove it, since it currently adds structure without actionable meaning.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands throughout, but includes a few trimmable explanations such as the product overview paragraph and 'so you can focus on the integration logic rather than auth plumbing', matching 'Efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure/get, action list/run, request proxy) plus a complete flag table, covering the common cases concretely, matching 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll → search → run sequence with a polling feedback loop for connection states (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the dangling 'skip to Step 2' reference and the unlabeled '1b' subsection introduce minor gaps.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no external bundle files to navigate, but everything is inlined in a single ~140-line file and a few sections (the unexplained nested Overview bullets, the 'Popular actions' restatement) could be tighter, matching 'Good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	17 / 20 Passed

Description

61%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 clearly identifies a distinct, named platform and includes an explicit 'Use when' trigger, but its action verbs are generic and its trigger vocabulary is narrow, omitting the natural health-data terms users would actually say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Human API operations such as retrieving wearable/medical data, querying health records, or automating data sync workflows.

Broaden the trigger clause with natural terms users say — e.g. 'Use when the user wants to access health data, wearables, medical records, or Human API data.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('Human API integration') but its actions are generic and abstract — 'Manage data, records, and automate workflows' lists no concrete operations, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Human API data') are present and explicit, but the 'when' could be more specific with concrete trigger phrases, matching the anchor for 'Has both what and when; when could be more explicit'.	4 / 5
Trigger Term Quality	It repeats the core keyword 'Human API' in the trigger clause but offers no synonyms or natural variations a user might say (e.g. health data, wearables, medical records), fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Human API' is a specific named platform with a distinct trigger, giving it a clear niche and minimal overlap with other skills, matching 'Clear niche with distinct triggers; minimal conflict risk'.	5 / 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/human-api/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.