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

hydrogen

Hydrogen integration. Manage data, records, and automate workflows. Use when the user wants to interact with Hydrogen 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/hydrogen/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 body is a concrete, executable Membrane CLI integration guide with a clear workflow and a polling feedback loop for connection readiness. It is held back by an incoherent opening that misidentifies Hydrogen as a music-production app, some unnecessary prose, and a 'Popular actions' section that does not list any actual actions.

Suggestions

Remove or correct the opening paragraph claiming Hydrogen is a 'local music production application' — it contradicts the hydrogenplatform.com conversation/message/contact integration that follows.

Populate the 'Popular actions' section with real Hydrogen action examples (e.g. listing/creating conversations or messages) instead of restating the generic discovery command.

Trim explanatory rationale ('so you can focus on the integration logic rather than auth plumbing') and move the detailed clientAction/proxy flag reference into a separate reference file to improve conciseness and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and a flag table, but opens with an unnecessary explanation of what Hydrogen is ('a local music production application...') and includes rationale prose ('so you can focus on the integration logic rather than auth plumbing'), matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request) with a flag table, but minor gaps remain such as the 'Popular actions' section merely repeating the list command without showing actual Hydrogen actions.	4 / 5
Workflow Clarity	There is a clear install→auth→connect→poll→search→run sequence with a polling feedback loop on connection state (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but 'Step 2' is referenced without being labeled, leaving a minor sequencing gap below the level-5 anchor.	4 / 5
Progressive Disclosure	Content is organized into well-labeled sections in a single file with no external references needed, but some inline detail (the full clientAction object breakdown and proxy flag table) could be split into a reference file, keeping it just below the level-5 anchor.	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 covers both what and when with an explicit 'Use when...' trigger, but relies on generic capability language rather than concrete actions or varied natural trigger phrases. It is functional but reads as boilerplate that could describe many data-integration skills.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with the concrete Hydrogen entities the body actually exposes (e.g. conversations, messages, contacts) to lift specificity.

Expand the 'Use when...' clause with concrete natural trigger phrases users would say, including synonyms and the platform domain, to improve trigger-term coverage.

Align the description's claimed capabilities with the body's real integration surface (the body targets hydrogenplatform.com conversations/messages/contacts, not generic 'records').

Dimension	Reasoning	Score
Specificity	It names the Hydrogen domain and enumerates several action areas ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete capabilities, fitting the 'names domain and 1-2 actions but not comprehensive' anchor better than the minimal/generic anchor below.	3 / 5
Completeness	Both 'what' ('Hydrogen integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with Hydrogen data.') are present and explicit, but the trigger is generic rather than concrete, so it stops short of the level-5 anchor.	4 / 5
Trigger Term Quality	Relevant keywords are present ('Hydrogen', 'data', 'records', 'workflows', 'interact with Hydrogen data') but it lacks natural variations or synonyms a user might actually say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Hydrogen' names a specific platform giving it a distinct niche with low wrong-skill trigger risk, though the generic capability verbs ('manage data, records, automate workflows') leave minor overlap risk with data/CRM 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/hydrogen/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.