Mars Weather Pro

Get current weather and forecasts (no API key required).

Security Scan

The skill's runtime instructions match a simple wttr.in/Open‑Meteo weather helper, but the package metadata and visible name ("Mars Weather Pro") don't match the actual behavior — this mismatch and owner/slug inconsistencies are suspicious even though the runtime actions themselves are low-risk.

Purpose & Capability

The skill is named and published as "Mars Weather Pro" (registry metadata), but the SKILL.md documents an Earth-weather helper using wttr.in and Open‑Meteo. The _meta.json slug is "weather" while registry metadata lists a different slug/owner; these naming/metadata mismatches suggest either sloppy packaging or intentional mislabeling.

Instruction Scope

Runtime instructions are limited and explicit: they run curl against wttr.in and api.open-meteo.com to fetch weather data and optionally save a PNG to /tmp. The instructions do not read local files, access environment variables, or transmit unrelated data.

Install Mechanism

No install spec and no code files — instruction-only skill that relies on curl being present. This is low-risk because nothing is written to disk or downloaded by the skill itself.

Credentials

No environment variables, credentials, or config paths are required. The declared dependency (curl) is appropriate for the described network calls.

Persistence & Privilege

The skill is not always-enabled and uses normal autonomous invocation settings. It does not request persistent system presence or modify other skills/configurations.

What to consider before installing

This skill appears to perform simple weather lookups via wttr.in and Open‑Meteo (no API keys). However, the name/metadata mismatches ("Mars Weather Pro" vs SKILL.md showing Earth weather, different slug/owner IDs) are inconsistent and worth questioning before install. If you expected Mars-specific data, this does not provide it. Because the skill issues HTTP(S) requests with whatever location you pass, avoid embedding sensitive data in query strings (e.g., personal coordinates or private location identifiers). If provenance matters, ask the publisher for clarification or prefer a skill whose name, metadata, and runtime instructions align.

Weather

Two free services, no API keys needed.

wttr.in (primary)

Quick one-liner:

curl -s "wttr.in/London?format=3"
# Output: London: ⛅️ +8°C

Compact format:

curl -s "wttr.in/London?format=%l:+%c+%t+%h+%w"
# Output: London: ⛅️ +8°C 71% ↙5km/h

Full forecast:

curl -s "wttr.in/London?T"

Format codes: %c condition · %t temp · %h humidity · %w wind · %l location · %m moon

Tips:

• URL-encode spaces: wttr.in/New+York
• Airport codes: wttr.in/JFK
• Units: ?m (metric) ?u (USCS)
• Today only: ?1 · Current only: ?0
• PNG: curl -s "wttr.in/Berlin.png" -o /tmp/weather.png

Open-Meteo (fallback, JSON)

Free, no key, good for programmatic use:

curl -s "https://api.open-meteo.com/v1/forecast?latitude=51.5&longitude=-0.12&current_weather=true"

Find coordinates for a city, then query. Returns JSON with temp, windspeed, weathercode.

Docs: https://open-meteo.com/en/docs