← Search

blender-time-of-day
Developer tools 📌 Pinned version: commit 71d031d
⚙ Needs: Before you start: read this whole install prompt…

blender-time-of-day

Time of day and atmosphere in Blender 5.2: a measured sky and matching sun or moon for dawn, morning, noon, golden hour, sunset, blue hour, overcast and night with stars and city glow, grey-card exposure balancing, height fog from visibility, god rays, Cycles and EEVEE volumetrics, a compositor grade, and stylized moods (cyberpunk, horror, underwater, desert) in one script call.

At a glance
What
Time of day and atmosphere in Blender 5.2: a measured sky and matching sun or moon for dawn, morning, noon, golden hour, sunset, blue hour, overcast and night with stars and city glow, grey-card exposure balancing, height fog from visibility, god rays, Cycles and EEVEE volumetrics, a compositor grade, and stylized moods (cyberpunk, horror, underwater, desert) in one script call.
Cost
Free
Needs
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.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

⌁

Install

Copy the install package below, then paste it into Muse📌 Pinned version: commit 71d031d
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a build before installing →

🧭 What this touches
Based on the install prompt we scanned, this build does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-19
🔒 Security and provenance
📌 Pinned version: commit 71d031d · 2026-10-19
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

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: Blender 5.2 LTS or newer is required to USE this skill (installing it is only copying files, but every use runs Blender code inside Blender). No account, no API key, no paid service, and nothing is sent anywhere. This listing installs only the blender-time-of-day skill: blender-core, which SKILL.md says holds the execution model, blender-lighting-lookdev (studio and product lighting), blender-rendering (render settings), blender-weather-fx (rain, snow, wetness and lightning) and the 17 other blender-* skills in the same repository are NOT installed. Install "blender-time-of-day" for me. It sets the time of day and the atmosphere of a Blender 5.2 scene in one script call: a measured sky with a matching sun or moon lamp for dawn, morning, noon, golden hour, sunset, blue hour, overcast and night, exposure balanced on a grey card, height fog derived from meteorological visibility, and stylized moods (cyberpunk, horror, underwater, desert) with accent lights and a compositor grade. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-time-of-day/ folder at the pinned commit: SKILL.md, references/fog-volumetrics.md, references/light-values.md, references/night-and-moods.md, scripts/_bpyx.py, scripts/scene_mood.py) Pinned version: install the code at commit 71d031dab8bc6729504d11a78cbe91945401045f exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/EL4CTEO/blender-skills into a temporary folder, check out commit 71d031dab8bc6729504d11a78cbe91945401045f, and copy the skills/blender-time-of-day/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-19: [FINGERPRINTS] - SKILL.md: SHA-256 d32b342df7950c13d4f3838a94be96c7cb6a118a1c53a87dc18149d3bef4acf4 - references/fog-volumetrics.md: SHA-256 8371b4b7517363b97e8b023611a5ea8351c913d60205a09805bb47f76d62320c - references/light-values.md: SHA-256 21569a5d3c92271f6e219ee77cf3982c9cde59d4d1f3090528086d608030a3a8 - references/night-and-moods.md: SHA-256 662299d09b341c70488a1e934ce07437610c2ad0dddc92bed93b348e94a76442 - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/scene_mood.py: SHA-256 c82cd0a010ac657df727301a89403cc9f5c599bda84349e2e80ed3c2f6d0b134 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, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds six files: SKILL.md (6,715 bytes), three reference documents (references/fog-volumetrics.md, 3,124 bytes, fog density from visibility, phase functions, Cycles and EEVEE volumes and god rays; references/light-values.md, 2,884 bytes, sun colors and strengths measured in Blender 5.2.2 by elevation, lamp units, color temperatures and practical wattages; references/night-and-moods.md, 4,075 bytes, night and blue-hour rules and the four stylized moods), and two Python scripts under scripts/ (scripts/_bpyx.py, 4,503 bytes; scripts/scene_mood.py, 22,978 bytes). - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. The files name no account, no API key, no telemetry and no remote service, and neither script contains any network code (no HTTP, no network sockets, no uploads). The word "socket" in the files is a Blender node socket (a compositor group socket, a link's from_socket), not a network socket. No script in this folder reads any environment variable, and neither script uses subprocess. - scripts/scene_mood.py runs inside Blender, not on the host by itself: given a time preset (noon, morning, afternoon, golden, sunrise, sunset, blue_hour, night or moonless) or a mood (cyberpunk, horror, underwater or desert), with optional overrides for sun elevation and heading, overcast, fog visibility, fog height, fog color and anisotropy, moon elevation, city glow and stars, it builds ENV_World (a Multiple Scattering sky texture by day, or a night dome with a zenith gradient, horizon city glow and stars visible to camera rays only), the ENV_Mood collection (a Sun lamp as the sun or the moon, a fog box volume when fog is requested, and a magenta and cyan accent area-light pair for the cyberpunk mood), and, for moods that need one, the ENV_Grade compositor tree (bloom, white point, saturation); it sets the AgX view transform and look and the exposure balance, and, when fog is on, the EEVEE volumetric shadow, sample and range settings and the Cycles volume bounces. It meters a grey card between the ground and a wall facing the key light, scales the environment lights to the preset brightness, and returns the key light strength, color and elevation, the exposure, the practical scale and any warnings as JSON. It does not overwrite a compositor tree that is not named ENV_Grade (it reports that instead), and re-running it replaces only the objects and materials it made itself (names starting with ENV_Mood_); my own objects are untouched, and the script writes no file. scripts/_bpyx.py is the shared helper it imports (argument parsing after "--", JSON output, object, node and enum helpers); it is a synced copy of the repository's shared/_bpyx.py. - At use time, everything runs locally in my own Blender, on a scene file I point you at: either through blender-core's routes (live through blender-mcp or headless through its launcher, neither of which this listing installs), or directly with a Blender command such as blender -b scene.blend -P scene_mood.py -- --time golden. The script changes the current scene in memory only (world, environment lights, fog, view and volume settings); keeping the change means saving the .blend myself in Blender. SKILL.md asks to verify every mood with a render, not the viewport, because fog, stars and bloom only show in rendered output, and warns that very dense fog in EEVEE can band, where Cycles is preferred. No use is launched by this install. - The scope is the time of day and the atmosphere only: sky, sun and moon, exposure balance, fog and volumetrics, night, and the four stylized moods. SKILL.md states the execution model is in blender-core, studio and product lighting are in blender-lighting-lookdev, render settings are in blender-rendering, and rain, snow, wetness and lightning are in blender-weather-fx, and its mood notes also point to blender-weather-fx for wet streets and dust particles and to blender-rendering for verification renders; none of those skills is installed by this listing, so their know-how is missing until they are installed separately. The repository's own installer and Claude Code plugin install all 22 skills at once and are not the route used here. 3. When I say "yes, install", install it as a skill: copy the whole blender-time-of-day folder into the agent's skills directory, in a folder named "blender-time-of-day", keeping all six files with their references/ and scripts/ subfolders. 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (for example: install Blender 5.2 LTS or newer myself if I do not have it, and install blender-core, blender-lighting-lookdev, blender-rendering, blender-weather-fx or any other specialized blender-* skill separately if I want them; using the skill is a separate step that only starts when I ask for it). 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.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.