Cron

Security checks across static analysis, malware telemetry, and agentic risk

Overview

This skill appears to be a local schedule/reminder helper that stores recurring job data on the user's machine, with no evidence of network access, credential use, or hidden execution.

This skill looks safe for local recurring reminders and task schedules. Be aware that it stores schedule details in local OpenClaw memory, so avoid putting secrets in job notes, and make sure Python 3 is available because the registry metadata does not declare it.

Static analysis

No static analysis findings were reported for this release.

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Risk analysis

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

#
ASI04: Agentic Supply Chain Vulnerabilities
Info
What this means

The skill may not work unless Python 3 is available, even though the registry metadata does not declare that dependency.

Why it was flagged

The runtime requirement is disclosed in SKILL.md, while the registry requirements list no required binaries. This is a metadata completeness issue rather than evidence of unsafe code.

Skill content
## Runtime Requirements
- Python 3 must be available as `python3`
- No external packages required
Recommendation

Before installing, confirm Python 3 is available; the publisher should declare Python 3 in the registry requirements.

#
ASI06: Memory and Context Poisoning
Low
What this means

Recurring-job titles and notes may remain in local OpenClaw memory until removed or edited.

Why it was flagged

User-provided schedule details are written into persistent local job storage. This is core to the skill's purpose, but it means private or instruction-like text can be retained and later displayed.

Skill content
"title": args.title,
"notes": args.notes,
"tags": parse_csv(args.tags),
...
save_jobs(data)
Recommendation

Avoid storing secrets or highly sensitive instructions in job titles or notes, and periodically review the local cron memory files if privacy matters.