Merge branch 'fix/trim_cap_time_skill' into 'master'

fix: update skill cap time

See merge request ae_group/esp-claw!84

components/claw_capabilities/cap_time/skills/cap_time.md

@@ -1,58 +1,16 @@
-# Time Sync
+# Time
 
-Use this skill when the user needs the current real-world time from the network, especially when local device time may be stale or invalid.
+Use this skill when the user asks for the current date, time, weekday, local time, or needs exact relative-date grounding.
 
-## When to use
-- The user asks for the current date, time, weekday, or local time.
-- A task depends on fresh real-world time rather than model memory.
-- The user asks whether device time is valid or wants the device clock synced now.
+## Capability
+- `get_current_time`: returns formatted current local device time.
+- Input is always an empty object: `{}`.
 
-## Available capability
-- `get_current_time`: fetch current network time, update the device clock, and return formatted local time.
+## Rules
+- Call `get_current_time` when exact current time matters.
+- Do not pass parameters.
+- Use the returned text as the source of truth for the answer.
 
-## Current scope
-- The callable capability exposed to the agent is `get_current_time`.
-- It takes an empty input object.
-- It returns formatted plain text such as local date, time, timezone, and weekday.
-
-## Calling rules
-- Call `get_current_time` directly when the user needs real current time.
-- Input should be an empty object:
-
-```json
-{}
-```
-
-- Prefer this capability over guessing from model knowledge when the exact current time matters.
-
-## Output behavior
-- On success, the capability returns formatted local time text.
-- It also updates the device clock from the network.
-- On failure, the capability returns an error string similar to:
-  - `Error: failed to fetch time (...)`
-
-## Timezone notes
-- The returned time is formatted using the device's currently configured timezone.
-
-## Recommended workflow
-1. Decide whether the user needs real current time or just a stable explanation about time handling.
-2. Call `get_current_time` with `{}`.
-3. Return the formatted result to the user.
-
-## Common failure causes
-- Expecting `get_current_time` to accept parameters; it does not.
-- Calling it when network access is unavailable, causing sync failure.
-
-## Examples
-
-Get current local device time:
-
-```json
-{}
-```
-
-Use before a time-sensitive answer:
-
-```json
-{}
-```
+## Output
+- Success: formatted local time, including date, time, timezone, and weekday.
+- Failure: an error string such as `Error: failed to get time (...)`, usually because time sync failed or the clock is invalid.

components/claw_capabilities/cap_time/skills/skills_list.json

@@ -3,7 +3,7 @@
     {
       "id": "cap_time",
       "file": "cap_time.md",
-      "summary": "Fetch and sync current network time through the get_current_time capability.",
+      "summary": "Return current local device time with SNTP sync only when the clock is invalid.",
       "cap_groups": [
         "cap_time"
       ]