scheduler notification runbook
v1.0.0Reliable runbook for scheduled reminders and notification workflows with OpenClaw cron. Use when creating or reviewing reminder skills, scheduling one-shot o...
⭐ 0· 70·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the SKILL.md content: a runbook for deciding payload type, session target, schedule kinds, and reminder text. There are no unrelated env vars, binaries, or installs requested.
Instruction Scope
The instructions stay on-topic (choosing payloads, session targets, schedules, and writing reminder text). The runbook advises verifying that a job actually fired and troubleshooting delivery, but it does not give or request concrete steps or credentials for checking platform logs — operational verification will require appropriate scheduler/platform access outside this document.
Install Mechanism
No install spec and no code files are present. This is instruction-only, so nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. Nothing disproportionate is requested relative to the runbook's purpose.
Persistence & Privilege
always is false and there are no installation hooks. The skill does not request permanent presence or elevated system privileges. The default ability for the agent to invoke the skill autonomously is unchanged and appropriate for a runbook.
Assessment
This is a safe, instruction-only runbook: it contains guidance for choosing reminder payloads, session targets, and writing reminder copy and does not ask for credentials or install code. Before using it in production, ensure your scheduling system's permission model is correct — verifying whether jobs fired or troubleshooting delivery will require access to your scheduler/platform logs or APIs, which are outside this document. Also avoid encoding secrets or sensitive data into reminder text (reminders are meant to be readable later). If you wire this guidance into an automated workflow, review any scheduler integration code separately to confirm it only has the minimal permissions needed to create and inspect jobs.Like a lobster shell, security has layers — review code before you run it.
latestvk970shv5wzhrh5yngxr726x46983qgg1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
