Name: meteomatics-weather-api
Rating: 55.2 (1 reviews)
Author: membranedev

meteomatics-weather-api

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

Quality

62%

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/meteomatics-weather-api/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 a well-structured, largely executable guide to driving the Meteomatics API through the Membrane CLI, with a particularly clear connection-and-polling workflow. Its main weaknesses are mild marketing-style padding in the intro and lighter error/verification guidance on the action-execution side.

Suggestions

Trim the opening marketing paragraph (industries served, "highly customized weather queries") to keep the body lean and assume Claude's competence.

Add a concrete worked proxy example (a real endpoint path with --query flags) so the proxy section is fully copy-paste ready.

Add validation/error-recovery guidance for action runs (e.g. how to inspect a non-READY output field or retry on error) to match the strength of the connection workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with direct commands, but the intro paragraph (industries like agriculture, logistics, energy; "highly customized weather queries") and the redundant "Popular actions" re-listing of the action list command add unnecessary explanation Claude does not need.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands with flags are provided throughout (login, connection ensure, action run, proxy table), with only minor gaps from unsubstituted placeholders (CONNECTION_ID, <actionId>, /path/to/endpoint) and the lack of a worked proxy example.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based checkpoints and a feedback loop (poll, interpret READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, poll again after action), though the action-execution half lacks corresponding error/verification guidance.	4 / 5
Progressive Disclosure	The body is organized into clear sections (Overview, Working with the API, Popular actions, Best practices) and is self-contained with no external file references and no bundle files present; a small amount of reference-style content (the full proxy flag table, the clientAction spec) is inline but acceptable for a moderate single-file skill.	4 / 5
	Total	15 / 20 Passed

Description

57%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 establishes a clear, named niche and provides both what and when, but its action language is generic boilerplate and its trigger terms lack natural synonyms or concrete phrasing. It is competent but not exemplary.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete capabilities, e.g. "Query weather parameters, fetch time-series statistics by location and time range, and export PDF reports."

Expand the "Use when" clause with natural trigger phrases users would actually say, e.g. "Use when the user wants weather forecasts, historical meteorological data, or PDF weather reports from Meteomatics."

Add common synonyms/file-format or keyword variations (forecast, meteorological, climate) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Meteomatics Weather API domain but the actions listed ("Manage data, records, and automate workflows") are minimal and generic rather than concrete (e.g. query parameters, fetch time-series, export PDF), matching the anchor where the domain is named but actions are generic.	2 / 5
Completeness	Both a clear "what" (Meteomatics Weather API integration managing data, records, workflows) and an explicit "when" ("Use when the user wants to interact with Meteomatics Weather API data") are present, though the trigger phrasing is thin and repetitive rather than richly concrete, fitting the anchor for both present with "when" that could be more specific.	4 / 5
Trigger Term Quality	Relevant keywords ("Meteomatics Weather API", "weather") are present, but common natural variations and synonyms (forecast, meteorological, climate data) are missing, matching the anchor for some relevant keywords lacking common synonyms.	3 / 5
Distinctiveness Conflict Risk	The named Meteomatics Weather API niche gives a clear, distinct trigger with minimal conflict risk, though the generic boilerplate ("Manage data, records, and automate workflows") introduces minor overlap with other integration skills.	4 / 5
	Total	13 / 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/meteomatics-weather-api/SKILL.md
Commit: f484c82

Reviewed: 6 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.