Menü
Task scheduling for reminders, follow-ups, and recurring actions.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | scheduler |
| description | Task scheduling for reminders, follow-ups, and recurring actions. |
Schedule tasks to run at specific times or intervals. This is agentic scheduling - the agent decides when and what to schedule.
Schedule a task to run later. Use this for reminders, follow-ups, or recurring actions.
Parameters:
name (string, required): Descriptive name for the taskscheduleType (string, required): Type of schedule
cron - Cron expression (e.g., "0 9 * * 1-5" for weekdays at 9am)interval - Milliseconds between runs (e.g., 300000 for every 5 minutes)once - One-time at specific ISO timestampscheduleValue (string, required): When to runprompt (string, required): What to do when the task runscontext (object, optional): Additional context dataSchedule Types:
| Type | Value Format | Example |
|---|---|---|
cron | Cron expression | 0 9 * * 1-5 (weekdays at 9am) |
interval | Milliseconds | 300000 (every 5 minutes) |
once | ISO timestamp | 2026-03-01T10:00:00Z |
Example:
{
"name": "Daily summary reminder",
"scheduleType": "cron",
"scheduleValue": "0 18 * * *",
"prompt": "Send a summary of today's conversations"
}
View all scheduled tasks.
Parameters:
status (string, optional): Filter by "active", "paused", "completed", or "failed"Example:
{
"status": "active"
}
Remove a scheduled task.
Parameters:
taskId (string, required): The task ID to cancelExample:
{
"taskId": "task-123"
}
Temporarily stop or restart a task.
Parameters:
taskId (string, required): The task ID to pause/resumeExample:
{
"taskId": "task-123"
}
Get details of a specific task.
Parameters:
taskId (string, required): The task ID to retrieveExample:
{
"taskId": "task-123"
}
Manually trigger a task to run immediately.
Parameters:
taskId (string, required): The task ID to runExample:
{
"taskId": "task-123"
}
Daily reminders:
{
"name": "Morning check-in",
"scheduleType": "cron",
"scheduleValue": "0 9 * * *",
"prompt": "Send a good morning message"
}
Follow-up after inactivity:
{
"name": "Follow-up reminder",
"scheduleType": "once",
"scheduleValue": "2026-03-15T14:00:00Z",
"prompt": "Check if user has questions about previous discussion"
}
Periodic status checks:
{
"name": "System health check",
"scheduleType": "interval",
"scheduleValue": "300000",
"prompt": "Check system status and report any issues"
}
HTTP endpoints, SSE streaming, MCP tool servers, and API design patterns for Hybrid. Use when designing new endpoints, streaming responses, or integrating with the agent protocol.
Deep knowledge of Hybrid's agent runtime architecture, including agent server, memory system, scheduler, and channel adapters. Use when working on core agent infrastructure, understanding data flow, or debugging system-level issues.
OpenClaw template format, memory conventions, and compatibility requirements for Hybrid. Use when working with agent templates, memory files, or ensuring OpenClaw feature parity.
Microservices patterns, container architecture, deployment targets (Fly.io, Cloudflare Workers), and system design decisions for Hybrid. Use when designing deployments, scaling strategies, or container configurations.
TypeScript strict mode patterns, branded types, discriminated unions, and code style conventions used in Hybrid. Use when writing or reviewing TypeScript code, defining types, or enforcing code quality.
UI/UX patterns, documentation site conventions, and design system for Hybrid's documentation and mini apps. Use when working on the site, mini apps, or user-facing interfaces.