qclaw-cron-skill

Create cron-based reminders and scheduled message delivery jobs.

Updated May 4, 2026
One-click install
npx skills add https://github.com/234194027-cpu/xianclaw --skill qclaw-cron-skill-234194027-cpu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qclaw-cron-skill
Source: https://github.com/234194027-cpu/xianclaw/tree/main/resources/openclaw/config/skills/qclaw-cron-skill
Command: npx skills add https://github.com/234194027-cpu/xianclaw --skill qclaw-cron-skill-234194027-cpu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of setting accurate reminders, one-off alerts, and recurring scheduled tasks without guessing time-zone handling or delivery parameters.

Core Features & Use Cases

  • Cron, interval, and specific-time scheduling: Supports one-time at-times (including “X minutes later”) and recurring schedules (every N minutes/hours, daily, weekly, weekdays).
  • Correct delivery routing to internal vs external channels: Ensures the scheduled job is created using the proper delivery target, including mandatory lookup rules for external channels.
  • Guardrails against invalid scheduling: Enforces timezone computation via date +%z, requires agentId, and prevents creating external-channel delivery jobs without a valid to target.

Use case: You want to remind your teammate every weekday at 6 PM to submit their status update, or send a one-time alert 10 minutes from now with a custom message.

Quick Start

Tell your assistant: “Create a recurring reminder every weekday at 6 PM for my status update: {content}.”

Frequently Asked Questions about qclaw-cron-skill

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

FAQPage Schema
How do I schedule recurring reminders using cron intervals?

Scheduling recurring reminders with cron intervals requires providing an agentId, resolving the timezone via date +%z, and specifying the recurring pattern. The system then creates a delivery job that routes messages to the correct target automatically.

What's the best way to set up a one-off alert for X minutes later?

Setting up a one-off alert for X minutes later requires specifying the delay duration and target agentId. The system computes the timezone using date +%z formatting and creates a single scheduled delivery job with your custom message.

Does cron scheduling work with external delivery channels?

Cron scheduling works with external delivery channels by enforcing strict to-resolution rules. The system prevents creating external-channel delivery jobs without a valid target, ensuring messages route correctly to external recipients.

Why does my scheduled reminder require an agentId?

Scheduled reminders require an agentId because the system enforces mandatory agentId extraction to identify the correct delivery target. Without a valid agentId, the cron job cannot be created or routed to the intended recipient.

How do I cancel or manage existing scheduled cron tasks?

Canceling or managing existing scheduled cron tasks is supported through dedicated management workflows. You can identify the task by its agentId and schedule parameters, then execute cancellation commands to stop the recurring or one-off delivery job.

What limitations apply to reminder messages in scheduled delivery jobs?

Reminder messages in scheduled delivery jobs are constrained to 2–3 sentences and cannot contain tool or heartbeat responses. This ensures messages remain concise and focused on the intended reminder content for the recipient.