Name: stormglassio
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

stormglassio

Stormglass.io integration. Manage Organizations. Use when the user wants to interact with Stormglass.io data.

Quality

73%

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

Quality

Content

81%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 action-packed with executable commands, a well-sequenced connection workflow including state-based validation checkpoints, and clear sectioning. It is held back only by minor padding and by inlining reference-style material that could live in separate files.

Suggestions

Remove the filler line 'Use action names and parameters as needed.' and trim the opening context paragraph about who uses Stormglass.io, since Claude already understands weather APIs.

Move the large flags table and the clientAction object schema into a separate reference file (e.g. references/proxy-and-connection.md) to make the main body a leaner overview.

Add a one-line worked example with a resolved actionId and CONNECTION_ID so the action-run snippet is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, tables, and state descriptions; only minor padding remains, e.g. the opening context paragraph ('maritime businesses, researchers, and developers') and the filler line 'Use action names and parameters as needed.' — fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	Provides concrete executable commands throughout (npm install, membrane login, connection ensure, action run) plus a flags table, with a minor gap that actionId/CONNECTION_ID remain unresolved placeholders requiring a discovery step — matching 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-until-ready feedback loop with error recovery guidance, matching 'clear sequence with explicit validation steps; feedback loops for error recovery'.	5 / 5
Progressive Disclosure	No bundle files exist and the body is well-sectioned with no nested references, but the ~140-line skill inlines all reference-style content (flags table, clientAction schema) rather than splitting it out, fitting 'good structure; most content appropriately placed; minor organization gaps' rather than a clean lean overview.	4 / 5
	Total	17 / 20 Passed

Description

66%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 has a clear trigger clause and a distinctive proper-noun niche, but its capability list is thin and lacks the natural synonyms (weather, marine, tides) users would actually say. It answers both what and when but undersells the breadth of the Stormglass.io API.

Suggestions

Add concrete capabilities to the description, e.g. 'Fetch weather, tide, solar, and astronomy data' instead of the generic 'Manage Organizations'.

Include natural trigger terms users would say — 'weather', 'marine forecasts', 'tides', 'ocean conditions' — alongside the Stormglass.io proper noun.

Tighten the 'when' clause to specific data needs: 'Use when the user wants marine weather, tide, solar, or astronomy data from Stormglass.io.'

Dimension	Reasoning	Score
Specificity	Names the domain ("Stormglass.io integration") and one concrete action ("Manage Organizations"), but omits the actual data capabilities like weather, tide, solar, and astronomy — matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Provides an explicit trigger ("Use when the user wants to interact with Stormglass.io data") and a what ("Manage Organizations"), so both are present; the 'what' is somewhat narrow, fitting 'has both what and when; when could be more specific' rather than the fully concrete 5 anchor.	4 / 5
Trigger Term Quality	Includes the natural proper-noun keyword "Stormglass.io" and the phrase "interact with Stormglass.io data", but misses common synonyms a user would say like weather, marine, forecasts, or tides — matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The repeated proper noun "Stormglass.io" carves out a clear niche with minimal overlap risk against other skills, matching 'clear niche with distinct triggers; minimal conflict risk'.	5 / 5
	Total	15 / 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/stormglassio/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.