cron

Schedule future or periodic cron jobs with explicit agent-id.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bbzsking/copaw --skill cron-bbzsking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cron
Source: https://github.com/bbzsking/copaw/tree/main/src/qwenpaw/agents/skills/cron-zh
Command: npx skills add https://github.com/bbzsking/copaw --skill cron-bbzsking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage future timed or periodic tasks by creating and controlling cron jobs for automated actions, ensuring every operation is tied to a specific agent context.

Core Features & Use Cases

  • Schedule tasks that run at a future time or on a recurring basis across channels and targets.
  • Create, list, view, pause/resume, and delete cron jobs with explicit agent-id to avoid misrouting.
  • Support two task types (text and agent) and require time/cron, channel, target-user, target-session for creation, enabling reminders and automated checks.

Quick Start

Create a scheduled job with qwenpaw cron create, providing --agent-id and all required flags.

Frequently Asked Questions about cron

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

FAQPage Schema
How do I schedule future tasks and recurring cron jobs for an automated workflow?▼

To schedule future tasks, you create cron jobs by providing a time or cron expression, channel, target-user, and target-session. This automates actions like reminders and checks across specified targets.

How do I list, pause, and delete scheduled cron jobs for task management?▼

You manage scheduled cron jobs by listing, inspecting, pausing, resuming, and deleting tasks. Every management command requires an explicit agent-id to ensure operations target the correct agent context.

What information do I need to create a cron job for task automation?▼

Creating a cron job requires an explicit agent-id, a time or cron expression, a channel, target-user, and target-session. You also select a task type of either text or agent during creation.

Why does my scheduled task fail to create without an explicit agent-id?▼

Scheduled task creation fails without an explicit agent-id because the system enforces this flag on all commands. This requirement prevents misrouting by tying every cron job to a specific agent context.

Can I schedule automated recurring checks and reminders across different channels?▼

Yes, you can schedule recurring checks and reminders across different channels and targets. By setting a cron expression and specifying the channel with target-session details, tasks automate on a recurring basis.

What is the difference between text and agent task types when scheduling cron jobs?▼

When scheduling cron jobs, text and agent are the two supported task types. The metadata does not detail the internal differences, but both require time, channel, target-user, and target-session for creation.