Crypto Auto Progression
v0.1.0为 crypto-hedge-backtest 启用并维护“真实执行驱动”的自动推进(cron)。当用户要求每N分钟自动推进、自动汇报阶段成果、排查 cron 持续报错、或将自动化流程固化为可复用方案时使用。
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (auto progression for a crypto-hedge-backtest) match the SKILL.md: it instructs creating 5m/30m/daily cron jobs to run scripts, produce files/commits, and report results. That capability set is consistent with the stated purpose. However, the instructions expect the agent to perform code changes, runs, and commits (write access to the project), which is a higher privilege than the skill declares; the skill does not document required credentials or repo access which would normally be needed.
Instruction Scope
SKILL.md tells the agent to create cron jobs, run 'cron run --force', inspect 'cron runs' and 'cron list', detect and act on new files/commits/reports, and '跑脚本 / 改代码 / 产出文件' (run scripts / change code / produce files). Those are concrete actions that read and modify project state and may call external services (Binance). The instructions grant broad discretion to modify code and create persistent jobs; they do not limit what files/commands are used or require human review before committing changes.
Install Mechanism
Instruction-only skill with no install spec and no code files — minimal risk from installation (nothing is downloaded or written by an installer).
Credentials
The skill declares no required env vars or credentials, yet its instructions assume access to the project filesystem/repository and reference pulling data from Binance (network calls and potential API keys). This is a mismatch: tasks like fetching Binance data or pushing commits typically require API keys and repository auth, which are not surfaced or justified.
Persistence & Privilege
always:false (normal), but the core behavior is to create and manage recurring cron jobs on the platform (persistent automation). This creates long-lived effects (scheduled runs and potential repeated code changes). The skill does not request explicit confirmation steps or safety limits for those persistent actions.
What to consider before installing
This skill will set up recurring jobs that can run scripts, modify project code, and create commits/reports. Before installing: 1) Verify and trust the skill source — it has no homepage or author info. 2) Run it first in an isolated/staging workspace (not your production repo). 3) Require least-privilege credentials (read-only where possible) and hold back credentials for Binance or repo write access until you audit the exact commands and cron job contents. 4) Insist that every automated commit/change be reviewed (change diffs, signed commits, or gated merge). 5) Log and alert on all automated actions and provide a quick kill-switch to disable cron jobs. 6) If you need this functionality, ask the author for an explicit list of required env vars/permissions and for the exact cron job payload templates to review before giving write access.Like a lobster shell, security has layers — review code before you run it.
latest
Crypto Auto Progression
为 projects/crypto-hedge-backtest 提供可复用的自动推进流程。
目标
- 用 cron 驱动周期推进,而不是空提醒。
- 每次触发至少做一项真实执行:
跑脚本 / 改代码 / 产出文件。 - 仅在有阶段成果时汇报,避免重复话术刷屏。
标准任务模板
1) 5分钟推进任务(主任务)
- schedule:
every 5m - sessionTarget:
main - payload.kind:
systemEvent - payload.text 必须强调“真实执行 + 阶段成果汇报 + 无成果不重复提醒”
2) 30分钟健康检查(守护任务)
- schedule:
every 30m - 检查最近30分钟是否有真实产出(新文件/新commit/新报告)
- 无产出要告警并说明阻塞点
3) 每日日报(可选)
- schedule:
cron 30 21 * * *+Asia/Manila - 汇总:完成项、关键结果、风险点、明日计划
创建与验证(强制顺序)
- 先创建 1个 5分钟主任务。
- 立即
cron run --force手动触发一次。 - 用
cron runs确认status=ok。 - 再创建 30 分钟健康检查和每日日报。
- 用
cron list复核enabled=true和nextRunAtMs。
故障排查(高频问题)
-
invalid cron.add params ... required property 'name/schedule/sessionTarget/payload'- 原因:job 体缺字段或传了空
job:{}。 - 处理:按完整 job 结构重发,禁止盲目重试同一坏请求。
- 原因:job 体缺字段或传了空
-
openclaw-cn cron disable ... --json报unknown option '--json'- 原因:
cron disable不支持--json。 - 处理:去掉
--json。
- 原因:
-
Binance 拉数偶发
SSL: UNEXPECTED_EOF_WHILE_READING- 处理:在数据拉取层加入网络重试 + 指数退避;重试后再继续 scan 链路。
汇报规范(本项目)
- 有实质成果时汇报:
- 新增/更新文件
- 关键指标/结论
- 下一步动作
- 状态语句使用二选一:
继续推进中(无需你回复)我已暂停推进,等待你决策
Comments
Loading comments...
