Claude Windows

Steps

1. Resolve inputs

Parse the arguments for work hours (HH:MM-HH:MM) and optionally alpha (a number in (0,1)). For anything not supplied, fall back to the session environment, which the active profile's settings.json env block injects (so values are per profile, and each profile is a separate account):

• CLAUDE_WINDOWS_HOURS (e.g. 11:00-19:00)
• CLAUDE_WINDOWS_ALPHA (default 0.5; share of slack given to the morning window, higher = more morning)
• CLAUDE_WINDOWS_DAYS (default 1-5; cron day-of-week field for the routines)

If neither args nor env provide hours, ask for them. If args were passed and differ from the stored env value, treat the args as the new default; Step 5 persists them.

2. Compute the schedule

All arithmetic in minutes. W = 300 (the 5-hour window).

L     = end - start                       # workday length; must be > 0
k     = largest integer with (k-1)*W ` from the computed times and config. Cron runs in UTC: convert the local times, and warn in the report that a DST change in the user's timezone shifts the local firing times by an hour until the skill is re-run.
   - model: Haiku (cheapest; the reply is throwaway)
   - prompt: `Reply with the single word: ok. Do nothing else.`

### 5. Persist config and report

If hours or alpha came from args and differ from the stored env values, persist them to the active profile's settings file at `$CLAUDE_CONFIG_DIR/settings.json` (default `~/.claude/settings.json` when the variable is unset): Read the full file first, then edit ONLY the relevant keys inside the `env` block (creating the block if absent), preserving everything else byte for byte. This is a live harness file; the permission prompt on the edit is expected. If the user declines the edit, proceed without persisting and tell them which key to set manually. Note that env changes load at session start, so a bare `/claude-windows` picks up the new default from the next session onward.

Report: routines created/deleted, the session count, whether the default was persisted, and two standing caveats in one line each: the weekly cap is unaffected, and a message sent before the anchor ping shifts that day's boundaries (self-heals if sent more than 5h before the anchor).

## Critical

- Only routines prefixed `claude-windows-` may ever be deleted or replaced.
- No routine changes before the Step 3 approval.
- Cloud routines only; never `CronCreate`/local cron for this.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [gsarig](https://github.com/gsarig)
- **Source:** [gsarig/skills](https://github.com/gsarig/skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.