Skip to content
TrustedSkillsbeta
Back to all skills

Timezone Tools

Checked
henkisdabro·vlatest·utilities

Converts times between timezones effortlessly, ensuring accurate scheduling and communication across global teams.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add henkisdabro/wookstar-claude-plugins --skill timezone-tools -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

henkisdabro

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned henkisdabro/wookstar-claude-plugins at d8b9c1fcef.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
6 files, 381 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to convert between time zones, determine the current time in a specific location, and calculate time differences. It can handle various formats for specifying locations, including city names and IATA codes. The tool aims to provide accurate and reliable timezone information for scheduling and coordination purposes.

When to use it

  • Schedule a meeting with someone in London: "What time is 3 PM EST in London?"
  • Determine the current time in Tokyo: "What's the current time in Tokyo?"
  • Calculate the time difference between New York and Los Angeles: “What’s the difference between New York and Los Angeles?”
  • Plan a trip across multiple time zones: "I need to leave San Francisco at 8 AM PST, what time will that be when I arrive in Sydney?"

Key capabilities

  • Time zone conversion
  • Current time lookup by location
  • Time difference calculation
  • Support for city names and IATA codes

Example prompts

  • "Convert 10:00 AM EST to GMT."
  • "What is the current time in Paris?"
  • "Calculate the time difference between Chicago and Rome."

Tips & gotchas

The skill relies on accurate location data, so ambiguous city names might return unexpected results. Be as specific as possible when specifying locations (e.g., "London, UK" instead of just "London").