Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Audits OpenClaw cron jobs to detect duplicates, noisy notifications, frequent runs, failures, and missing prerequisites, providing report-only optimization s...
Audits OpenClaw cron jobs to detect duplicates, noisy notifications, frequent runs, failures, and missing prerequisites, providing report-only optimization s...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Produces a single, human-readable cron audit report from an OpenClaw cron job list. Flags common ops issues: duplicate purpose (multiple jobs doing the same thing) notification spam (too many announce jobs) over-frequent cadence (high cost / high load) repeated failures / flaky external dependencies missing/invalid env prerequisites (e.g., vault file not present)
Lite = report-only by default. Do not disable/update/remove cron jobs unless the user explicitly says to apply a specific change. When proposing changes, prefer minimal, reversible edits: change delivery to none slow cadence add a digest job
Get current cron list (JSON): If you have the OpenClaw tool: call cron(list) and save output. If you are on terminal: openclaw cron list --json > cron_jobs.json (if available). Run analyzer: python3 skills/aoi-cron-ops-lite/scripts/analyze_cron_jobs.py --in cron_jobs.json
10β25 lines: totals (enabled/disabled) top risks (1β5) recommended actions (grouped) βapply planβ (explicit patches to run, but not executed)
Pro may auto-apply safe patches (with policy + approvals), generate PR-like diffs for cron config, and maintain a history ledger. Lite must never auto-apply.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.