CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ambient-weather-automation

Automate Ambient Weather tasks via Rube MCP (Composio). Always search tools first for current schemas.

55

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/ambient-weather-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 body is well-structured and actionable with concrete MCP call templates, but workflow clarity is capped by the missing post-execution validation loop for batch tool execution, and minor redundancy slightly reduces conciseness.

Suggestions

Add an explicit post-execution validation step after RUBE_MULTI_EXECUTE_TOOL (e.g., inspect each tool result for errors, retry failures, confirm pagination is exhausted) to lift the batch-operation workflow cap.

Consolidate the repeated 'search tools first' guidance into a single authoritative location to remove redundancy across Prerequisites, Tool Discovery, Step 1, and Known Pitfalls.

Include one or two concrete Ambient Weather example use cases with representative tool slugs/arguments (even noted as illustrative) to make the execution step more copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean with no concept-padding, but the 'search tools first' directive is repeated across Prerequisites, Tool Discovery, Step 1, and Known Pitfalls, which is minor redundancy that could be trimmed.

4 / 5

Actionability

Concrete MCP call templates (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) with copy-pasteable shapes are provided, though arguments use placeholders and no real Ambient Weather example slugs are shown.

4 / 5

Workflow Clarity

The discover -> connect -> execute sequence is clear with a pre-execution connection checkpoint, but the batch RUBE_MULTI_EXECUTE_TOOL step lacks an explicit post-execution validation/error-handling loop, capping this dimension at 3 per the batch-operations guideline.

3 / 5

Progressive Disclosure

A single well-organized file with clear section headers and no nested references; with no bundle files and length slightly over the 50-line simple-skill threshold, it is well structured but not a clean 5.

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 clearly names the niche and integration but is capped by the absence of an explicit 'Use when...' trigger clause and somewhat generic capability language ('Automate ... tasks'). It is distinct but not maximally complete or trigger-rich.

Suggestions

Add a 'Use when...' clause naming concrete Ambient Weather use cases (e.g., 'Use when fetching weather station data, device readings, or automating Ambient Weather workflows').

Replace the generic 'Automate Ambient Weather tasks' with 1-2 specific capabilities (e.g., 'Fetch current conditions and device readings, manage Ambient Weather schedules').

Include natural trigger synonyms such as 'weather station', 'Ambient Weather API', or 'personal weather station' to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('Ambient Weather') and mechanism ('Rube MCP (Composio)') plus one concrete action ('Always search tools first for current schemas'), but 'Automate ... tasks' is generic, so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear (automate Ambient Weather via Rube MCP) but there is no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

'Ambient Weather' is a natural term a user would say, but the description lacks synonyms, variations, or file-extension-style triggers, leaving common phrasings uncovered.

3 / 5

Distinctiveness Conflict Risk

'Ambient Weather' is a specific product niche paired with a specific integration (Rube MCP/Composio), giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

ComposioHQ/awesome-claude-skills

Path

composio-skills/ambient-weather-automation/SKILL.md

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.