Cron Setup — 技能工具

Name: Cron Setup — 技能工具
Author: BrennerSpear

BrennerSpear

Cron Setup — 技能工具

v1.0.0

[自动翻译] Create and manage OpenClaw cron jobs following our conventions. Use when setting up periodic tasks, reminders, automated checks, or any scheduled work...

0· 587·4 当前·4 累计

by @brennerspear (BrennerSpear)·MIT-0

自动化开发工具

下载技能包

License

MIT-0

最后更新

2026/4/11

安全扫描

VirusTotal

可疑

查看报告

OpenClaw

可疑

medium confidence

The skill's instructions generally match a cron-job helper, but there are notable inconsistencies (model selection vs template) and it directs the agent to post job output to a hard-coded Telegram channel/topic without declaring how credentials are provided — this could lead to unintended data exfiltration or misconfiguration.

评估建议

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 n...

详细分析 ▾

⚠ 用途与能力

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.

⚠ 指令范围

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.

✓ 安装机制

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.

⚠ 凭证需求

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.

✓ 持久化与权限

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.

安全有层次，运行前请审查代码。

License

MIT-0

可自由使用、修改和再分发，无需署名。

查看条款 ↗

运行时依赖

无特殊依赖

版本

latestv1.0.02026/2/26

Auto-publish from CI

● 可疑

安装命令点击复制

官方npx clawhub@latest install cron-setup

镜像加速npx clawhub@latest install cron-setup --registry https://cn.clawhub-mirror.com

技能文档

Our conventions for creating cron jobs in OpenClaw.

Default Settings

Setting	Default	Why
Model	`anthropic/claude-sonnet-4-5`	Reliable tool calls, works with any Anthropic Max plan — no OpenRouter needed
Session	`isolated`	Cron jobs run in their own session, not the main chat
Delivery	`"mode": "none"`	Job handles its own output (posts to Discord, etc.)
Timeout	120-180s	Most jobs should finish fast

Model Notes

Default to Sonnet (anthropic/claude-sonnet-4-5). Reliable, portable (no OpenRouter API key needed).
DeepSeek is unreliable for tool calls — don't use it for cron jobs.
Use Opus (anthropic/claude-opus-4-6) only as a last resort — expensive for scheduled tasks.
Model ID format: Use anthropic/claude-sonnet-4-5 not the full dated version (anthropic/claude-sonnet-4-20250514).

Job Template

{
  "name": "descriptive-kebab-case-name",
  "schedule": {
    "kind": "cron",
    "expr": "/30    ",
    "tz": "America/New_York"
  },
  "sessionTarget": "isolated",
  "payload": {
    "kind": "agentTurn",
    "message": "TASK INSTRUCTIONS HERE",
    "model": "openrouter/deepseek/deepseek-v3.2",
    "timeoutSeconds": 120
  },
  "delivery": {
    "mode": "none"
  }
}

Schedule Patterns

Pattern	Cron Expression	Notes
Every 30 min	`/30`	Good for inbox checks, monitoring
Every hour	`0`	Self-reflection, status checks
Daily at 4 AM	`0 4`	Cleanup, backups (during quiet hours)
Daily at 6 AM	`0 6`	Morning digests, daily summaries
Weekly Monday 2 PM	`0 14 1`	Weekly outreach, reviews
One-shot	Use `"kind": "at"` instead	Reminders, one-time tasks

Task Instruction Conventions
Be explicit with commands — Give the cron agent exact bash commands to run. It doesn't have our context.

Include skip conditions — If there's nothing to do, the agent should reply SKIP to avoid wasting tokens.

Handle its own output — The job should post results to Telegram (or wherever) using the message tool directly. Don't rely on delivery mode for formatted output.

Include error handling — What should happen if a command fails?

Keep instructions self-contained — The cron agent wakes up with no context. Everything it needs should be in the task message.
Telegram Posting from Cron Jobs
When a cron job needs to notify us, include these instructions in the task:
Post to Telegram using the message tool: action: send channel: telegram target: -1003856094222 threadId: TOPIC_ID message: Your formatted message
Topic IDs:
1 — Main topic (general updates, alerts)

573 — Research

1032 — Crypto

1488 — PR updates / dev notifications

1869 — Sticker store

3188 — Activity feed (workspace changes)
Delivery Modes
Mode When to Use
"mode": "none" Job posts its own output to Telegram (most common)
"mode": "announce" OpenClaw auto-delivers the agent's final message to a channel. Use when output IS the message (e.g., daily digest). Set "channel": "telegram" and "to": "-1003856094222:TOPIC_ID"

Anti-Patterns
❌ Don't use Opus for cron jobs unless the task genuinely needs it. Most cron tasks are simple checks. ❌ Don't use heartbeat for things that can be a cron job. Heartbeat runs in the main session (Opus) and costs way more. ❌ Don't create cron jobs that loop/poll — each run should be a single check. If you need polling, use a background exec script instead. ❌ Don't set delivery mode to "announce" and also have the job post to Telegram — you'll get duplicate messages.
Existing Jobs (Reference)
Check current jobs anytime with the cron list tool. As of setup:
workspace-activity-feed — Every 30 min, commits workspace changes, posts to activity feed

agentmail-inbox-check — Every 30 min, checks for new emails, responds to agents

sub-agent-monitor — Every 15 min, checks on stalled sub-agents

self-reflection — Hourly, reviews recent sessions for lessons learned

daily-workspace-commit — Daily 4 AM, git commits workspace changes

system-watchdog — Daily 4 AM, checks system resources

OpenClaw Daily News Digest — Daily 6 AM, generates news digest

sticker-sales-loop — Weekly Monday 2 PM, agent outreach for sticker store

Our conventions for creating cron jobs in OpenClaw.

Default Settings

Setting	Default	Why
Model	`anthropic/claude-sonnet-4-5`	Reliable tool calls, works with any Anthropic Max plan — no OpenRouter needed
Session	`isolated`	Cron jobs run in their own session, not the main chat
Delivery	`"mode": "none"`	Job handles its own output (posts to Discord, etc.)
Timeout	120-180s	Most jobs should finish fast

Model Notes
Default to Sonnet (anthropic/claude-sonnet-4-5). Reliable, portable (no OpenRouter API key needed).

DeepSeek is unreliable for tool calls — don't use it for cron jobs.

Use Opus (anthropic/claude-opus-4-6) only as a last resort — expensive for scheduled tasks.

Model ID format: Use anthropic/claude-sonnet-4-5 not the full dated version (anthropic/claude-sonnet-4-20250514).
Job Template
{ "name": "descriptive-kebab-case-name", "schedule": { "kind": "cron", "expr": "/30 ", "tz": "America/New_York" }, "sessionTarget": "isolated", "payload": { "kind": "agentTurn", "message": "TASK INSTRUCTIONS HERE", "model": "openrouter/deepseek/deepseek-v3.2", "timeoutSeconds": 120 }, "delivery": { "mode": "none" } }
Schedule Patterns
Pattern Cron Expression Notes
Every 30 min /30 Good for inbox checks, monitoring
Every hour 0 Self-reflection, status checks
Daily at 4 AM 0 4 Cleanup, backups (during quiet hours)
Daily at 6 AM 0 6 Morning digests, daily summaries
Weekly Monday 2 PM 0 14 1 Weekly outreach, reviews
One-shot Use "kind": "at" instead Reminders, one-time tasks

Task Instruction Conventions
Be explicit with commands — Give the cron agent exact bash commands to run. It doesn't have our context.

Include skip conditions — If there's nothing to do, the agent should reply SKIP to avoid wasting tokens.

Handle its own output — The job should post results to Telegram (or wherever) using the message tool directly. Don't rely on delivery mode for formatted output.

Include error handling — What should happen if a command fails?

Keep instructions self-contained — The cron agent wakes up with no context. Everything it needs should be in the task message.
Telegram Posting from Cron Jobs
When a cron job needs to notify us, include these instructions in the task:
Post to Telegram using the message tool: action: send channel: telegram target: -1003856094222 threadId: TOPIC_ID message: Your formatted message
Topic IDs:
1 — Main topic (general updates, alerts)

573 — Research

1032 — Crypto

1488 — PR updates / dev notifications

1869 — Sticker store

3188 — Activity feed (workspace changes)
Delivery Modes
Mode When to Use
"mode": "none" Job posts its own output to Telegram (most common)
"mode": "announce" OpenClaw auto-delivers the agent's final message to a channel. Use when output IS the message (e.g., daily digest). Set "channel": "telegram" and "to": "-1003856094222:TOPIC_ID"

Anti-Patterns
❌ Don't use Opus for cron jobs unless the task genuinely needs it. Most cron tasks are simple checks. ❌ Don't use heartbeat for things that can be a cron job. Heartbeat runs in the main session (Opus) and costs way more. ❌ Don't create cron jobs that loop/poll — each run should be a single check. If you need polling, use a background exec script instead. ❌ Don't set delivery mode to "announce" and also have the job post to Telegram — you'll get duplicate messages.
Existing Jobs (Reference)
Check current jobs anytime with the cron list tool. As of setup:
workspace-activity-feed — Every 30 min, commits workspace changes, posts to activity feed

agentmail-inbox-check — Every 30 min, checks for new emails, responds to agents

sub-agent-monitor — Every 15 min, checks on stalled sub-agents

self-reflection — Hourly, reviews recent sessions for lessons learned

daily-workspace-commit — Daily 4 AM, git commits workspace changes

system-watchdog — Daily 4 AM, checks system resources

OpenClaw Daily News Digest — Daily 6 AM, generates news digest

sticker-sales-loop — Weekly Monday 2 PM, agent outreach for sticker store

数据来源：ClawHub ↗ · 中文优化：龙虾技能库

OpenClaw 技能定制 / 插件定制 / 私有工作流定制

免费技能或插件可能存在安全风险，如需更匹配、更安全的方案，建议联系付费定制

了解定制服务

Mode	When to Use
`"mode": "none"`	Job posts its own output to Telegram (most common)
`"mode": "announce"`	OpenClaw auto-delivers the agent's final message to a channel. Use when output IS the message (e.g., daily digest). Set `"channel": "telegram"` and `"to": "-1003856094222:TOPIC_ID"`

License

运行时依赖

版本

安装命令 点击复制

技能文档

Default Settings

Model Notes

Job Template

Schedule Patterns

Task Instruction Conventions

Telegram Posting from Cron Jobs

Delivery Modes

Anti-Patterns

Existing Jobs (Reference)

Default Settings

Model Notes

Job Template

Schedule Patterns

Task Instruction Conventions

Telegram Posting from Cron Jobs

Delivery Modes

Anti-Patterns

Existing Jobs (Reference)

安装命令点击复制