Token导航 LogoToken导航

Agent Skill · 研究检索

cron-gate(克朗门)

cron-gate 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

cron-gate 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 13,349。

总安装 9,456周安装 394GitHub Stars 公开资料未说明下载 3,152核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:cron-gate(克朗门)
来源仓库:https://github.com/ori-claw/cron-gate
安装命令:
openclaw skills install cron-gate
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install cron-gate

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

通过零令牌 Python 脚本预先检查会话中的新消息,仅在存在新活动时触发昂贵的 OpenClaw cron,从而节省令牌。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install cron-gate;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

cron-gate 怎么安装?

在终端执行 openclaw skills install cron-gate。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

cron-gate 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

cron-gate 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

cron-gate 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

cron-gate 用的人多吗?

公开数据是累计安装 9,456 次,近一周安装 394 次,下载 3,152 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

cron-gate 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
cron-gate

克朗门 · 本页

9,456—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Cron Gate

Stop wasting tokens on crons with nothing to do.

Every OpenClaw cron that spawns an isolated LLM session burns tokens — prompt loading, Weave files, tool calls — even when there's nothing new to process. If you run memory integration across 5 sessions twice a day, that's 10 LLM wake-ups. Most of them find nothing and go back to sleep, having burned ~40K tokens each.

Cron Gate is a zero-token Python gatekeeper that checks for new activity *before* triggering expensive LLM crons. No new messages? No wake-up. No tokens burned.

How It Works

System crontab (free)          OpenClaw cron (expensive)
        │                              │
   gate.py runs              disabled, waiting
        │                              │
   checks sessions.json       ┌───────┘
        │                     │
   new activity? ─── yes ───► triggers cron via API
        │
       no ──► exits silently (0 tokens)
  1. A lightweight Python script runs on system crontab (zero LLM cost)
  2. It reads sessions.json to check updatedAt timestamps
  3. Compares against its own state file (last time it triggered each session)
  4. Only calls the OpenClaw gateway API to trigger crons for sessions with genuinely new messages
  5. Idle sessions never wake up — they cost nothing until someone talks in them

Install

1. Copy the gate script

cp gate.py /opt/scripts/cron-gate.py
chmod +x /opt/scripts/cron-gate.py

2. Configure your session-to-cron mapping

Edit the SESSION_CRONS dict in gate.py to map your session keys to their integration cron IDs:

SESSION_CRONS = {
    "agent:main:telegram:group:-1234567890": {
        "evening": "your-evening-cron-id-here",
        "morning": "your-morning-cron-id-here",
    },
    "agent:main:discord:channel:9876543210": {
        "evening": "another-cron-id",
        "morning": None,  # skip morning for this session
    },
}

Finding your session keys: Look in ~/.openclaw/agents/main/sessions/sessions.json

Finding your cron IDs: Run /crons in chat or check the OpenClaw dashboard

3. Disable the original crons

For each integration cron you're gating, disable it (but don't delete — the gate script triggers them on-demand):

/cron update <cron-id> enabled=false

Or ask your agent: "Disable all memory integration crons — they'll be triggered by the gate script now."

4. Add system crontab entries

# Evening integration window (adjust times to match your schedule)
5 6 * * * /usr/bin/python3 /opt/scripts/cron-gate.py evening >> /var/log/cron-gate.log 2>&1

# Morning integration window
5 18 * * * /usr/bin/python3 /opt/scripts/cron-gate.py morning >> /var/log/cron-gate.log 2>&1

Usage

# Dry run — see what would trigger without actually doing it
python3 gate.py --dry-run evening

# Force a specific slot (ignore time-of-day check)
python3 gate.py morning

# Normal operation (auto-detects slot from UTC hour)
python3 gate.py

Time Windows

The script auto-detects which slot to run based on UTC hour:

  • Evening: 4-8 UTC
  • Morning: 16-20 UTC

Override by passing evening or morning as an argument. When run from crontab with an explicit slot argument, the time window check is bypassed.

State File

Activity timestamps are stored in /opt/scripts/cron-gate-state.json (configurable). This is how the gate knows what's "new" — it compares each session's updatedAt against the last time it triggered that cron.

To reset (re-trigger everything on next run):

rm /opt/scripts/cron-gate-state.json

Token Savings

Real-world numbers from the first deployment:

  • Before: 10 integration crons × 2/day = 20 LLM sessions, ~800K tokens/day
  • After: Only sessions with new activity get triggered. Idle sessions = 0 tokens.
  • Typical savings: 60-80% reduction in integration token costs
  • Gate script cost: Zero. It's pure Python, no LLM involved.

Beyond Memory Integration

This pattern works for any cron that might have nothing to do:

  • Email checks — gate behind inbox message count
  • Social platform rounds — gate behind API health check
  • Notification checks — gate behind unread count
  • Any periodic LLM task — if a cheap check can determine "nothing to do," gate it

The principle: check cheap, wake expensive only when needed.

Requirements

  • Python 3.8+
  • OpenClaw with gateway API running on localhost:18789
  • System crontab access (crontab -e)
  • No additional dependencies (stdlib only)

平台分布

OpenClaw

91.87%
按下载量换算2,896

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills