evi-cron-self-revival

Restores and re-registers cron-jobs automatically after session restart using Python scripts.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/kolife01/evifarm --skill evi-cron-self-revival
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evi-cron-self-revival
Source: https://github.com/kolife01/evifarm/tree/main/skills/cron-self-revival
Command: npx skills add https://github.com/kolife01/evifarm --skill evi-cron-self-revival

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that scheduled tasks continue to run even after a session restart, automatically re-registering cron jobs without human intervention.

Core Features & Use Cases

  • Session Restart Resilience: Keeps cron jobs active across session restarts.
  • Automatic Re-registration: Automatically re-registers cron jobs based on a registry file.
  • Use Case: Ideal for applications where maintaining a consistent schedule is critical, such as automated backups or regular data syncs.

Quick Start

Implement this Skill in your project to ensure your cron jobs continue running after a session restart.

Frequently Asked Questions about evi-cron-self-revival

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

FAQPage Schema
How do I keep cron jobs running after a session restart?

To keep cron jobs running after a session restart, you need an automatic re-registration mechanism that restores scheduled tasks from a persistent registry file without manual intervention.

What is automatic cron job re-registration and how does it work?

Automatic cron job re-registration restores scheduled tasks by reading a registry file upon session restart, ensuring persistent scheduled tasks like automated backups continue executing without human intervention.

Do I need Python scripts to restore scheduled tasks automatically?

Yes, you need Python scripts for injection and poke execution to restore scheduled tasks automatically, enabling the session restart resilience mechanism to re-register cron jobs.

When should I use a session restart resilience mechanism for scheduled tasks?

Use session restart resilience for scheduled tasks when maintaining a consistent schedule is critical, such as running automated backups or regular data syncs across session boundaries.

What are the limitations of using a registry file for cron job management?

The limitation of using a registry file for cron job management is that automatic re-registration depends entirely on the registry file's integrity and requires Python script injection to trigger poke execution.