cron

Schedule future tasks with copaw cron commands and explicit --agent-id.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Jacksonhuf/AxiMate --skill cron-jacksonhuf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cron
Source: https://github.com/Jacksonhuf/AxiMate/tree/main/integrations/ripple/copaw/src/copaw/agents/skills/cron
Command: npx skills add https://github.com/Jacksonhuf/AxiMate --skill cron-jacksonhuf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Schedules future tasks automatically to ensure timely execution.

Core Features & Use Cases

  • List, create, view, manage, and trigger scheduled tasks with copaw cron commands.
  • Enforces explicit --agent-id for all operations to avoid misrouting across workspaces.
  • Handles both time-based (cron) and one-off recurring workflows with guardrails.

Quick Start

Create a daily reminder task by running copaw cron create --agent-id <agent_id> --type text --name 'Daily reminder' --cron '0 9 * * *' --channel <channel> --target-user 'CHANGEME' --target-session 'CHANGEME' --text 'Good morning!'

Frequently Asked Questions about cron

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

FAQPage Schema
How do I schedule recurring tasks and reminders to run automatically?

To schedule recurring tasks automatically, you can create time-based or one-off workflows using the copaw cron commands. This ensures timely execution for reminders, alerts, and periodic checks across defined channels and sessions.

What is the best way to set up a daily scheduled alert across different channels?

Setting up a daily scheduled alert involves using the create command with a defined cron expression, target channel, and session. It enforces explicit agent-id usage to prevent misrouting workspaces during automated task execution.

How do I manage and modify existing scheduled tasks after creation?

You can manage existing scheduled tasks by using list, get, state, pause, resume, delete, and run capabilities. These commands allow full control over task execution states and modifications across your configured sessions.

Do I need an agent-id to create and trigger scheduled tasks?

Yes, an explicit agent-id is required for all cron scheduling operations. This strict enforcement prevents misrouting tasks across different workspaces and ensures commands execute within the correct environment.

Can I pause and resume recurring task workflows without deleting them?

Yes, you can pause and resume recurring task workflows using dedicated state commands. This allows you to temporarily halt scheduled alerts or periodic checks and restart them later without losing the configuration.

What are the limitations when scheduling future tasks across multiple sessions?

When scheduling future tasks across sessions, limitations include the strict requirement for explicit agent-id usage and the need to define target-user and target-session parameters to avoid misrouting during automated execution.