monitor-restore

Restore the 3-hour Jupiter+Leonardo cluster sweep loop via /loop 3h or CronCreate.

276|37|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/open-thoughts/OpenThoughts-Agent --skill monitor-restore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-restore
Source: https://github.com/open-thoughts/OpenThoughts-Agent/tree/main/.claude/skills/monitor-restore
Command: npx skills add https://github.com/open-thoughts/OpenThoughts-Agent --skill monitor-restore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Re-create and maintain the local 3-hour Jupiter+Leonardo cluster sweep loop within the Claude session; the loop is session-only and is dropped on session restart, so re-establish it at the start of a new session or whenever the user asks to restore it.

Core Features & Use Cases

  • Re-establish the recurring sweep with /loop 3h or CronCreate, including the canonical prompt as the task.
  • Prevent duplicates by checking for an active loop before creation and clearly indicate session-only persistence and 7-day cron expiry.
  • Integrate with supporting docs and launch/cleanup skills to ensure logs, job status, and cleanup actions are consistently applied across clusters.

Quick Start

Run the monitor-restore skill to re-create the 3-hour cluster sweep in the current Claude session.

Frequently Asked Questions about monitor-restore

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

FAQPage Schema
How do I restore the Jupiter and Leonardo cluster sweep after a session restart?

The cluster sweep loop is session-only and dropped on restart, so you must re-establish it at the start of a new Claude session. Run monitor-restore to re-create the 3-hour Jupiter+Leonardo sweep using the canonical prompt.

How do I automate the 3-hour cluster sweep loop using cron?

Automate the 3-hour cluster sweep by triggering /loop 3h or CronCreate with the canonical prompt in your Claude session. The monitor-restore skill checks for active duplicates before creation to prevent overlapping jobs.

What are the limitations of the Claude session cluster sweep loop?

The cluster sweep loop is session-only and is dropped on session restart. Additionally, cron jobs created via CronCreate expire after 7 days, requiring re-establishment for sustained monitoring.

Does the cluster sweep loop handle duplicate monitoring jobs?

Yes, the monitor-restore skill prevents duplicates by checking for an active 3-hour sweep loop before creating a new one. This ensures only one cluster sweep runs within the Claude session.

What's the best way to maintain logs and cleanup across Jupiter and Leonardo clusters?

Integrate the monitor-restore skill with supporting docs and cleanup skills to enforce consistent logs, job status, and cleanup actions across Jupiter and Leonardo clusters during the recurring sweep.