cron-management@1.0.0
CAUTION· static onlyPublisher claims: "Manage OpenClaw cron jobs — list, pause, resume, maintenance mode, and health checks." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-10 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Context shift attempt; Context shift attempt; Destructive file system command detected. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
| `cronctl maintenance on` | Enable maintenance mode (stops all jobs at runtime) |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Developers and operators use this skill to inspect OpenClaw cron job status, pause or resume jobs, enable maintenance mode, and diagnose recent job failures.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.3. **Verification**: Enable maintenance mode, wait for next trigger, check `/tmp/cron-skipped.log`Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.rm /tmp/cron-pausedFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim space-cadet: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Destructive file system command detected≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.