aerisweather
AerisWeather integration. Manage data, records, and automate workflows. Use when the user wants to interact with AerisWeather data.
48
52%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aerisweather/SKILL.mdQuality
Discovery
40%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 relies heavily on the 'AerisWeather' brand name for identification but fails to describe any concrete weather-related capabilities. The actions listed (manage data, records, automate workflows) are generic boilerplate that could describe virtually any integration. It needs specific weather-related actions and trigger terms to be effective.
Suggestions
Replace vague actions with specific weather capabilities, e.g., 'Fetches weather forecasts, historical weather data, severe weather alerts, and radar imagery from AerisWeather API.'
Add natural trigger terms users would say, such as 'weather forecast', 'temperature', 'conditions', 'severe weather alerts', 'radar', 'precipitation'.
Expand the 'Use when' clause with specific scenarios, e.g., 'Use when the user asks about weather conditions, forecasts, historical weather data, or needs to integrate weather information into their application.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. It doesn't describe what kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It has a weak 'what' (manage data, records, automate workflows) and a basic 'when' clause ('Use when the user wants to interact with AerisWeather data'), but the 'when' is essentially just restating the 'what' without providing meaningful trigger guidance. | 2 / 3 |
Trigger Term Quality | 'AerisWeather' is a strong specific trigger term that users would naturally mention. However, the description lacks natural weather-related keywords users might say like 'weather forecast', 'weather data', 'conditions', 'temperature', 'radar', or 'alerts'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'AerisWeather' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with many other integration skills. Without weather-specific terms, it's not clearly distinguishable from other data management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, actionable CLI commands for integrating with AerisWeather via Membrane, with good coverage of authentication, connection management, and action execution. However, it suffers from some bloat — the overview bullet list and description-less action table add little value — and the workflow could benefit from a clearer end-to-end numbered sequence with explicit validation steps. The content would also benefit from splitting reference material into separate files.
Suggestions
Remove or condense the 'AerisWeather Overview' bullet list, which provides no actionable guidance and wastes tokens.
Either add meaningful descriptions to the popular actions table or remove entries with 'No description' — they add noise without value.
Add a concise end-to-end numbered workflow (e.g., 'Quick Start: 1. Install CLI → 2. Login → 3. Create connection → 4. Search actions → 5. Run action') with explicit validation checkpoints after connection creation and action execution.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the overview bullet list that adds no actionable value, and the popular actions table with 'No description' entries is low-signal. The Membrane CLI setup and proxy sections are reasonably efficient, but the overall document could be tightened significantly. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Parameter flags are clearly documented in tables with descriptions. | 3 / 3 |
Workflow Clarity | The connection setup workflow has a reasonable sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, errors), but there's no explicit validation checkpoint after running actions, and the overall flow from install → auth → connect → discover → run could be more clearly sequenced as a numbered end-to-end workflow. The state polling loop is described but lacks a clear retry/timeout strategy. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but it's somewhat monolithic — the popular actions table, proxy reference, and best practices could be in separate files. There are no references to bundle files for deeper content, and the overview bullet list doesn't link to anything actionable. The external docs link is provided but no internal file references exist. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- Reviewed
Table of Contents
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.