/aerisweather

name: aerisweather
description: |
  AerisWeather integration. Manage data, records, and automate workflows. Use when the user wants to interact with AerisWeather data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""

AerisWeather

AerisWeather provides weather data and APIs for developers and businesses. It's used by those needing weather information integrated into their applications or services.

Official docs: https://www.aerisweather.com/support/docs/api/

AerisWeather Overview

• **Observations**
• **Advisories**
• **Storm Reports**
• **Lightning Reports**
• **Tropical Cyclones**
• **Fire Weather**
• **Outlooks**
• **Summaries**
• **Forecasts**
• **Long Range**
• **Sun Moon**
• **Places**
• **Profile**
• **Alerts**
• **Weather Stations**
• **API Usage**

Working with AerisWeather

This skill uses the Membrane CLI to interact with AerisWeather. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to AerisWeather

Use `membrane connection ensure` to find or create a connection by app URL or domain:

membrane connection ensure "https://www.aerisweather.com" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

• **`READY`** — connection is fully set up. Skip to **Step 2**.
• **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
• `clientAction.type` — the kind of action needed:
• `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
• `"provide-input"` — more information is needed (e.g. which app to connect to).
• `clientAction.description` — human-readable explanation of what's needed.
• `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
• `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

• **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

Popular actions

| Name | Key | Description | |---|---|---| | Search Places | search-places | No description | | Get Place Information | get-place-info | No description | | Get Weather Conditions | get-conditions | No description | | Get Current Weather Observations | get-current-observations | No description | | Get Weather Forecasts | get-weather-forecasts | No description | | Get Air Quality | get-air-quality | No description | | Get Air Quality Forecast | get-air-quality-forecast | No description | | Get Weather Alerts | get-weather-alerts | No description | | Get Alerts Summary | get-alerts-summary | No description | | Get Observations Summary | get-observations-summary | No description | | Get Climate Normals | get-climate-normals | No description | | Get Maritime Weather | get-maritime-weather | No description | | Get Weather Indices | get-weather-indices | No description | | Get Convective Outlook | get-convective-outlook | No description | | Get River Gauges | get-river-gauges | No description | | Get Tides | get-tides | No description | | Get Tropical Cyclones | get-tropical-cyclones | No description | | Get Lightning Strikes | get-lightning | No description | | Get Road Weather Conditions | get-road-weather | No description | | Get Drought Monitor | get-drought-monitor | No description |

Running actions

membrane action run <actionId> --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "v