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

Blog Docs Log in Get started

solcast

Solcast integration. Manage Organizations. Use when the user wants to interact with Solcast 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/solcast/SKILL.md

Quality

Content

75%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, actionable integration guide built around concrete Membrane CLI commands, with a clear connection workflow and explicit state-based validation. Its main weaknesses are minor: a little over-explanatory prose, a "Popular actions" section that defers rather than names actions, and slightly inconsistent step numbering.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, executable CLI commands with brief operational guidance, and it does not explain basic concepts Claude already knows. Minor over-explanation (the "solar developers, grid operators, and researchers" audience line and the "so you can focus on the integration logic rather than auth plumbing" commentary) could be trimmed, matching "Efficient; minor instances of over-explanation."	4 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure/get, action list/run, request proxy) plus a thorough proxy flags table. It is not a 5 because the "Popular actions" section does not name actual Solcast actions and there is no fully-worked end-to-end example with real values.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-for-ready → search → run/proxy sequence with state-based validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-user-action feedback loop. It falls short of 5 because step numbering is loose ("Step 2" and "1b" are referenced without consistent labels) and error recovery for CONFIGURATION_ERROR/SETUP_FAILED is thin.	4 / 5
Progressive Disclosure	The document is well-organized with clear section headers and easy navigation, and there are no problematic nested references. It is not a 5 because all content is inline with no split-out reference files for a ~140-line skill, though little of it clearly belongs elsewhere.	4 / 5
	Total	16 / 20 Passed

Description

48%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 an explicit trigger clause and benefits from a unique brand name, but it is let down by a thin and slightly off-scope statement of capabilities that fails to convey the skill's actual solar-forecasting function. Trigger terms rely on the brand alone and omit the natural synonyms users would say.

Suggestions

Replace the vague "Solcast integration. Manage Organizations." with the skill's real capabilities, e.g. "Fetch solar irradiance, radiation and power forecasts, energy estimates, and historical/live data from Solcast."

Expand the trigger to include natural synonyms, e.g. "Use when the user needs solar forecasting, irradiance data, power forecasts, or historical solar weather data from Solcast."

Drop or reframe "Manage Organizations" since it does not reflect the skill's documented Sites/Forecasts focus and could mislead.

Dimension	Reasoning	Score
Specificity	It names the domain ("Solcast integration") and one thin action ("Manage Organizations"), but the action is generic and does not reflect the skill's actual scope (sites, radiation/power forecasts, energy estimates, historical/live data). This matches the anchor "Names the domain but actions are minimal or generic" rather than a 3, which would require 1-2 genuinely concrete actions.	2 / 5
Completeness	An explicit "Use when..." clause is present, but the "what" is too thin to convey the skill's purpose — "Solcast integration" only names the domain and "Manage Organizations" is a single tangential action that omits the skill's real forecasting/irradiance capabilities. A reader cannot determine what the skill actually does, which caps completeness despite the explicit trigger.	3 / 5
Trigger Term Quality	It includes the brand keyword and a reasonable trigger phrase ("Use when the user wants to interact with Solcast data"), but misses the natural synonyms a user would actually say (solar forecast, solar irradiance, power forecasts). This fits "Some relevant keywords but missing common variations or synonyms"; it is not a 4 because coverage is limited to the brand plus generic "data".	3 / 5
Distinctiveness Conflict Risk	"Solcast" is a unique named app, giving a clear niche and low conflict risk, but the trigger terms are thin (only "Solcast data") rather than the comprehensive distinct triggers of a 5. This matches "Mostly distinct; minor overlap risk with closely related skills".	4 / 5
	Total	12 / 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/solcast/SKILL.md
Commit: f484c82

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