← Back to Skills Marketplace
tianheihei002

Cron System Manager

by tianheihei002 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
69
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install cron-system-manager
Description
雨晴定时任务系统管理器。当需要检查cron任务状态、修改任务配置、排查重复职责、优化任务安排时触发此技能。也是主人确认的"主动发现+解决问题"能力核心。
README (SKILL.md)

Cron系统管理器 — 雨晴定时任务技能

这是雨晴的核心技能之一，管理所有定时任务的职责分工、规则制定和主动优化。 每次对话都要遵循本技能定义的角色分工。

一、核心原则

  1. 飞书推送规则（永久，禁止违反）：

    • ✅ 唯一推送：只有每日早间新闻 → 推送飞书
    • ✅ 响应交互：主人在飞书主动对话/回复时 → 在飞书响应
    • ❌ 禁止主动：不主动在飞书发起对话或推送任何内容
    • ❌ 禁止推送：其他所有情况（复盘、自检、Skills更新等）→ 不推飞书

  2. 超时失败自动补救原则（2026-03-25确立）：

    • cron 执行超时 → 立刻调高超时时间 → 立刻在独立会话重试
    • 不等主人来问 → 主动告知主人补救状态
    • 完整闭环：发现 → 修复 → 重试 → 告知

  3. 职责唯一性原则： 每个任务必须有且只有一个核心职责，不允许两个任务做同样的事

  4. 主动发现问题： HEARTBEAT每小时cron、每日复盘cron都有检查职责冲突的义务，发现即修复并汇报

  5. 新建任务前必查： 新建任务必须先确认与现有任务无职责重叠，方可创建

二、当前定时任务矩阵（2026-03-25最终版）

任务 ID 触发时间 核心职责 禁止事项
每日早间新闻 f7a98a38 06:37 北京 天气+新闻+飞书推送 -
每日自我复盘 a3f08238 23:37 北京 全面检查+复盘+主动改进 ❌不发飞书
每小时自检 848b23b5 每小时:00 ERRORS+cron状态+Skills+职能冲突 ❌不发飞书 ❌不做复盘
Skills每日更新 00cd2069 03:00 北京 clawhub检查+Skills更新 ❌不发飞书
每周总结 c5fd7eec 周日09:00 周报生成+保存+清理 ❌不发飞书

三、HEARTBEAT（消息触发）

触发规则

  • 每条消息进入时自动执行
  • 5秒内完成，极简判断

职责（P0极简）

读取 /workspace/ERRORS.md 头部20行：
  → 有❌/P0紧急问题？
      能修复 → 直接修复 + 告知主人
      不能修 → 告知主人需要协助
  → 无紧急问题？
      HEARTBEAT_OK（静默）

禁止事项

  • ❌ 不检查常规cron状态
  • ❌ 不读记忆文件
  • ❌ 不生成复盘
  • ❌ 不扫描职能冲突
  • ❌ 不做任何常规检查

四、每小时自检cron（定时执行）

触发规则

  • 每小时:00执行

职责（常规检查）

1. ERRORS.md 常规问题扫描
   - 有无P1/P2问题？
   - 有无超过24小时未解决的状态？

2. 所有cron任务状态
   - 有error的任务？
   - 连续2次以上error？
   - 有idle但不该idle的任务？

3. 每日自检（24小时周期）
   - Skills目录有无更新？
   - MEMORY.md有无损坏？
   - 有无职能冲突？

输出

  • 有error：summary写'⚠️ 发现问题：[描述]，已[处理]'
  • 无error：HEARTBEAT_OK

五、每日自我复盘cron（定时执行）

触发规则

  • 北京时间 23:37执行

职责（全面版7件事）

1. cron任务全面状态检查
2. 职能冲突扫描（发现即记录）
3. 系统完整性检查
4. 读取今日工作记录
5. 生成复盘（简洁版）
6. 主动改进建议（根据今日发现）
7. 保存到 /workspace/memory/每日复盘-YYYY-MM-DD.md

禁止事项

  • ❌ 不发飞书消息
  • ❌ 不做系统完整性之外的深度扫描

六、职能冲突检测机制

每次复盘cron执行时必做

  1. 检查是否有两个任务做了同样的事
  2. 检查是否有任务重复推送飞书
  3. 检查是否有HEARTBEAT和cron做同样的检查

发现冲突时

  • 立即记录到 /workspace/memory/职能冲突-YYYY-MM-DD.md
  • 立即修复（更新任务prompt或重新分配职责）
  • 在当日复盘中汇报

七、新建任务检查流程

当主人要求新建定时任务时：

Step 1：确认新任务的核心职责（一句话描述）
Step 2：与现有任务矩阵逐项比对，确认无重叠
Step 3：确认触发时间不与其他任务冲突
Step 4：确认推送目标（飞书 or 不推飞书）
Step 5：告知主人检查结果，有冲突则提出合并建议
Step 6：主人确认后创建

八、Token消耗参考

任务 单次 每日 每月
PDF类生成任务（天气/财经/教学/理财） ~200K ~800K ~24M
每小时自检 ~1.2K ~29K ~864K
每日自我复盘 ~100K 100K ~3M
Skills每日更新 ~5K 5K ~150K
HEARTBEAT ~500 ~10K ~300K
每周总结 ~100K — ~400K
合计 ~944K/天 ~28.3M/月

⚠️ PDF类生成任务包含多个搜索+HTML生成+部署步骤，超时时间统一定为600秒，不得低于此值。

九、文件路径速查

文件 路径
HEARTBEAT规则 /workspace/HEARTBEAT.md
ERRORS追踪 /workspace/ERRORS.md
每日记忆 /workspace/memory/YYYY-MM-DD.md
每日复盘 /workspace/memory/每日复盘-YYYY-MM-DD.md
职能冲突 /workspace/memory/职能冲突-YYYY-MM-DD.md
主动改进 /workspace/memory/主动改进-YYYY-MM-DD.md
每小时日志 /workspace/memory/hourly-check-YYYY-MM-DD.log

整理：雨晴 🌧️☀️ 更新：2026-03-25 00:23

七、ERRORS.md主动清理机制

清理原则

  • ERRORS.md只保留当前P0/P1问题
  • 问题解决后立即从主文件删除，不堆积
  • 完整历史移至：/workspace/memory/问题解决手册.md

清理触发时机

  • 每日复盘cron执行时顺手检查
  • 问题解决后立即清理
  • 每周总结时做一次全面清理

清理标准

状态 处理方式
P0紧急未解决 留在ERRORS.md
P1/P2已解决 立即删除，移至历史文档
超过7天的"处理中"记录 评估：能解决吗？→是→解决；否→更新说明
超过30天的任何记录 全部清理，保留摘要

八、问题解决参考

遇到问题时参考：

  • /workspace/memory/问题解决手册.md — 完整问题解决流程+今日经验
  • /workspace/memory/飞书推送系统化排错手册.md — 飞书推送专项排错
  • /workspace/ERRORS.md — 当前所有问题的追踪记录
Usage Guidance
Before installing: understand that this skill will read and write many files under /workspace and is instructed to autonomously 'fix' cron/tasks and update logs. Ask the author to clarify: (1) which channel exactly should be used to '告知主人' (Feishu is referenced but no Feishu credentials are declared); (2) whether the agent must get owner confirmation before making any changes (HEARTBEAT currently says '直接修复'); (3) add required config paths and any credentials to the metadata if external services (Feishu) are used; (4) resolve contradictory rules about when to send Feishu messages; and (5) consider limiting the skill's write permissions or requiring interactive confirmation for high-impact actions. If you cannot get these clarifications, treat the skill as potentially risky and avoid granting it broad write access or unattended execution privileges.
Capability Analysis
Type: OpenClaw Skill Name: cron-system-manager Version: 1.0.0 The skill bundle defines a comprehensive management system for an OpenClaw agent's scheduled tasks (cron jobs). It includes instructions for error tracking, task conflict resolution, and self-maintenance using local files in the /workspace directory. There are no indicators of data exfiltration, malicious execution, or unauthorized access; the logic is strictly focused on internal task organization and reporting as described in SKILL.md.
Capability Assessment
⚠ Purpose & Capability
The skill claims to manage and repair cron tasks and the SKILL.md contains detailed steps to read, update, and remove entries under /workspace and to modify task prompts/assignments — which aligns with a cron manager. However the skill metadata declares no required config paths, binaries, or credentials even though the instructions reference many concrete filesystem paths and external push channels (飞书). That mismatch (declared zero requirements vs. actual file and external-channel use) is an incoherence.
⚠ Instruction Scope
The runtime instructions explicitly tell the agent to read and write files under /workspace (e.g., /workspace/ERRORS.md, /workspace/memory/*), to detect and '立即修复' cron/task conflicts, and to perform hourly/daily checks. There are internal contradictions: some parts say '告知主人' but the '飞书推送规则' forbids active Feishu pushes except the morning-news task, and HEARTBEAT forbids reading memory files while other cron jobs do read them. The instructions give broad, sometimes autonomous authority (fix then notify) without clear constraints on what 'fix' means or which channel to use to notify the owner.
✓ Install Mechanism
This is instruction-only (no install spec, no code files). That keeps install risk low — nothing is downloaded or written by an installer. The main risk comes from what the agent is told to do at runtime, not from an installer.
⚠ Credentials
The SKILL.md refers to sending Feishu (飞书) pushes and responding to the owner, but the skill declares no environment variables or credentials (no Feishu token). If Feishu integration is required, missing credentials are an incoherence. The instructions also access many workspace paths (read/write) without those paths appearing in required config paths. The absence of declared credentials/config suggests the metadata is incomplete or misleading.
⚠ Persistence & Privilege
The skill instructs the agent to '立即修复' tasks, update prompts, remove entries from ERRORS.md, and create files under /workspace/memory/* — i.e., it expects write capability and autonomous remediation. While 'always' is false, the skill still implies making automated, persistent changes to the environment and logs without explicit, per-action owner confirmation in several branches (e.g., HEARTBEAT fixes). That level of autonomous write-and-modify behavior is notable and should be constrained or made explicit.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install cron-system-manager
  3. After installation, invoke the skill by name or use /cron-system-manager
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
cron-system-manager v1.0.0 - 首次发布，全面定义定时任务（cron）系统管理规范 - 明确职责矩阵与唯一性原则，防止任务重复或冲突 - 设定关键任务（如每日复盘、每小时自检、技能更新等）角色、触发时间、禁止事项和输出标准 - 制定严格的飞书推送规则，仅每日早间新闻允许主动推送 - 内置HEARTBEAT和职能冲突自动检测及补救机制 - 清晰列出任务新建检查流程、Token消耗评估与文件路径规范 - 建立ERRORS.md主动清理与问题归档机制
Metadata
Slug cron-system-manager
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Cron System Manager?

雨晴定时任务系统管理器。当需要检查cron任务状态、修改任务配置、排查重复职责、优化任务安排时触发此技能。也是主人确认的"主动发现+解决问题"能力核心。 It is an AI Agent Skill for Claude Code / OpenClaw, with 69 downloads so far.

How do I install Cron System Manager?

Run "/install cron-system-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Cron System Manager free?

Yes, Cron System Manager is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Cron System Manager support?

Cron System Manager is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Cron System Manager?

It is built and maintained by tianheihei002 (@tianheihei002); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments