Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Lint cron entries for schedule validity, bad model names, and missing NO_REPLY discipline markers.
Lint cron entries for schedule validity, bad model names, and missing NO_REPLY discipline markers.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Author: Billy (SAPCONET)
Provide quick lint + checklist guardrails for cron entries and notification discipline (NO_REPLY).
scripts/cron-lint.py: static checks for cron entry lines.
Cron schedule must contain exactly 5 fields. Rejects known bad model names (for example: haiku-4-6). Flags jobs that appear to announce/message but do not include NO_REPLY.
Lint a cron file: python3 scripts/cron-lint.py /path/to/crontab.txt Lint stdin: cat /path/to/crontab.txt | python3 scripts/cron-lint.py - Exit codes: 0: no issues 1: one or more issues found 2: usage or read error
Announce/inbox/notify-style jobs should explicitly include NO_REPLY in payload or message body. Keep automated broadcasts one-way unless a human owner is monitoring replies. Include owner and purpose in command comments.
*/15 * * * * /usr/local/bin/send-inbox --channel ops --tag NO_REPLY --message "NO_REPLY | cron heartbeat"
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.