Dianel555Dianel555/DSkills/skills/time/SKILL.md

time

Skill65 starsChanged 2 months agoMITView on GitHub

Time and timezone utilities for getting current time and converting between timezones. Use when: (1) Getting current time in any timezone, (2) Converting time between different timezones, (3) Working with IANA timezone names, (4) Scheduling across timezones, (5) Time-sensitive operations. Triggers: "what time is it", "current time", "convert time", "timezone", "time in [city]".

Installs packages

3 other projects use a version of this.

Adopted by

Most recently taken up by

osick/ctx.skillstheir own version, first seen Oct 13, 2026
LilithLabs/liliththeir own version, first seen Jun 20, 2026
thaitype/skillstheir own version, first seen Mar 15, 2026

Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
thaitype/skills★ 13same name
LilithLabs/lilith★ 1same name
osick/ctx.skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- ace-toolSkill
- agent-wikiSkill
- capability-evolverSkill
- cc-agySkill
- cc-codexSkill
- codex-ccSkill
- context7Skill
- exaSkill
- github-trending-analyzerSkill
- grill-meSkill
- grok-searchSkill
- ledger-tasks-yyloSkill
- literature-searcherSkill
- ontolySkill
- plan-ledger-tasks-yyloSkill
- sequential-thinkSkill
- serenaSkill
- wiki-yyloSkill

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Run scripts/time_cli.py via Bash:
line 13
Very specific:
Call get_current_time with timezone parameter
line 59
Very specific:
Call convert_time with all parameters
line 65

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Time

Time and timezone conversion utilities. Standalone CLI only (no MCP dependency).

Execution Methods

Run scripts/time_cli.py via Bash:

# Prerequisites: pip install pytz (or use Python 3.9+ with zoneinfo)

# Get current time in a timezone
python scripts/time_cli.py get --timezone "Asia/Shanghai"
python scripts/time_cli.py get --timezone "America/New_York"
python scripts/time_cli.py get  # Uses system timezone

# Convert time between timezones
python scripts/time_cli.py convert \
  --time "16:30" \
  --from "America/New_York" \
  --to "Asia/Tokyo"

# List available timezones
python scripts/time_cli.py list [--filter "Asia"]

Tool Capability Matrix

Tool	Parameters	Output
`get_current_time`	`timezone` (required, IANA name)	`{timezone, datetime, is_dst}`
`convert_time`	`source_timezone`, `time` (HH:MM), `target_timezone`	`{source, target, time_difference}`

Common IANA Timezone Names

Region	Timezone
China	`Asia/Shanghai`
Japan	`Asia/Tokyo`
Korea	`Asia/Seoul`
US East	`America/New_York`
US West	`America/Los_Angeles`
UK	`Europe/London`
Germany	`Europe/Berlin`
France	`Europe/Paris`
Australia	`Australia/Sydney`
UTC	`UTC`

Workflow

Getting Current Time

Identify target timezone (use IANA name)
Call get_current_time with timezone parameter
Response includes ISO 8601 datetime and DST status

Converting Time

Identify source timezone and time (24-hour format HH:MM)
Identify target timezone
Call convert_time with all parameters
Response includes both times and time difference

Output Format

get_current_time Response

{
  "timezone": "Asia/Shanghai",
  "datetime": "2024-01-01T21:00:00+08:00",
  "is_dst": false
}

convert_time Response

{
  "source": {
    "timezone": "America/New_York",
    "datetime": "2024-01-01T16:30:00-05:00",
    "is_dst": false
  },
  "target": {
    "timezone": "Asia/Tokyo",
    "datetime": "2024-01-02T06:30:00+09:00",
    "is_dst": false
  },
  "time_difference": "+14.0h"
}

Error Handling

Error	Recovery
Invalid timezone	Check IANA timezone name spelling
Invalid time format	Use 24-hour format HH:MM
MCP unavailable	Fall back to CLI script

Anti-Patterns

Prohibited	Correct
Use city names directly	Use IANA timezone names (e.g., `Asia/Tokyo` not `Tokyo`)
Use 12-hour format	Use 24-hour format (e.g., `16:30` not `4:30 PM`)
Assume timezone	Always specify timezone explicitly

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