Enforces correct local-time awareness. Prevents the classic UTC-as-local mistake.
Timezone: field)now.py script for accurate local time outputtimezone_setup.py for one-time configuration--patch-agents and confirms. This is not default behavior.⚠️ User Warning: Running timezone_setup.py --patch-agents will write standing instructions into AGENTS.md. This persists across sessions and affects all future agent behavior. Only do this if you want the timezone rule to apply permanently.
now.py explicitly--patch-agents flagtimezone_setup.py if timezone changesThis skill may:
skills/timezone/tz_config.json (to save config)--patch-agents)timedatectl or read /etc/localtime (system timezone detection only)USER.md should contain a timezone field:
text
Timezone: America/New_York
Use a valid IANA timezone string (e.g. America/New_York, Europe/London, Asia/Tokyo).
Aliases like ET, PT, CT are also accepted.
bash
python3 skills/timezone/scripts/timezone_setup.py
This detects timezone from USER.md or system, writes tz_config.json. Does NOT touch AGENTS.md unless user runs with --patch-agents.
To also patch AGENTS.md (optional, requires user confirmation):
bash
python3 skills/timezone/scripts/timezone_setup.py --patch-agents
Always run now.py before reporting any time — never guess from internal knowledge:
bash
python3 skills/timezone/scripts/now.py
Report output verbatim. If it fails: tell the user, ask them to run timezone_setup.py first.
Before outputting any time, ask: is this UTC or local?
Z, +00:00, or +0000 → convert before reportingWhen user types /timezone:
now.py)timezone_setup.py --set "<IANA_NAME>"Custom implementations and questions: pods@agentmail.to