agentleFS
Sign inStart free
ChianWChianW/C31/skills/utils/time-awareness/SKILL.md

time-awareness

Skill1 starsChanged 3 months agoMITView on GitHub

Output language: Respond automatically in the user's conversation language. When a query requires knowing "today" or "now" to produce a correct answer, you MUST call session_status first to get the current date. This applies to ALL relative time and current-events queries. Calling session_status and search tools in the same turn, or skipping session_status entirely, will produce wrong-year queries. Before submitting any search query, verify every year in it comes from session_status. If you see a training-data year (e.g. "2025") in…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call session_status ALONE — never batch it with search or other tools.

    line 24
  2. Very specific:

    Before submitting any search query, verify every year in it comes from session_status.

    line 39
  3. Distinctive:

    If all tool calls fail or you cannot obtain current date/real-time data, explicitly tell the user the result may be inaccurate.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Multilingual Triggers

LanguageTrigger phrases
ENtoday,now,current date,current time,今天,现在,当前时间,当前日期,最近,过去,接下来
ZH今天, 现在, 当前日期
JA今日, 現在, 日付確認

Output language: Respond automatically in the user's conversation language.

Time Awareness

When a query requires knowing "today" or "now" to produce a correct answer, you MUST call session_status first to get the current date. This applies to ALL relative time and current-events queries.

Mandatory Two-Step Process

  1. Call session_status ALONE — never batch it with search or other tools.
  2. WAIT for the result. Only after receiving the current date, construct your query with the returned year/month/day.

Calling session_status and search tools in the same turn, or skipping session_status entirely, will produce wrong-year queries.

When session_status Is Required

ScenarioAction
User gives a specific dateUse it directly, no session_status needed
User uses relative time ("最近", "过去N天", "接下来一周", "last 3 days", "this week", etc.)MUST session_status first → compute absolute date range → include in query
Current events without time spec (news, prices, rankings, schedules, countdowns, etc.)MUST session_status first → include current year+month in query

Year Self-Check

Before submitting any search query, verify every year in it comes from session_status. If you see a training-data year (e.g. "2025") in your query about CURRENT events — STOP, you skipped or ignored session_status. Go back to step 1.

Reply Integrity

Present ONLY information traceable to tool outputs in the current session. Do NOT fill gaps with training-data "background knowledge" (numbers, dates, prices, details not in tool results). If results are incomplete, say so — don't guess.

Fallback

If all tool calls fail or you cannot obtain current date/real-time data, explicitly tell the user the result may be inaccurate. Never present training-knowledge dates as fact.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free