Aegean Cron Mastery
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The instructions match a cron/reminder purpose, but the skill instructs file deletions, persistent memory writes, and includes hard-coded delivery targets while declaring no required config/credentials — these mismatches merit caution.
This skill appears to implement legitimate cron/scheduler guidance, but it contains several red flags: (1) it instructs deleting a local state file (~/.openclaw/state/cron/jobs.json) and writing to MEMORY.md — back up those files and require explicit confirmation before performing deletions/writes; (2) templates include hard-coded Telegram recipient IDs (e.g., 1027899060) and instruct sending proactive messages — verify how your platform's Telegram connector is configured and avoid using or keeping hard-coded external recipients; (3) the skill expects 'main' session privileges to remove jobs and perform maintenance, so restrict who/what can schedule janitor jobs and review any jobs before enabling autonomous execution; (4) the registry metadata declares no required config paths or credentials despite the instructions needing filesystem and messaging access — ask the author to explicitly list required permissions, config paths, and connectors; (5) the differing ownerId in _meta.json vs registry metadata is odd — request clarification or a clean packaging. Recommended actions before installing: review and sanitize example templates (remove hard-coded IDs), require an explicit allow-list for any cron jobs that can delete files or send messages, and test any troubleshooting steps (like file deletion) in a safe environment or with backups. If you need higher assurance, ask the publisher for a clarified manifest that declares required config paths and connector credentials and/or request a version that does not suggest destructive filesystem commands.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
No VirusTotal findings
Risk analysis
No visible risk-analysis findings were reported for this release.