cron-dispatch — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited cron-dispatch (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when a script must run unattended on a schedule and the same pattern has to work on both a Windows dev box and a Linux server. It gives copy-paste setup for Windows Task Scheduler and Linux cron, plus logging and an overlap guard so a slow run never stacks on top of the next tick.
User input:
Run my scraper.py every day at 9am on Windows now, and give me the Linux cron line for the server later.Output:
# Windows: register a daily 09:00 task (run from the repo root)
powershell -ExecutionPolicy Bypass -File assets/setup_task.ps1 `
-TaskName "scraper-daily" `
-Command "python" `
-Arguments "E:\proj\scraper.py" `
-Time "09:00"# Linux: same job, 09:00 daily, logged, no overlap
0 9 * * * cd /srv/proj && flock -n /tmp/scraper.lock python scraper.py >> /srv/proj/cron.log 2>&1flock on Linux, -MultipleInstances IgnoreNew on Windows) so a long run does not double up.Reference: assets/setup_task.ps1, assets/cron_linux.sh.
Distilled from production use across the author's automation projects. v1.0.0. See also: [[pipeline-orchestrator]], [[telegram-alerter]].
→ Build the full runnable bot with Trawlkit.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.