connector-weatherapi Skill (Caffeine): Weather in Motoko

Gives Claude Caffeine's recipe for reading WeatherAPI.com weather data from a Motoko canister.

Installs: 8.5K; on skills.sh
Stars: 2; on GitHub
Updated: Oct 2026; last repo commit

connector-weatherapi tells Claude to read weather data through the weatherapi-client mops package, not hand-written HTTPS calls to api.weatherapi.com. It shows a canister that reads current temperature and a three-day maximum series, lists the nine operations in one module, and explains the API key setup, error messages and optional-field quirks.

It loads when a Caffeine build mentions weather, forecast, astronomy, timezone, IP geolocation, marine or tide data, or location autocomplete. It is useful only if you build on Caffeine AI or write Motoko canisters. You need a WeatherAPI.com key.

Good for

Developers building apps on Caffeine AI that show weather
Motoko canister authors who need forecasts, astronomy or IP lookup
Anyone wiring a WeatherAPI key into an Internet Computer app

Install connector-weatherapi

Claude Code

Copy this prompt.

Install the connector-weatherapi skill in Claude Code. Run this command:

npx skills add https://github.com/caffeinelabs/skills --skill connector-weatherapi

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

This skill is for building on Caffeine AI, the app builder from Caffeine Labs, or for writing Motoko code for the Internet Computer. It is not a general weather tool. It is one file and bundles no scripts. It has you write Motoko code into a project, so there is no Claude app upload route.

From its listing on skills.sh. Source.

What's in the skill

When it loads

MANDATORY recipe for every Caffeine build that reads weather data from a canister. The supported path is the `weatherapi-client` mops package (WeatherAPI.com) over outbound HTTPS, authenticated with a query-string API key. Hand-rolling `ic.http_request` calls to `api.weatherapi.com` is a FORBIDDEN anti-pattern — it bypasses the non-replicated-outcall safeguard (WeatherAPI bodies carry per-request clocks and fail consensus), the generated JSON decoding, and the API-key handling. Load this skill whenever the user, spec, or any prior task mentions weather, forecast, temperature, humidity, wind, rain, snow, conditions, sunrise, sunset, moon phase, astronomy, timezone, IP geolocation, marine or tide forecasts, or location autocomplete — and BEFORE writing any code that touches a weather endpoint.

Sections in SKILL.md

The nine operations
API key setup
Calls are non-replicated by default
Everything is optional
Empty string and zero mean "omit"
Errors

Key facts

Author: Caffeine Labs (vendor's own repo)
License: Apache-2.0 (LICENSE file and README)
Version: 0.3.0 (SKILL.md frontmatter)
Installs on skills.sh: 8,478 (Nov 2, 2026)
GitHub stars: 2 (Nov 2, 2026)
Last repo commit: Oct 30, 2026
What it includes: 1 file, SKILL.md. No scripts.
Needs: A WeatherAPI.com API key, and the weatherapi-client mops package at ~0.4.0 (SKILL.md frontmatter)
Works in: Builds on Caffeine AI and Motoko canisters. The README says its skills work with agents that support skills

What it includes

Canister that reads current temperature and three-day maximum temperatures
It uses realtimeWeather and forecastWeather from Apis/APIsApi.
Network · Backend snippet
Current, forecast, history, future, marine, astronomy, time zone, IP lookup and search
All nine are read-only GET requests, per SKILL.md.
Network · Nine operations
Sign up at weatherapi.com and pass the key as auth = ?#apiKey key
SKILL.md says the client appends the key to the request URL and tells you to keep it in a stable variable set by an admin call.
Read · API key setup
The package defaults to non-replicated outcalls because responses carry per-request clocks
Read · Non-replicated calls
Every response field is optional; read them with a do ? block
Read · Optional fields
An empty string or zero means "omit"; hour = 0 omits the filter
Read · Omitted parameters
Non-2xx responses throw an error with HTTP status and the first 100 characters
SKILL.md says 401 is a bad key, 403 an endpoint not on your plan, 400 an unresolvable query.
Read · Error handling

From the official docs

Permissions

Low risk

connector-weatherapi has no scripts, but the code it has Claude write sends your WeatherAPI key in request URLs. Our advice: hold the key in an admin-set variable and never log URLs.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

The API key travels in the URL
SKILL.md says WeatherAPI takes no Authorization header, so the client adds ?key= to the request URL. Keep the key in an admin-set variable and never log the built URL. github.com
Paid endpoints return 403 on free keys
History, future, marine and 14-day forecasts need a paid WeatherAPI plan. Check your plan before you build on them. github.com

Technical details

Turning on read-only	No read-only switch.
Talks to	api.weatherapi.com
Sign-in and keys	A WeatherAPI.com key passed as a query-string credential, per SKILL.md. The skill itself stores nothing.
Scopes	Claude writes Motoko code for your project (src/backend/main.mo in the example) The code you ship calls WeatherAPI with your API key

Questions

What does connector-weatherapi do?

It tells Claude how to read WeatherAPI.com data from a Motoko canister in a Caffeine build. It uses the weatherapi-client package and a query-string API key.

Can I use it outside Caffeine?

Only if you write Motoko for the Internet Computer. The skill is built around Caffeine builds, canisters and mops packages, and its code is Motoko.

How do I install it?

Use the install box at the top. The README documents npx skills add for the whole repo and fetching a single SKILL.md.

Is WeatherAPI free?

SKILL.md says the free tier covers current weather, 3-day forecast, astronomy, timezone, search and IP lookup. History, future, marine and 14-day forecasts need a paid plan and return 403 on free keys.

Where does my API key go?

SKILL.md says the client appends it as ?key= in the request URL, so it appears in the URL. It tells you to keep it in a stable variable written by an admin-only call and never log the built URL.

Why does hour = 0 return the whole day?

SKILL.md says zero and empty strings are dropped as "not supplied", so hour = 0 omits the hour filter and you get the full hourly array.

Is it official?

Yes. It sits in the caffeinelabs/skills repo, under the Caffeine Labs GitHub organization, whose description reads "Create brilliant apps and websites through chat!".

Is it safe?

The skill bundles no scripts. It has Claude write code that sends a WeatherAPI key in request URLs. Our advice: keep the key in an admin-set variable as SKILL.md says, and never commit it.

Information

updated Nov 2, 2026

Repository: caffeinelabs/skills
Folder: skills/connector-weatherapi

caffeinelabs/skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4

connector-weatherapi SKILL.md · github.com
README · github.com
LICENSE · github.com
skills.sh listing · skills.sh