uguratadargun/office/temporal

/temporal — concrete date ranges, relative to now

This is the single source of truth for "what dates does <window> mean right now?". It resolves named windows to concrete ISO date ranges relative to your run time (new Date() at the moment you invoke it), so you never re-derive dates manually. It only reads the clock and prints — no files written, no network.

Run it

# all windows at once (a quick temporal-context dump)
node "$AGENT_DIR/.claude/skills/temporal/when.mjs"
 
# one or several specific windows
node "$AGENT_DIR/.claude/skills/temporal/when.mjs" last30Days thisQuarter
 
# JSON only (machine-readable), or list the supported keywords
node "$AGENT_DIR/.claude/skills/temporal/when.mjs" --json last7Days
node "$AGENT_DIR/.claude/skills/temporal/when.mjs" --list

If $AGENT_DIR is somehow unset, the script also lives under ~/.claude/skills/temporal/when.mjs.

Windows

Aliases: ytd, qtd, mtd, wtd, 7d, 30d, 90d, 12m.

Convention: this* windows are period-start → today (to-date); last* named periods are the full prior complete period.

Output

Each window prints a human line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same span as a half-open [start, end)

range of exact UTC instants, ideal for timestamp / createdAt-style queries

• days, inclusive, timezone, tzOffsetMinutes, asOf — span, tz, and the

instant the range was resolved

Use the returned dates as the time bounds for the task. The named shortcuts /today, /yesterday, /last30Days, /lastQuarter, … each call this same resolver for their one window.