cap_scheduler

Manage IoT device scheduler rules for timed event publications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you inspect and manage timer-based schedule rules so your device can publish the right trigger events at the right times instead of relying on manual timing.

Core Features & Use Cases

  • Schedule lifecycle management: list, get, add, update, remove, enable/disable, pause/resume, trigger now, and reload scheduler definitions.
  • Multiple timing modes: one-time execution, periodic interval execution, and cron-like wall-clock execution.
  • Event publishing for downstream actions: schedules only publish events; router and post-trigger behavior are configured elsewhere.
  • Use case: set up a periodic “health check” or a one-time “bootstrap” wake-up so the agent loop runs automatically at scheduled times.

Quick Start

Ask to list current schedules, then add a new interval schedule with a unique id and the desired event payload.

Frequently Asked Questions about cap_scheduler

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

FAQPage Schema
How do I schedule IoT device events using cron and interval triggers?

The scheduler manages timed event publications by enforcing a schedule_json string with kind-specific fields, allowing you to list, add, update, and control schedules for downstream IoT automation actions.

Can I trigger a scheduled IoT event immediately instead of waiting for the timer?

This immediate triggering capability works alongside the standard schedule lifecycle management, allowing you to test event payloads or force execution while retaining the original schedule configuration.

Does the scheduler handle the downstream actions after an event is published?

This separation means you manage timing rules here, but the actual device behavior and agent loop execution triggered by those events are configured in separate routing components.

How do I set up a periodic health check or agent wake-up timer?

This supports automated agent loop execution by publishing events that trigger bootstrap wake-ups or periodic checks, eliminating the need for manual timing interventions.

What format does the schedule configuration need to be in?

This JSON string format enforces required input validation to ensure the scheduler can correctly parse and execute your timed event publication rules without configuration errors.

Why should I use a dedicated scheduler instead of manual timing for IoT automation?

It provides full lifecycle management including enable/disable, pause/resume, and reload capabilities, giving you precise control over event publishing that manual timing cannot match.