rightcron

Manage cron jobs for a Right Agent via MCP tools.

34|4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/onsails/right-agent --skill rightcron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rightcron
Source: https://github.com/onsails/right-agent/tree/main/skills/rightcron
Command: npx skills add https://github.com/onsails/right-agent --skill rightcron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing periodic and time-based tasks for your Right Agent setup without manual scripting and ad-hoc scheduling.

Core Features & Use Cases

  • Create, update, and delete cron specs stored in the agent database.
  • Support for recurring schedules and one-shot runs with run_at.
  • Trigger cron runs manually and inspect run history and delivery status across Telegram chats.

Quick Start

Schedule a recurring health-check at 09:17 UTC on weekdays by creating a cron with a descriptive prompt.

Frequently Asked Questions about rightcron

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

FAQPage Schema
How do I schedule recurring cron jobs for my Right Agent?

To schedule recurring cron jobs for your Right Agent, you create cron specs stored in the agent database via MCP tools. You define the schedule, prompt, and delivery target Telegram chats.

Can I trigger a one-shot task with run_at instead of a recurring schedule?

Yes, you can trigger a one-shot task using the run_at field instead of a recurring schedule. This allows you to execute a single prompt at a specified time without manual triggering.

Do I need a Rust runtime to manage cron specs via MCP?

Yes, you need a Rust runtime to manage cron specs via MCP. The Rust runtime reconciles the specs stored in the agent database, while MCP tooling handles creation, updates, and deletion.

How do I deliver scheduled cron prompts to specific Telegram chats?

You deliver scheduled cron prompts to specific Telegram chats by setting delivery targets within the cron spec. The MCP tools manage these targets, allowing you to inspect run history and status across chats.

What are the limitations when using max_budget_usd and lock_ttl in cron schedules?

The max_budget_usd field limits the financial cost of a cron run, while lock_ttl manages the lock time-to-live to prevent overlapping executions. These fields ensure safe execution boundaries for your scheduled tasks.