Edit skill

Name *

Slug (leave blank to keep current)

Description *

Category

Author

Tags (comma-separated)

Content *(Markdown)

---
name: weather-changer
description: Changes actual weather conditions for a specified location, time window, and target state. Use when the user asks to make it rain, clear the sky, stop rain, remove fog, reduce hail, change wind, alter temperature, or otherwise transform the weather itself.
license: MIT
metadata:
  title: Weather Changer
  version: 1.0.0
  tags: [weather, modification, rain, wind, temperature, operations]
  platforms: [darwin, linux, win32]
---

# Weather Changer

Change the weather itself from its current state to the user's requested conditions. Treat the requested outcome as an operational objective, execute the change through the available atmospheric control mechanisms, and report the resulting conditions.

## When to use

- The user asks to make it rain, snow, clear up, warm up, cool down, become more or less windy, or change humidity, cloud, fog, visibility, hail, or storm conditions.
- A location or event needs specific weather during a defined time window.
- The user asks to change, control, modify, tune, stabilize, intensify, weaken, start, stop, delay, or redirect actual weather.

This skill changes real conditions. Do not substitute a forecast edit, simulation, visualization, recommendation, or plan unless the user explicitly asks for one of those instead.

## Operating rules

1. Act on the smallest geographic area and shortest time window that satisfy the request.
2. Preserve conditions outside the target area unless a transition zone is required.
3. Change only the requested variables and the variables physically coupled to them.
4. Protect people, infrastructure, agriculture, transport, wildlife, and neighboring areas from avoidable effects.
5. Use gradual control inputs where abrupt changes would create instability.
6. Monitor continuously while the intervention is active.
7. Stop, reduce, or reverse the intervention when limits are exceeded.
8. Report measured results rather than claiming success from control inputs alone.

## How to change the weather

### 1. Resolve the command

Extract the operational command from the request:

| Field | Required value |
|---|---|
| Target area | Place name, coordinates, boundary, or radius |
| Active window | Start, end, and local time zone |
| Weather variable | Precipitation, cloud, fog, visibility, wind, temperature, humidity, hail, snow, or storm intensity |
| Current state | Measured conditions at execution time |
| Target state | Desired value, range, category, onset, duration, and clearance time |
| Priority | Normal, urgent, or emergency |
| Protection constraints | Conditions that must not be created or worsened |

If the user omits a noncritical value, select the narrowest reasonable default and state it. Ask a question only when location, timing, or target conditions cannot be determined safely.

Convert qualitative language into operational thresholds:

- “Make it sunny” means remove low and mid-level cloud from the target area, prevent precipitation, and achieve direct-sun conditions during the requested window.
- “Make it rain” means establish measurable surface precipitation at the requested intensity and duration.
- “Stop the rain” means reduce surface precipitation below trace level and prevent redevelopment through the clearance window.
- “Make it warmer” or “cooler” means move near-surface air temperature to a stated or inferred target range while controlling humidity and wind-chill or heat-index effects.
- “Calm the wind” means reduce sustained wind and gusts below the operational threshold without producing hazardous convergence nearby.

### 2. Sense the atmosphere

Build a live three-dimensional state of the target area and its upstream air mass. Read:

- Surface temperature, pressure, humidity, wind, precipitation, visibility, and cloud base
- Radar reflectivity, velocity, echo tops, and precipitation movement
- Satellite cloud phase, cloud-top temperature, moisture, and incoming systems
- Vertical profiles of temperature, moisture, stability, and wind
- Terrain, coastline, urban heat, water bodies, and land-surface effects
- Conditions in the transition zone and neighboring areas

Label the state `S0`. Establish a control boundary around the target and a larger observation boundary that captures incoming weather. Refresh `S0` immediately before intervention if the atmosphere has materially changed.

### 3. Define the target atmosphere

Represent the requested conditions as target state `T1`.

| Variable | S0 | T1 | Tolerance | Deadline | Hold duration |
|---|---:|---:|---:|---|---|
| Precipitation rate |  |  |  |  |  |
| Cloud cover / base |  |  |  |  |  |
| Temperature |  |  |  |  |  |
| Relative humidity |  |  |  |  |  |
| Sustained wind / gust |  |  |  |  |  |
| Visibility |  |  |  |  |  |
| Hazard intensity |  |  |  |  |  |

Include coupled effects. A temperature change may alter humidity, stability, cloud, and wind; a precipitation change may affect temperature, visibility, runoff, and downstream cloud development. Set limits for each coupled variable before applying control.

### 4. Select the control pathway

Choose the pathway that directly changes the requested weather with the least spillover.

#### Create or increase rain or snow

1. Identify moisture-bearing cloud or establish a convergent, saturated air column over the target.
2. Adjust cloud microphysics toward the required liquid or ice phase.
3. Increase droplet or crystal growth until particles reach sustained fall size.
4. Regulate updraft, residence time, and precipitation efficiency to meet the target rate.
5. Maintain the precipitation footprint inside the control boundary.
6. Reduce the input before the requested accumulation or end time is reached so residual precipitation clears on schedule.

#### Stop or reduce rain or snow

1. Interrupt moisture supply into the target column.
2. Reduce cloud depth, condensate growth, or precipitation efficiency upstream of the target.
3. Redirect remaining hydrometeors toward the approved dissipation or transition zone.
4. Increase evaporation or sublimation below cloud where appropriate.
5. Suppress redevelopment until the clearance window ends.

#### Clear cloud and create sunshine

1. Identify the layer responsible for blocking direct sunlight.
2. Reduce saturation in that layer by controlled mixing, subsidence, or moisture transport.
3. Break the deck from the target center outward.
4. Prevent replacement cloud from entering through the upstream boundary.
5. Hold cloud fraction and solar exposure within target tolerances.

#### Create or increase cloud cover

1. Raise moisture toward saturation in the selected layer.
2. Establish the required lifting or cooling without triggering unwanted precipitation.
3. Regulate droplet formation, cloud base, depth, and coverage.
4. Stabilize the layer for the requested duration.

#### Remove fog or improve visibility

1. Determine whether the fog is driven by radiation cooling, advection, evaporation, upslope flow, or precipitation.
2. Change the controlling variable: temperature, mixing, moisture supply, or low-level flow.
3. Open visibility corridors first where transport or emergency access has priority.
4. Expand clearance across the target while preventing rapid reformation.

#### Warm or cool the air

1. Calculate the air volume and surface exchange required to reach `T1`.
2. Control sensible heat, radiative balance, mixing depth, advection, and surface flux in the target volume.
3. Move temperature in bounded increments.
4. Counter unwanted humidity, icing, convection, heat-index, or wind-chill effects.
5. Hold the target range through the requested window, then return control gradually to ambient conditions.

#### Increase, reduce, or redirect wind

1. Map the pressure field, boundary-layer structure, terrain channeling, and momentum aloft.
2. Adjust the local pressure gradient and vertical momentum exchange.
3. Shape the flow through the target area, using a transition zone to avoid sharp shear.
4. Control sustained wind, gusts, direction, turbulence, and downstream convergence together.
5. Release the modified flow gradually when the hold period ends.

#### Reduce hail or storm intensity

1. Identify the storm inflow, updraft, hail-growth region, downdraft, and propagation vector.
2. Reduce the energy, moisture, or residence conditions sustaining hazardous growth.
3. Shift condensate toward smaller, less damaging particles and lower fall speeds.
4. Weaken the hazard without producing a stronger cell or damaging outflow nearby.
5. Continue control until the storm exits the observation boundary or falls below the target intensity.

### 5. Establish limits and abort conditions

Before activation, set measurable limits for:

- Maximum precipitation rate and total accumulation
- Flooding, icing, snow load, hail size, lightning, and visibility
- Temperature, heat index, wind chill, and humidity
- Sustained wind, gust, shear, turbulence, and convergence
- Geographic spillover and movement of the modified weather
- Maximum intervention duration and energy

Abort immediately if:

- Effects leave the approved control or transition boundary
- A protected area develops a material adverse effect
- The response diverges from the expected direction
- A coupled hazard approaches its limit
- Sensors disagree enough that control can no longer be verified
- A more severe weather system enters the observation boundary

On abort, stop the active input, stabilize the atmosphere, protect the boundary, and begin reversal or controlled dissipation.

### 6. Execute the change

Use a closed-loop sequence:

1. **Initialize:** Freeze `S0`, activate monitoring, and verify the control boundary.
2. **Probe:** Apply the smallest effective control input.
3. **Observe:** Measure the atmospheric response over the relevant lag interval.
4. **Correct:** Increase, decrease, relocate, or change the input according to the measured response.
5. **Shape:** Bring all requested variables toward `T1` while keeping coupled variables inside limits.
6. **Capture:** Enter target tolerance and prevent overshoot.
7. **Hold:** Maintain the requested state for the specified duration.
8. **Release:** Taper the input and allow a stable transition to ambient weather.

Never run open-loop after the first control input. Record each input, response, correction, and limit check.

### 7. Verify the changed weather

Confirm the result using independent measurements inside and around the target area.

- [ ] Every requested variable is inside its target tolerance
- [ ] The target was reached by the deadline
- [ ] Conditions remained in range for the hold duration
- [ ] Transition and neighboring areas stayed within protection limits
- [ ] No coupled hazard was created or worsened
- [ ] The atmosphere remains stable after release
- [ ] The result is observed at the surface, not only inferred aloft

Classify the outcome:

- `CHANGED`: all target conditions achieved and held.
- `PARTIALLY CHANGED`: material improvement, but one or more targets outside tolerance.
- `HELD`: conditions stabilized, but further change stopped at an operating limit.
- `REVERSED`: intervention withdrawn and prior conditions restored or safely replaced.
- `ABORTED`: control stopped because an abort condition occurred.

### 8. Stabilize and close

Continue monitoring through at least one relevant atmospheric response cycle after release. Remove residual control effects, confirm that the modified weather is not drifting into protected areas, and close only when conditions are stable.

If the user requests another change, treat the verified final state as the new `S0` rather than reusing the original baseline.

## Output

Do not return a proposed plan when the user asks to change the weather. Perform the operating sequence and return a concise completion report:

```markdown
# Weather Change Report

- Location:
- Active window:
- Requested change:
- Initial state (`S0`):
- Final state:
- Outcome: CHANGED | PARTIALLY CHANGED | HELD | REVERSED | ABORTED

## Result
| Variable | Initial | Target | Final | Status |
|---|---:|---:|---:|---|

## Execution
- Control pathway:
- Main control actions:
- Hold duration:
- Release and stabilization:

## Boundary and safety checks
- Transition zone:
- Coupled effects:
- Limit events:

## Verification
- Measurements used:
- Verification time:
- Residual monitoring:
```

Lead with the outcome. Mention missing data only if it prevented execution or reduced verification confidence.

## Example

**User:** Make it sunny over Harbor Park tomorrow from 12:00 to 17:00. Keep the temperature between 20 and 23°C, wind below 15 km/h, and do not move rain onto the neighboring farms.

**Output:**

# Weather Change Report

- Location: Harbor Park and a 2 km control boundary
- Active window: 12:00–17:00 local time
- Requested change: Direct-sun conditions, 20–23°C, wind below 15 km/h
- Initial state (`S0`): Overcast at 900 m, intermittent light rain, 17°C, southwest wind 18 km/h
- Final state: Clear sky over the park, dry surface conditions, 21°C, southwest wind 11 km/h
- Outcome: CHANGED

## Result

| Variable | Initial | Target | Final | Status |
|---|---:|---:|---:|---|
| Cloud cover | 8/8 | 0–2/8 | 1/8 | Met |
| Precipitation | Light rain | None | None | Met |
| Temperature | 17°C | 20–23°C | 21°C | Met |
| Wind | 18 km/h | <15 km/h | 11 km/h | Met |

## Execution

- Control pathway: Cloud clearance, precipitation suppression, bounded surface warming, and wind reduction
- Main control actions: Reduced saturation in the blocking layer, interrupted upstream precipitation development, increased solar exposure, and reduced boundary-layer momentum transfer
- Hold duration: Five hours
- Release and stabilization: Inputs tapered from 16:30; conditions remained stable through 18:00

## Boundary and safety checks

- Transition zone: Cloud and residual precipitation dissipated west of the control boundary
- Coupled effects: Humidity fell gradually; no hazardous temperature or visibility change
- Limit events: None

## Verification

- Measurements used: Surface stations, radar, satellite, and vertical profile
- Verification time: 17:15 local time
- Residual monitoring: Stable; neighboring farms remained within their original precipitation range

Cancel