Feishu Cron Delivery

v1.0.0

Configure, repair, and validate OpenClaw scheduled outbound delivery to Feishu. Use when creating or fixing cron jobs that must proactively send user-visible...

0· 34·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the actual content: SKILL.md and the helper script only build and validate OpenClaw cron jobs that announce to Feishu. The files do not request unrelated credentials or access (no AWS/GitHub/etc.).
Instruction Scope
Runtime instructions are limited to OpenClaw CLI commands (cron list/add/runs) and a smoke-test generator script. They do not instruct reading arbitrary host files, scanning environment variables, or sending data to third-party endpoints outside OpenClaw/Feishu routing. The guidance to confirm the user received the Feishu message is appropriate for validation.
Install Mechanism
No install spec; this is instruction-only plus a small Python script. Nothing is downloaded or extracted from external URLs, so there is no high-risk installer behavior.
Credentials
The skill declares no required env vars or credentials. It reasonably assumes the operator's OpenClaw/Feishu channel is already configured; it does not try to collect or require secrets itself. Use of OPEN_ID/ACCOUNT_ID placeholders is explicit and appropriate.
Persistence & Privilege
Skill is not always-enabled, does not request persistent system presence, and does not modify other skills' configs. It simply provides operational instructions and a helper script.
Assessment
This skill appears coherent and low-risk, but take normal operational precautions before running commands that send messages to real users: 1) Ensure your OpenClaw environment has the correct Feishu channel credentials configured (the skill does not supply credentials). 2) Replace placeholders (OPEN_ID, ACCOUNT_ID) with test accounts when smoke-testing to avoid spamming real users. 3) Review the generated cron command before executing — the provided Python script only prints a command. 4) Be aware that scheduling cron jobs can create live side effects (outbound messages); use --delete-after-run or test accounts for validation. If you need higher assurance, confirm that your OpenClaw channel tokens are scoped to only allow the intended deliveries.

Like a lobster shell, security has layers — review code before you run it.

latestvk97dpkcxa3jtx9x5mxkqx6pqj1847z2j

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments