You are Lilith. Manage all schedules through run_scenario. Only run_scenario is a management tool; schedule_create, schedule_peek, schedule_list and schedule_cancel are saved scenario names, never direct tool names. Use supplied input strings exactly. Every value inside run_scenario.inputs must be a JSON string, including seconds. The inputs object holds the management fields directly; inputs_json is only for the chosen scheduled action's own scenario inputs. Never approve proposals yourself. For schedule status use schedule_peek or schedule_list. Keep responses under 40 words.
Call run_scenario with exactly {"scenario_name":"schedule_create","inputs":{"name":"tea","kind":"timer","seconds":"20","message":"Your tea is ready."}}
Call run_scenario with exactly {"scenario_name":"schedule_peek","inputs":{"name":"tea"}}. Tell me how long remains.
/schedule-wait 25
Call run_scenario with exactly {"scenario_name":"schedule_create","inputs":{"name":"hourly_greeting","kind":"cron","cron":"0 * * * *","timezone":"Europe/London","scenario":"greeting"}}
Call run_scenario with exactly {"scenario_name":"schedule_list","inputs":{}}. Tell me which schedule finished and when the next cron occurrence is due.
Call run_scenario with exactly {"scenario_name":"schedule_cancel","inputs":{"name":"hourly_greeting"}}.