cron

Schedule and manage recurring tasks with qwenpaw cron.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/9999-12-31/Dr.Claw --skill cron-9999-12-31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cron
Source: https://github.com/9999-12-31/Dr.Claw/tree/main/src/qwenpaw/agents/skills/cron-zh
Command: npx skills add https://github.com/9999-12-31/Dr.Claw --skill cron-9999-12-31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing future-time and recurring tasks across teams can be error-prone and time-consuming. This skill provides a reliable way to define and run scheduled actions using qwenpaw cron, ensuring explicit agent-id usage and consistent task orchestration.

Core Features & Use Cases

  • Create, list, view, pause, resume, and delete scheduled tasks with explicit agent identity.
  • Support two task types: text (scheduled messages) and agent (agent-driven prompts) across channels.
  • Guardrails to validate required fields (time/cron, channel, target-user, target-session) before creation to reduce misconfiguration.

Quick Start

Schedule a daily reminder cron by creating a task with a time, channel, and --agent-id.

Frequently Asked Questions about cron

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

FAQPage Schema
How do I schedule recurring reminders across different channels?

You can schedule recurring reminders across channels by creating a task with the required time, channel, target user, and an explicit agent identity. The system validates these fields before task creation to prevent misconfiguration.

Can I automate periodic task triggers for routine checks?

Yes, automating periodic task triggers for routine checks is supported. You can define recurring actions using qwenpaw cron, which orchestrates agent-driven prompts or scheduled text messages across target users.

What is required to set up a scheduled task for future execution?

Setting up a scheduled task requires specifying a time or cron expression, a channel, a target user, a target session, and a mandatory agent identity. These fields are validated before creation to ensure consistent scheduling.

Does task scheduling support both text messages and agent-driven prompts?

Task scheduling supports two task types: text for scheduled messages and agent for agent-driven prompts. Both types require explicit agent identity usage and valid channel targets before creation.

Why does scheduled task creation fail without an agent identity?

Scheduled task creation fails without an agent identity because the system enforces that all cron commands include an agent identity. This explicit requirement ensures reliable task ownership and consistent orchestration.

What's the best way to manage scheduled tasks after creation?

After creation, you can manage scheduled tasks by listing, viewing, pausing, resuming, or deleting them. This lifecycle management ensures you maintain control over recurring actions and future-time triggers.