Weather Fetcher

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — None to install this skill — no account, no key, no payment. One use-time network call, disclosed up front: at use time it fetches Dubai's current temperature from the free Open-Meteo API (api.open-meteo.com, no API key) via WebFetch. It is not user-invocable (user-invocable: false): it is meant to be called by another skill or workflow, for example the weather-svg-creator demo in the same repository. Install "Weather Fetcher" for me. It fetches the current temperature for Dubai, UAE and returns just the value and its unit: it calls the free Open-Meteo forecast API for Dubai's fixed coordinates (latitude 25.2048, longitude 55.2708) with WebFetch, in Celsius or Fahrenheit as the caller requests, reads current.temperature_2m from the JSON, and reports it. Open-Meteo needs no API key. It writes no files and fetches nothing else — a minimal, real building block for the weather-card demo in the same repository, with the city hardcoded to Dubai. Its folder is a single SKILL.md file. Repository: https://github.com/shanraisshan/claude-code-best-practice (the skill is the whole .claude/skills/weather-fetcher/ folder at the pinned commit: SKILL.md, 1 file in total) Pinned version: install the code at commit cd8e296b06dd1dea732ec15e39645b4edba09bcf exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/shanraisshan/claude-code-best-practice into a temporary folder, check out commit cd8e296b06dd1dea732ec15e39645b4edba09bcf, and copy the .claude/skills/weather-fetcher/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 4350c64fd975416da3a1ed34c6f1add622b28413edc377994f4a320263cf661e If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The folder holds 1 file only: SKILL.md (1,588 bytes, frontmatter name weather-fetcher, user-invocable: false, allowed-tools WebFetch only). There is no script, no companion file and no other code in it. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no weather request is made. - At use time it makes exactly one outbound request: a GET to api.open-meteo.com (the free Open-Meteo forecast API, no key) carrying only Dubai's fixed coordinates and the requested temperature unit in the query string. It reads no personal information or credentials, writes no file, and sends nothing anywhere else. - Do not fetch any weather, do not call Open-Meteo, and do not use the skill in any way during this install: using it is a separate step that only starts when it is called later. 3. When I say "yes, install", install it as a skill: copy the whole weather-fetcher folder into the agent's skills directory, in a folder named exactly "weather-fetcher", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: weather-fetcher), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that this skill only ever fetches Dubai's current temperature from Open-Meteo, that it is called by other skills rather than invoked directly, and that using it is a separate step that only starts when it is called later). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.