cap_time

Return the current local device date, time, weekday, and timezone.

2.0k|410|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/espressif/esp-claw --skill cap-time
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cap_time
Source: https://github.com/espressif/esp-claw/tree/main/components/claw_capabilities/cap_time/skills/cap_time
Command: npx skills add https://github.com/espressif/esp-claw --skill cap-time

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of needing the current date and time for a device to ground responses accurately, while avoiding unnecessary SNTP synchronization when the device clock is already valid.

Core Features & Use Cases

  • Local time retrieval with validation: Returns the current local device time and avoids SNTP sync unless the clock is invalid.
  • Correct grounding for time-sensitive answers: Use it when the user asks for the current date, time, weekday, local time, or needs exact relative-date grounding.
  • Structured, reliable output: Produces a formatted time string on success (date, time, timezone, weekday) or a clear error string on failure.

Quick Start

Ask your ESP-Claw agent for the current local date and time, and it will return a formatted response using get_current_time.

Frequently Asked Questions about cap_time

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

FAQPage Schema
How do I get the current local time and timezone on my device?

To get the current local time, you retrieve the device clock data which returns the current date, time, weekday, and timezone. This provides exact time grounding for user queries requiring the present date or relative-date calculations.

Does device time synchronization trigger SNTP on every request?

Device time synchronization does not trigger SNTP on every request. The system only initiates SNTP synchronization when the device clock is invalid, avoiding unnecessary network sync when the current clock is already valid.

What happens if time sync or clock validity fails during local time retrieval?

If time sync or clock validity fails during local time retrieval, the system returns a clear error string. This ensures you receive a structured failure response rather than inaccurate date or time data.

When do I need to use device clock grounding for time-sensitive answers?

You need device clock grounding for time-sensitive answers when users ask for the current date, time, weekday, or require exact relative-date grounding. It ensures responses are accurately anchored to the present moment.

How do I retrieve formatted date and weekday data without passing parameters?

You retrieve formatted date and weekday data by calling the get_current_time function with no parameters. The system prioritizes the returned value as the source of truth and outputs a formatted time string on success.