Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Cron Setup
v1.0.0Create and manage OpenClaw cron jobs following our conventions. Use when setting up periodic tasks, reminders, automated checks, or any scheduled work.
⭐ 0· 551·4 current·4 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims to be a cron-job convention guide and most instructions align with that purpose, but the Job Template sets payload.model to an OpenRouter DeepSeek model while the text repeatedly says to default to anthropic/claude-sonnet-4-5 and explicitly notes that no OpenRouter key is needed. That mismatch is incoherent: a cron setup that 'doesn't need OpenRouter' should not use an openrouter model in its template. Also the SKILL.md embeds a hard-coded Telegram channel target (-1003856094222) and topic IDs — baking a fixed external destination into the conventions is a design choice that may not belong in a generic cron-setup skill.
Instruction Scope
Instructions require cron jobs to post results to Telegram using a 'message' tool and to include exact bash commands and error handling. The SKILL.md instructs posting to a specific channel and specific topic IDs; it also references tools like 'cron list' and a 'message' tool that are not declared in the skill metadata. Because the skill encourages sending arbitrary job output to a fixed external endpoint, it broadens the scope to include potential transmission of sensitive data.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so there is no installer risk or remote code download to evaluate.
Credentials
The skill declares no required environment variables or credentials, yet the guidance assumes the agent has a 'message' tool capable of posting to Telegram and the job template includes an OpenRouter model string (openrouter/...). If an OpenRouter model is actually used it would typically require an API key (not declared). Likewise, posting to Telegram normally requires credentials or a configured tool; those are not documented. The absence of declared credential requirements is disproportionate to the external actions the instructions expect.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide config, and is instruction-only. It does not demand persistent presence or elevated platform privileges.
What to consider before installing
This skill is mostly a straightforward cron-job style guide, but you should not install or run it without clarifying a few things: (1) Ask the author to explain and fix the model inconsistency (text recommends anthropic/claude-sonnet-4-5 but the example uses openrouter/deepseek). If openrouter models are required, ask where the API key is stored and why it wasn't declared. (2) Confirm how Telegram posting is authenticated: the SKILL.md hardcodes a Telegram channel ID and topic IDs but declares no credentials — verify who controls that channel and whether you want scheduled jobs posting there. (3) Consider removing or parameterizing hard-coded targets (channel ID and topic IDs) so jobs don't inadvertently leak sensitive output to a shared external channel. (4) Test in a safe environment with non-sensitive payloads before enabling production runs, and require explicit environment variables or admin approval for any job that posts externally. If the author cannot justify the model/template mismatch and the embedded Telegram targets, treat the skill as unsafe to enable.Like a lobster shell, security has layers — review code before you run it.
latestvk976r2ej0fy4c5rrf207ga5df181vk9d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.