always-current-date

Acquire a fresh local-time anchor for each direct user turn.

Updated Jul 20, 2026

Search Tags:#recovery #time #date #timezone #clock #prefix #temporal reasoning

Ready to run

npx skills add https://github.com/srinitude/skills --skill always-current-date

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: always-current-date
Source: https://github.com/srinitude/skills/tree/main/skills/always-current-date
Command: npx skills add https://github.com/srinitude/skills --skill always-current-date

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It prevents stale or guessed dates in assistant replies by refreshing a local time anchor for each direct user turn.

Core Features & Use Cases

Fresh per-turn clocking: Captures one new local-time anchor before interpreting a direct user message.
Temporal resolution: Converts relative phrases like tomorrow, yesterday, and next Friday into actionable absolute dates when needed.
Failure-safe behavior: Blocks date-dependent work when the clock is missing, invalid, or stale, and uses a stable failure marker instead of guessing.
Recovery and resume support: Reloads after compaction or resume, reacquires after midnight, and preserves historical evidence separately from current state.

Quick Start

Use the always-current-date skill to answer the user’s message with a freshly acquired date anchor and the correct visible date prefix.

Frequently Asked Questions about always-current-date

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent stale date responses in temporal conversations?▼

To prevent stale date responses, acquire a fresh local time anchor before interpreting each direct user turn. This mechanism ensures replies rely on current observations rather than historical evidence, keeping temporal conversations accurate and anchored to today.

How does a local time anchor handle relative date calculations?▼

A local time anchor handles relative date calculations by capturing one new local time marker per turn. This stable reference point converts relative phrases like tomorrow or next Friday into actionable absolute dates when needed for tool-ready calculations.

What happens to date-dependent work if the clock is missing or invalid?▼

If the clock is missing or invalid, date-dependent work is blocked using fail-closed error handling. The system uses a stable failure marker instead of guessing, preventing inaccurate temporal reasoning when the clock state is stale.

Can I recover temporal reasoning state after a session compaction or resume?▼

Yes, you can recover temporal reasoning state because the system reloads after compaction or resume. It reacquires the clock after midnight and preserves historical evidence separately from current state to maintain accurate recovery.

Does timezone precedence affect how the current date is acquired?▼

Yes, timezone precedence affects date acquisition by enforcing strict timezone rules during the relative clock call. This ensures the visible date prefix and local time anchor reflect the correct regional time before generating a response.