Stats
Actions
Tags
From tomorrow-weather
Retrieve historical weather data for any location and date range using Tomorrow.io (back to year 2000)
How this command is triggered — by the user, by Claude, or both
Slash command
/tomorrow-weather:SKILLweather-history/The summary Claude sees in its command listing — used to decide when to auto-load this command
Use the `tomorrow-weather` MCP server to fetch historical weather data. Call the `get_historical_weather` tool with: - The location the user provides (city name, coordinates, or address) - A start date (required) - An end date (optional, defaults to start date for a single day) - A timestep: "1d" for daily, "1h" for hourly Return a clear summary of the historical conditions including: - Temperature (high, low, average) - Precipitation totals - Wind conditions - Humidity - Notable weather events (storms, extreme temperatures) If the user asks a comparative question (e.g. "was it hotter la...
Use the tomorrow-weather MCP server to fetch historical weather data.
Call the get_historical_weather tool with:
Return a clear summary of the historical conditions including:
If the user asks a comparative question (e.g. "was it hotter last July than this July?"), gather both datasets and compare them side by side.
Note: historical data is available from January 2000 onwards. If the user requests data before that, inform them of the limitation.
npx claudepluginhub chidinwaka/tomorrow-weather-plugin --plugin tomorrow-weather/SKILLResolves GitHub issue via isolated worktree, TDD workflow, and auto-closing PR creation.
/SKILLCreates conventional git commit from conversation intent using git-agent and pushes to remote. Accepts optional Claude model name for co-author.
/SKILLSurfaces current session task from state file, evaluates clarity (prompts for clarification if needed), assesses completion, and verifies if fully done.