ghost/clock

Samsung Clock timer start/cancel/state and the Google Clock alarm/world-city/stopwatch toolkit. Timer app is auto-detected; Samsung actions never open alarms.

Draft 4.1× fewer tokens Score 20/100 Official hard skill python

Before / after

Benchmark details ↓
Tokens saved1,029,086Paired medians · 1/1 tasks · N=5
UI actions saved13Paired medians · 1/1 tasks · N=5
Pass · before → with skill4/5 → 5/5Current arms · failures included

Before With skill · median tokens per task

Clock: alarm 7:30 "Gym" Clock: alarm 7:30 "Gym". Median tokens: before 1,113,113, with skill 84,163. N=5 before / 5 with skill. 1,113,11384,163 −92% tokensN=5/5 N=5 before / 5 with skill
Before 4/5 · Wilson 95% CI 0.376–0.964; with skill 5/5 · Wilson 95% CI 0.566–1.000

6 more actions not benchmarked yet

maintainer-run, not independent · claude-haiku-5-5 · 2026-10-22. Every failure is counted (intention-to-treat).

Demo: set_alarm · HOME → launch → action

Control Samsung and Google Clock on Android with an AI agent

Start, cancel and inspect Samsung timers; use the existing Google Clock alarm, timer, stopwatch and world-city toolkit. Timer actions detect the installed app. No account is needed.

Try asking: Start a one-minute Samsung timer, then cancel it and check that it stopped.

Toolkit

ActionAppWhat it doesParams
start_timerSamsung or GoogleStart and validate the requested durationseconds, app=auto/google/samsung, label (Google only)
cancel_timerSamsungCancel the active timer; no-op if none activeapp=auto/samsung
get_timer_stateSamsungReturn active=true/false, including paused timersapp=auto/samsung
set_alarmGoogle onlyCreate and validate an alarmhour, minute, label
list_alarmsGoogle onlyRead alarm time, label, repeat and enabled statenone
start_stopwatchGoogle onlyStart and validate the stopwatchnone
add_world_cityGoogle onlyAdd and validate a world-clock citycity

Samsung timer behavior

Auto selection prefers installed Samsung Clock, then Google Clock; app=google forces Google when installed. A missing requested app fails explicitly. Samsung uses only Timer and never opens its Alarm tab. An existing active Samsung timer is preserved: start_timer refuses to replace it. Its duration is set through the identified number pickers, reread before Start, and validated with the active timer service plus Pause control. It does not create named timer presets. Custom Samsung labels are unsupported and fail before starting; omit label or use the default Timer.

Cancellation requires the currently visible Samsung cancellation control and verifies the timer notification service stopped. SHOW_TIMERS opens an add-timer picker while another timer is active, so cancellation does not navigate away from the countdown. get_timer_state reports whether a timer is active, including paused timers; it does not claim remaining time. No alarm definitions are deleted.

The bundled app-scoped snapshot reads visible Clock nodes without an idle wait. Normal uiautomator dump can stall during an animated countdown. Snapshot failure fails closed; no root, network or installed helper APK is required for Samsung timer actions.

Use

ghost skill run ghost/clock start_timer --param seconds=60 --param app=samsung
ghost skill run ghost/clock cancel_timer --param app=samsung
ghost skill run ghost/clock get_timer_state --param app=samsung

Use a device returned by list_devices or configure GHOST_DEVICE. From MCP, call find_skill, then run_skill with the selected device. Google-only actions retain their existing Google Clock targets.

Verification scope

The current primary fingerprint targets Samsung Clock >=12, Android >=13, with Google Clock declared as a companion. Samsung SM-A156B verification uses the Timer page on Samsung SM-A156B, Android 16, Samsung Clock 12.5.60.29, English UI. Three clean-reset start/cancel/state cycles passed; paused-timer state was also checked. See current signed runs for measured outcomes. Existing Google evidence below belongs to its recorded skill versions; no new Google physical-device run is claimed. Demos must cancel their owned timer and restore the original picker afterward.

Known failure modes and versions tested

Versions tested

App versionAndroidDeviceSkill versionSigned self-runs (pass/total)Dates
7.414Google/sdk_gphone64_x86_64 (emulator, 1080x2400, 420 dpi, en-US)1.0.0, 1.0.116/172026-10-05

Android 13 was additionally replayed on Samsung SM-A037F (720x1600, 300 dpi, en-GB) and an emulator (1080x2400, 420 dpi, en-US). See the cross-device report for measured outcomes and limitations; other profiles remain unverified.

Stale or noncanonical artifacts are pruned from runs/. Current Samsung timer self-runs cover start_timer, cancel_timer and get_timer_state. Google-only set_alarm, list_alarms, start_stopwatch and add_world_city are unverified on the current build; no Google Clock install or alarm interaction is performed on the Samsung test device.

Recorded failures

  • 2026-10-05, v1.0.0, set_alarm: ValidatorFailedError; validator ran before the new alarm card rendered, and freshly added cards report a content-desc without the time; fixed in 1.0.1 (validator scrolls and matches cards by containment).

Popups and first-run screens handled

  • None app-specific; Android permission dialogs go through the engine's OS popup layer.

Other known failure modes

  • Clock navigation and visible-state reads use the bundled read-only accessibility snapshot, including when expired timers keep background accessibility events active. Unavailable snapshots fail closed; no root or extra APK is needed for this fallback.
  • 12 h vs 24 h display depends on the device setting; helpers accept both.
  • A city already on the list is not duplicated; the action still succeeds.

Historical Google compatibility through 1.0.2

The manifest targets Android >=13 and Google Clock >=7.4, with en-US and en-GB flows. The authoring screen remains 1080x2400 at 420 dpi; alarm cards and scrolling now use measured bounds for narrower screens too. Alarm validation rereads time, label and the enabled switch. list_alarms rewinds and rereads rows, including count. Root-readable Clock preferences remain authoritative for timer state, label/original duration and sw_state=1. When preferences are unreadable, the app-scoped snapshot requires a matching timer card with a decreasing countdown near the requested duration, or an increasing stopwatch with Pause exposed. Off-screen pager nodes are excluded. World-city validation rereads the city list. See snapshot source and offline build and current signed runs for exercised devices.

  • Intent creation still depends on Google Clock selectors during verification; slow rendering or a changed UI can fail. The nat2 before-arm failure set no alarm within the agent turn budget; it is not evidence of an independent skill validator check.
  • Alarm collection has a six-scan limit; a larger list may be incomplete.

Adding an already-visible city leaves it selected. After a new selection, the helper restores the city tab in case an expiring timer interrupted navigation, then independently checks the saved city list.

Version1.0.4 only taps Samsung timer_cancel_button when a timer_pause_button or timer_resume_button establishes the Timer screen. Generic alarm Cancel/Dismiss/Stop controls are never tapped. Samsung remains the evidence target; the Google-primary/multi-app fingerprint concern requires a separate Google-device replay and is not claimed fixed here. Picker replay coverage uses a one-minute timer; large durations remain unverified and can require many taps.

Samsung picker startup and readback

Cold phone-B launch takes with version 1.0.4 failed the one-minute duration check before any timer started. Version 1.0.5 waits for two equal native picker snapshots before input, then observes each exact wheel step with a bounded wait. Missing numeric input text requires the native Timer picker's hour/minute/second description; conflicting or unavailable values fail closed. It never repeats a tap blindly or presses Start without the requested duration. The Google-only actions remain unverified on phone B.

Try a sample prompt or run an action by name. Replace any parameters in braces with your own values.

set_alarm

Play demo

Try asking

  • Set an alarm for 7:30 tomorrow morning called Gym
  • wake me up at 6:45
  • create an alarm at 22:00 labelled Meds
  • set a 7am alarm
ghost skill run ghost/clock set_alarm

list_alarms

Play demo

Try asking

  • What alarms do I have set?
  • list my alarms
  • when is my next alarm
  • show all alarms on the clock app
ghost skill run ghost/clock list_alarms

start_timer

Play demo

Try asking

  • Start a 5 minute timer for tea
  • set a timer for 10 minutes
  • countdown 90 seconds labelled pasta
  • start a 30 second timer
ghost skill run ghost/clock start_timer

start_stopwatch

Play demo

Try asking

  • Start the stopwatch
  • start timing
  • run the stopwatch
  • begin a stopwatch
ghost skill run ghost/clock start_stopwatch

add_world_city

Play demo

Try asking

  • Add Tokyo to my world clock
  • show the time in New York on my clock
  • add London to world clock
  • track Sydney time
ghost skill run ghost/clock add_world_city

cancel_timer

Play demo

Try asking

  • Cancel my Samsung timer
  • stop the Samsung countdown
  • cancel the Galaxy timer
ghost skill run ghost/clock cancel_timer

get_timer_state

Play demo

Try asking

  • Is a Samsung timer active?
  • check my Galaxy countdown state
  • did the Samsung timer stop?
ghost skill run ghost/clock get_timer_state
Benchmark details

Ghost-native before/after

maintainer-run, not independent
Model: claude-haiku-5-5 · Date: 2026-10-22

Same task across three arms. Skill replay runs without a model. Medians include every valid episode, including failures.

Clock: alarm 7:30 "Gym"

N=5 seeds · 2026-10-22

Arm / provenancePass a/b · Wilson 95% CITokens, median [q1–q3]LLM calls, medianUI actions, medianWall, median
Agent aloneclaude-haiku-5-5 · 2026-10-22
Skill 1.0.1 · SHA b37d4c36
4/5 · Wilson 95% CI 0.376–0.9641,113,113[1,010,774–1,417,012]20141.9 min
Skill replayno model · 2026-10-22
Skill 1.0.1 · SHA b37d4c36
5/5 · Wilson 95% CI 0.566–1.0000[0–0]0622 s
Agent + skillclaude-haiku-5-5 · 2026-10-22
Skill 1.0.1 · SHA b37d4c36
5/5 · Wilson 95% CI 0.566–1.00084,163[84,027–84,954]4145 s

Agent + skill vs agent alone: 5 paired seeds; 1 fail → pass, 0 pass → fail; McNemar exact p = 1. Median tokens saved: 1,029,086.

Skill replay vs agent alone: 5 paired seeds; 1 fail → pass, 0 pass → fail; McNemar exact p = 1. Median tokens saved: 1,113,113.

Failed episodes

  • Clock: alarm 7:30 "Gym" · Agent alone · seed 3 · claude-haiku-5-5
Episodes (15)
TaskArmSeedModelPassLLM callsTokensUI actionsWallTrace
Clock: alarm 7:30 "Gym"Agent + skill0claude-haiku-5-52026-10-22 · Skill 1.0.1 · SHA b37d4c36pass485k171 s
Clock: alarm 7:30 "Gym"Skill replay0replay2026-10-22 · Skill 1.0.1 · SHA b37d4c36pass00622 s
Clock: alarm 7:30 "Gym"Agent alone0claude-haiku-5-52026-10-22 · Skill 1.0.1 · SHA b37d4c36pass201.01M142.0 min
Clock: alarm 7:30 "Gym"Agent + skill1claude-haiku-5-52026-10-22 · Skill 1.0.1 · SHA b37d4c36pass484k145 s
Clock: alarm 7:30 "Gym"Skill replay1replay2026-10-22 · Skill 1.0.1 · SHA b37d4c36pass00621 s
Clock: alarm 7:30 "Gym"Agent alone1claude-haiku-5-52026-10-22 · Skill 1.0.1 · SHA b37d4c36pass13535k1174 s
Clock: alarm 7:30 "Gym"Agent + skill2claude-haiku-5-52026-10-22 · Skill 1.0.1 · SHA b37d4c36pass5167k162 s
Clock: alarm 7:30 "Gym"Skill replay2replay2026-10-22 · Skill 1.0.1 · SHA b37d4c36pass00622 s
Clock: alarm 7:30 "Gym"Agent alone2claude-haiku-5-52026-10-22 · Skill 1.0.1 · SHA b37d4c36pass252.00M141.9 min
Clock: alarm 7:30 "Gym"Agent + skill3claude-haiku-5-52026-10-22 · Skill 1.0.1 · SHA b37d4c36pass484k144 s
Clock: alarm 7:30 "Gym"Skill replay3replay2026-10-22 · Skill 1.0.1 · SHA b37d4c36pass00621 s
Clock: alarm 7:30 "Gym"Agent alone3claude-haiku-5-52026-10-22 · Skill 1.0.1 · SHA b37d4c36fail251.42M322.0 min
Clock: alarm 7:30 "Gym"Agent + skill4claude-haiku-5-52026-10-22 · Skill 1.0.1 · SHA b37d4c36pass484k144 s
Clock: alarm 7:30 "Gym"Skill replay4replay2026-10-22 · Skill 1.0.1 · SHA b37d4c36pass00623 s
Clock: alarm 7:30 "Gym"Agent alone4claude-haiku-5-52026-10-22 · Skill 1.0.1 · SHA b37d4c36pass171.11M141.9 min

Display only: points come from signed run artifacts.