Loading...
Loading...
Found 37 Skills
Durable cron jobs with Rivet Actors: schedule.after and schedule.at timers survive restarts and crashes, plus re-arming recurring jobs and idempotent handlers.
Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks
Vercel Cron Jobs configuration and best practices. Use when adding, editing, or debugging scheduled tasks in vercel.json.
Deterministic audit of cron/scheduled job scripts for reliability, error handling, logging, cleanup, and concurrency safety. Use when user says "audit cron", "check cron script", "cron best practices", "scheduled job review", or "bash script audit". Do NOT use for crontab scheduling syntax, systemd timers, or general shell linting without a cron/scheduled-job context.
Google Workspace Events: Renew/reactivate Workspace Events subscriptions.
定时任务管理
This skill should be used when the user asks to "create scheduled job", "scheduled script", "cron job", "automation schedule", "recurring task", "batch processing", "nightly job", or any ServiceNow Scheduled Job development.
Vercel Functions and Edge Runtime, including cron jobs and routing middleware. Use when building APIs, serverless workloads, or scheduled tasks on Vercel.
Create and refine HEARTBEAT.md files for murmur — a CLI daemon that runs scheduled Claude prompts on a cron or interval schedule. Use this skill when the user wants to set up a recurring automated action (e.g., "monitor my GitHub issues", "check Hacker News for AI articles", "watch my endpoints", "send me a daily digest"). Guides the user through an interview, drafts the heartbeat prompt, tests it, and registers it with murmur's scheduler. Triggers: heartbeat, murmur, recurring task, scheduled action, cron, monitor, watch, automate, periodic check, scheduled prompt.
QQBot Scheduled Reminder. Supports creation, query, and cancellation of one-time and recurring reminders. Used when communicating via QQ channel and involving reminders/scheduled tasks.
Asks for user feedback after each task or cron job completion and runs a recursive learning flow. If output is good, asks what was good until 10 approvals; if needs improvement, asks why/how/what via multiple choice plus optional examples, uses web search and iterative thinking to resolve, and caps iterations by severity (slight 5, medium 10, severe 20). Keeps feedback non-intrusive. Use when completing discrete tasks or cron jobs for the user.
Manage OpenClaw bot configuration - channels, agents, security, and autopilot settings