sue-cronjob

Manage SUE-tagged cron entries across Unix, Codex, Kimi, and RunPod backends.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dongzhuoyao/deepresearch --skill sue-cronjob
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sue-cronjob
Source: https://github.com/dongzhuoyao/deepresearch/tree/main/.codex/skills/sue-cronjob
Command: npx skills add https://github.com/dongzhuoyao/deepresearch --skill sue-cronjob

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Managing recurring scheduled tasks for SUE scale-up ML/HPC experiments is error-prone when juggling multiple experiment runs across different backends, as manual cron edits can accidentally disrupt unrelated system jobs or miss critical monitor and cleanup triggers.

Core Features & Use Cases

  • Tagged Cron Safety: Only modifies cron entries explicitly tagged with SUE_CRONJOB id=<id> to avoid accidental changes to unrelated scheduler jobs.
  • Multi-Platform Support: Handles local Unix cron, Codex CLI cron wrappers, Kimi CronCreate reminders, RunPod cleanup cron, and macOS LaunchAgents for cluster snapshot jobs.
  • Guardrail Enforcement: Enforces default Asia/Shanghai timezone, secret redaction, disable-instead-of-delete for temporary stops, and mandatory dashboard observability via Turso status writes.
  • Use Case: When running a long SUE fullrun experiment on RunPod, use this skill to set up a 10-minute recurring monitor cron that alerts you if GPU hours are missing, without risking other system cron entries.

Quick Start

Use the sue-cronjob skill to list all active SUE-tagged cron jobs for your current experiment workspace.

Frequently Asked Questions about sue-cronjob

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

FAQPage Schema
How do I safely manage cron jobs for ML experiments without affecting system scheduler tasks?▼

To safely manage cron jobs for ML experiments, you can use tagged entry validation to only modify entries explicitly tagged with SUE_CRONJOB id=<id>, preventing accidental changes to unrelated system scheduler tasks.

Can I schedule RunPod cleanup and monitor tasks across different backends from one place?▼

Yes, you can schedule RunPod cleanup and monitor tasks across multiple backends, handling local Unix cron, Codex CLI, Kimi CronCreate, RunPod, and macOS LaunchAgents from a single workflow interface.

How do I ensure consistent timezone and secret redaction when creating Codex CLI cron wrappers?▼

You ensure consistent timezone and secret redaction for Codex CLI cron wrappers by enforcing guardrails that apply a default Asia/Shanghai timezone and automatically redact secrets during entry creation.

What is the best way to track cron job execution status for HPC scale-up experiments?▼

The best way to track cron job execution status for HPC scale-up experiments is by writing mandatory status updates to a Turso cronjob_runs table, providing direct dashboard observability for your runs.

Does disabling a monitor cron entry permanently delete it from my Unix cron?▼

No, disabling a monitor cron entry does not permanently delete it from Unix cron; the system enforces a disable-instead-of-delete guardrail for temporary stops, allowing you to re-enable it later.

Why do my SUE experiment cron jobs require writing to a Turso cronjob_runs table?▼

SUE experiment cron jobs require writing to a Turso cronjob_runs table to enforce mandatory dashboard observability, ensuring that every scheduled monitor, dryrun, fullrun, and cleanup execution is tracked.