aerisweather
AerisWeather integration. Manage data, records, and automate workflows. Use when the user wants to interact with AerisWeather data.
61
52%
Does it follow best practices?
Impact
Pending
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.
This description identifies the integration target (AerisWeather) but fails to specify concrete weather-related capabilities or natural trigger terms users would employ. The generic phrasing 'manage data, records, and automate workflows' could apply to almost any integration, making it difficult for Claude to confidently select this skill over others.
Suggestions
Replace generic actions with specific weather capabilities like 'Fetch weather forecasts, retrieve historical weather data, set up severe weather alerts, access radar imagery'
Add natural trigger terms users would say: 'weather data', 'forecast', 'temperature', 'precipitation', 'weather conditions', 'meteorological'
Expand the 'Use when' clause with specific scenarios: 'Use when the user asks about weather forecasts, historical weather data, severe weather alerts, or mentions AerisWeather API'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what kind of weather data operations are possible (e.g., fetch forecasts, retrieve historical data, set up alerts). | 1 / 3 |
Completeness | Has a 'Use when' clause but it's too vague ('interact with AerisWeather data'). The 'what' portion is generic ('manage data, records') and doesn't specify actual capabilities. The trigger guidance lacks specific scenarios. | 2 / 3 |
Trigger Term Quality | Includes 'AerisWeather' as a specific trigger term, but lacks natural variations users might say like 'weather data', 'forecast', 'weather API', 'meteorological data', or 'weather conditions'. | 2 / 3 |
Distinctiveness Conflict Risk | 'AerisWeather' is a specific product name which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to overlap with many integration skills. Without weather-specific triggers, it could conflict with 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.
This skill provides solid actionable CLI commands for AerisWeather integration via Membrane, with clear syntax and examples. However, it lacks validation checkpoints in workflows, includes some unnecessary content (empty overview list, redundant intro), and the popular actions table with empty descriptions adds bulk without value. The best practices section is helpful but the overall structure could be tightened.
Suggestions
Add validation steps after key operations (e.g., 'Verify connection succeeded by running `membrane connection list --json` and confirming the connectionId appears')
Remove or populate the AerisWeather Overview bullet list - currently it lists features without any actionable information
Add descriptions to the popular actions table or remove actions without descriptions to reduce noise
Include error handling guidance for common failure scenarios (auth failures, invalid action IDs, connection issues)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the overview bullet list that adds little value, and the popular actions table has empty descriptions. The introductory paragraph explaining what AerisWeather is could be trimmed. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON input examples. The proxy request section includes a comprehensive options table. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. Missing feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the overview bullet list serves no purpose and could be removed. References to official docs exist but no internal file references for advanced topics. The popular actions table could be in a separate reference file. | 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
d19a82b
- 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.