ambient-weather-automation
Automate Ambient Weather tasks via Rube MCP (Composio). Always search tools first for current schemas.
67
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/ambient-weather-automation/SKILL.mdQuality
Discovery
22%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 is too vague to effectively guide skill selection. It names the integration (Ambient Weather via Rube MCP/Composio) but fails to specify concrete capabilities or provide trigger conditions. The procedural note about searching tools is implementation detail rather than useful selection criteria.
Suggestions
Replace 'Automate Ambient Weather tasks' with specific actions like 'Retrieve temperature, humidity, and barometric pressure data from Ambient Weather stations'
Add a 'Use when...' clause with natural trigger terms such as 'weather station data', 'outdoor temperature', 'humidity readings', or 'Ambient Weather API'
Remove the procedural instruction about searching tools (this belongs in the skill body, not the description) and use that space for capability details
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Ambient Weather tasks' without specifying what concrete actions are possible (e.g., fetch temperature data, retrieve humidity readings, export weather history). The instruction to 'search tools first' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate Ambient Weather tasks') and there is no 'Use when...' clause or equivalent trigger guidance. The description fails to answer when Claude should select this skill over others. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Ambient Weather', 'Rube MCP', 'Composio') but misses natural user terms like 'weather station', 'temperature', 'humidity', 'weather data', or 'sensor readings' that users would actually say when needing this skill. | 2 / 3 |
Distinctiveness Conflict Risk | 'Ambient Weather' and 'Rube MCP (Composio)' provide some specificity that distinguishes it from generic weather or automation skills, but 'tasks' is too broad and could overlap with other Composio-based integrations or weather-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently communicates how to use Ambient Weather via Rube MCP. The workflow is clear with proper validation steps, and the content respects token budget by avoiding unnecessary explanations. The main weakness is that the tool call examples use a pseudo-code format rather than showing actual executable syntax.
Suggestions
Clarify the exact syntax for tool calls - are these JSON payloads, function calls, or another format? Show one complete, copy-paste ready example.
Add a concrete example of what a successful RUBE_SEARCH_TOOLS response looks like so Claude knows what to expect and parse.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of what Ambient Weather or Composio are. Every section serves a purpose and assumes Claude understands the underlying concepts. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameters, but uses pseudo-code style blocks rather than actual executable code. The examples show structure but aren't copy-paste ready since they're not in a real programming language or actual MCP call format. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow pattern with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status before execution and addresses error recovery through the 'Known Pitfalls' section. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Quick reference table provides efficient navigation for common operations. | 3 / 3 |
Total | 11 / 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
- ComposioHQ/awesome-claude-skills
- Commit
2790447
- 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.