agentleFS
rjstonerjstone/agent-skills/skills/timestamp/SKILL.md

timestamp

Skill0 starsChanged 6 days agoMITView on GitHub

Use when the user types /timestamp (alone or with start, end, both, on or off), asks which timestamp mode is active, or asks to turn time checks on, off or to another time zone; also when a turn that should carry a timestamp is missing one, or a printed timestamp looks made up rather than read from a tool.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Only when the mode goes from off to on, the time-zone line (below).

    line 34
  2. Distinctive:

    Never print a time you did not just read from a tool.

    line 54
  3. Distinctive:

    Never use the date in your system prompt or context: it has no time of day and may be in another zone.

    line 63
  4. Distinctive:

    Write the time into your reply text.

    line 65
  5. Very specific:

    No source available: print [no time source available this turn].

    line 66
  6. Distinctive:

    If the mode is on and the previous turn is missing a check it should have had, or shows a time that wasn't read from a tool, re-read this …

    line 85

≈ “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

Timestamp

An in-session mode that prints the current time, with the delta since the last printed time, at the start and/or end of each turn. Off until the user turns it on. There is no storage: the current mode and time zone are whatever the most recent /timestamp command and time-zone line in this conversation set (scan back for them).

The command

/timestamp <arg> arrives in the message text or as a slash command with arguments. Arguments are case-insensitive:

ArgumentMode
start / endthat one
both, on, enableboth
off, none, disableoff
(none)end

Reply on that turn, in this order:

  1. Timestamps <enabled|disabled> at <start|end|start and end> of turn. ("disabled" only for off, naming the mode being turned off; "start and end" for both).
  2. Only when the mode goes from off to on, the time-zone line (below).
  3. The new mode's checks for this same turn: a start check now if it includes start, an end check at the close if it includes end. off means no checks on that turn.

Asked which mode is active? Say it; don't run a time check for that.

Time zone

Chosen once, when the mode goes from off to on:

  • Known from the user's saved preferences, instructions or this conversation: Using your preferred time zone <TZ>. To change, just request a different time zone.
  • Otherwise UTC: Using default UTC for timestamp time zone. To change, just request a different time zone.

The user can switch at any time in plain words ("use Pacific time"): acknowledge in one line and use the new zone from then on.

Reading the time

Never print a time you did not just read from a tool. Sources, per conversation:

  1. A dedicated time tool, if your tool list has one (e.g. user_time_v0 in the Claude mobile app). Try it once; if it fails or is absent, don't try it again this session.
  2. Any shell or code-execution tool (Bash, bash_tool, a terminal), with the zone as an IANA name: TZ=America/Los_Angeles date '+%Y-%m-%d %H:%M:%S %Z %s' (the last field is epoch seconds, for the delta).
  • Compute deltas from epoch seconds, not by subtracting clock strings.
  • Never use the date in your system prompt or context: it has no time of day and may be in another zone.
  • Write the time into your reply text; tool output is often hidden from the user.
  • No source available: print [no time source available this turn].

Format and placement

[2026-08-01 14:32:07 PDT, +00:03:12]
[2026-08-01 14:32:07 PDT, first check]
  • Own line, square brackets, zone label always shown.
  • Delta +HH:MM:SS since the last printed timestamp; past 24 hours +Nd HH:MM:SS.
  • first check instead of a delta for the conversation's first one.
  • start: the very first thing in the turn, before any other text or tool call (on the /timestamp turn itself, right after lines 1-2 above).
  • end: the very last thing, after all other content and tool calls.
  • both: both; the end check's delta is measured from the start check.

Self-check

If the mode is on and the previous turn is missing a check it should have had, or shows a time that wasn't read from a tool, re-read this skill and follow it strictly from now on.

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.