Weather SVG Creator

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, no network. Honest scope: it does NOT fetch any weather itself; it only renders a temperature value it is given, and it writes its two output files to hardcoded paths from the source repository's demo layout (orchestration-workflow/weather.svg and orchestration-workflow/output.md, relative to the current project). Install "Weather SVG Creator" for me. It creates a small SVG weather card for Dubai from a temperature value and unit supplied by the calling context — typically the sibling weather-fetcher skill — using the exact template in its reference.md (300x160 dark card), and writes the card to orchestration-workflow/weather.svg plus a markdown summary to orchestration-workflow/output.md. It never re-fetches or changes the value it is given. A trivial but real demo of the fetcher-plus-renderer pattern. Its folder holds SKILL.md plus reference.md (the templates and design specs) and examples.md (worked Celsius and Fahrenheit examples). Repository: https://github.com/shanraisshan/claude-code-best-practice (the skill is the whole .claude/skills/weather-svg-creator/ folder at the pinned commit: SKILL.md, examples.md, reference.md, 3 files 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-svg-creator/ 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 b157e73e8da5c5705dc0c56c83a47483b0db349ef66e8d0016cd0bbe972ebefa - examples.md: SHA-256 33c25099150c2e2884b7b0487f725b522185521bf2be2808ecd2a624b3267500 - reference.md: SHA-256 1ff5ca7768d1d1e6127789a6d2bcc3a13285646b0add5727bbe448a5bdff1bf3 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 3 files only: SKILL.md (1,247 bytes, frontmatter name weather-svg-creator), reference.md (the SVG and markdown templates with design specs) and examples.md (worked examples). There is no script 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. - At use time it only writes two local files, to the hardcoded relative paths orchestration-workflow/weather.svg and orchestration-workflow/output.md in the current project, using exactly the temperature value it is given. It fetches nothing, reads no personal information or credentials, and sends nothing anywhere. - Do not create any SVG card, do not write any output file, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole weather-svg-creator folder into the agent's skills directory, in a folder named exactly "weather-svg-creator", keeping its 3 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: weather-svg-creator), the 3 files 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 renders a temperature it is given (it fetches nothing itself) and writes to the hardcoded orchestration-workflow/ paths, and that using it is a separate step that only starts when I ask for it 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.