code/weather/SKILL.md
Checks the current weather for the user's location using live online data. Asks for location on first use and saves it for future runs. Use when the user wants a quick weather check or forecast.
npx skillsauth add mostafa-drz/claude-skills weatherInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Check the current weather for your location using live data from Open-Meteo (free, no API key needed).
Read ~/.claude/skills/weather/preferences.md using the Read tool. If not found, no preferences are set.
Check $ARGUMENTS:
help → display help then stopconfig → interactive setup then stopreset → delete ~/.claude/skills/weather/preferences.md, confirm, stopWeather — Check current weather for your location
Usage:
/weather Show weather for saved location
/weather Berlin Show weather for Berlin
/weather config Set your default location
/weather reset Clear saved location
/weather help This help
Examples:
/weather Uses your saved city
/weather "New York" One-off check for New York
/weather Tokyo One-off check for Tokyo
Current preferences:
(shown above under Preferences)
Use AskUserQuestion:
Q1 — "What city are you in?" (text input via Other)
Q2 — "Temperature unit?"
Save to ~/.claude/skills/weather/preferences.md.
Delete ~/.claude/skills/weather/preferences.md and confirm: "Preferences cleared. Using defaults."
If no preferences file exists and no city argument was provided:
$ARGUMENTS contains a city name (not help/config/reset) → use that cityUse WebFetch to call the Open-Meteo geocoding API:
https://geocoding-api.open-meteo.com/v1/search?name={city}&count=1&language=en&format=json
Extract latitude, longitude, and name (resolved city name) from the first result.
If no results found, tell the user and ask for a different city.
Use WebFetch to call the Open-Meteo forecast API:
https://api.open-meteo.com/v1/forecast?latitude={lat}&longitude={lon}¤t=temperature_2m,relative_humidity_2m,apparent_temperature,weather_code,wind_speed_10m,wind_direction_10m&temperature_unit={celsius|fahrenheit}&wind_speed_unit=kmh&timezone=auto
Show a fun, concise weather card:
{weather emoji} Weather in {City}
Temperature: {temp}°{C/F} (feels like {apparent}°)
Conditions: {description from weather code}
Humidity: {humidity}%
Wind: {speed} km/h {direction}
{fun one-liner comment about the weather}
Weather code mapping (WMO codes):
Emoji mapping:
If no preferences existed and no city argument was given, ask:
Save {City} as your default location?
If yes, write preferences file.
development
--- name: triage-board description: >- Generates a structured triage artifact from the current conversation's findings — a self-contained Desktop folder with a JSON Schema, schema-conformant report.json, prose markdown, and a single-file HTML viewer. Viewer ships with MD / CSV / JSON download buttons in the header and a per-finding "Copy as Markdown" action that produces a GitHub/Linear/Notion-ready ticket block. Stateless — triage state lives in the user's ticket system, not in the
development
Runs a beginner-mind end-to-end UI audit of any running app — local dev server, staging, production, or a specific URL. Drives Chrome through every interactive element on the target surface, collects structured findings (severity, category, where, symptom, impact, repro, triage), and hands the result off to `/triage-board` which produces the Desktop folder (schema + JSON + Markdown + single-file HTML viewer with MD/CSV/JSON exports and a per-finding Copy as Markdown button). Use when you want fresh-eyes verification of a feature, page, modal, flow, branch, or whole app — before shipping, before review, before a demo, or any time the UI deserves a careful poke.
development
Reviews the user's past Claude Code conversations from a wellbeing perspective — sentiment, tone, emotional arc, recurring patterns — and generates a supportive, science-grounded report in both Markdown and HTML. Default lookback is 48 hours across all projects. Uses recognised emotion frameworks (Plutchik, Ekman, Russell's circumplex, Pennebaker linguistic markers) and cites the science behind every observation. Learns the user's baseline tone over time so future reports flag genuine shifts, not noise. Use when the user asks for an emotional/wellbeing recap, mood check, sentiment review, or wants to understand their own ups and downs across recent work sessions.
development
--- name: workflow-advisor description: >- Analyzes recent Claude Code conversations and local Claude state (skills, settings, memory files, CLAUDE.md), researches the latest Claude Code features and best practices online, and suggests one workflow improvement at a time with reasoning and a concrete action item. Can save accepted suggestions to memory for tracking. Use when you want to discover underused Claude Code features, improve your development workflow, stay current with the lat