cron-job-guardian
检查 cron 或 timer 配置中的频率、幂等、重试、日志与并发风险。;use for cron, timer, ops workflows;do not use for 直接启停生产任务, 替代真正监控.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/52yuanchangxing/cron-job-guardianWhat This Skill Does
The cron-job-guardian skill acts as a specialized auditor for system-level automation. It is designed to inspect cron jobs, systemd timers, and periodic operational workflows for critical architectural flaws. By acting as a static analysis tool, it evaluates configurations against industry best practices to identify risks related to frequency, idempotency, retry mechanisms, logging, and concurrency.
When you engage this skill, it transforms raw configuration files or task descriptions into a structured security and reliability analysis. It helps developers and SREs prevent “runaway tasks” where overlapping executions or lack of state handling could cause data corruption or system instability. It focuses on the 'how' and 'what' of your scheduled tasks, providing actionable insights before you deploy them to production environments.
Installation
To install this skill, run the following command in your terminal or OpenClaw interface:
clawhub install openclaw/skills/skills/52yuanchangxing/cron-job-guardian
Ensure you are using the latest version of the OpenClaw environment to maintain compatibility with the local resource templates.
Use Cases
- Pre-deployment Audits: Review new cron job entries for potential concurrency bottlenecks.
- Refactoring Maintenance: Assess existing scheduled scripts to add missing idempotency logic.
- Error Debugging: Investigate why a specific job fails intermittently by checking logs and concurrency flags.
- Compliance Checks: Standardize how internal services log their heartbeat and task-completion status.
Example Prompts
- "I have a script running every minute that updates a shared database. Check this cron entry for idempotency and concurrency risks."
- "Review the systemd timer configuration for my backup task and suggest a better retry policy."
- "Here is my
crontabfile. Please analyze the frequencies and identify if any tasks are likely to conflict during system busy hours."
Tips & Limitations
- Static Analysis Only: The skill performs read-only audits. It will not execute, modify, or stop your production tasks. This ensures your system state remains untouched.
- Collaborative Validation: Always use the 'Draft' output provided by the skill as a baseline, then refine it with human oversight before applying changes.
- Boundary Awareness: If your task involves high-risk actions like deleting files or external API changes, define explicit boundaries. The skill provides 'dry-run' plans for these scenarios to prevent accidental damage.
- Information Gaps: If critical configuration details are missing, the skill will list 'Awaiting Confirmation' items. Do not assume default behaviors; provide as much context as possible for an accurate report.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-52yuanchangxing-cron-job-guardian": {
"enabled": true,
"auto_update": true
}
}
}Tags
Flags: file-read
Related Skills
incident-postmortem-assistant
将事故线索整理成复盘草案,区分根因、诱因、放大器、影响与修复动作。;use for incident, postmortem, sre workflows;do not use for 归责个人, 篡改时间线.
securityvitals
Security vitals checker for OpenClaw. Scans your installation, scores your setup, and shows you exactly what to fix. First scan in seconds.
sealvera
Tamper-evident audit trail for AI agent decisions. Use when logging LLM decisions, setting up AI compliance, auditing agents for EU AI Act, HIPAA, GDPR or SOC 2, or when a user asks about AI decision audit trails, explainability, or SealVera.
doc-gap-finder
扫描文档目录、标题结构与文件分布,找缺失章节、重复内容和过时区域。;use for docs, audit, knowledge workflows;do not use for 读取无权限目录, 直接修改原文档.
agent-health-diagnostics
Diagnose and fix the 4 most common OpenClaw agent failures — heartbeat spam, API rate limit cascades, channel death loops, and memory/embedding errors. Battle-tested across a 6-agent multi-host deployment.