ZJU-REAL/Easel / skills/builtin/skill-publish-scheduler
skill-publish-scheduler
Verified批量定时发布排期:管理"内容 × 平台 × 发布时间"的排期表,导入排期、查看队列、计算到期项、 到期派发给各平台发布 SKILL、回填状态。当用户说"定时发布""批量发布""排期发布""发布队列" "按计划发""这几条按时间自动发""发布排期表""到点发布"时使用。调度逻辑纯脚本,实际发布委派平台 SKILL。
批量定时发布排期
管理一张排期表(内容×平台×时间),到点把任务派发给各平台发布 SKILL。走
scripts/publish_queue.py(纯标准库)。本 SKILL 负责调度与状态,实际发布委派各平台 publisher (skill-xhs-publisher / skill-douyin-upload / skill-wechat-publisher / skill-bilibili-upload / cross-platform-publish)。
输入
排期表 CSV(表头需含 publish_at, platform, content,可选 title, note):
publish_at,platform,content,title
2026-08-01 09:00,xiaohongshu,outputs/note1,早间笔记
2026-08-01 20:00,douyin,outputs/主题名/final.mp4,晚间视频
或等价 JSON。
执行
脚本路径(相对项目根):skills/builtin/skill-publish-scheduler/scripts/publish_queue.py(各子命令 -h)。
Q=outputs/publish-queue/q.json
python <skill>/scripts/publish_queue.py import --file plan.csv --queue $Q # 导入排期
python <skill>/scripts/publish_queue.py list --queue $Q # 查看队列
python <skill>/scripts/publish_queue.py due --queue $Q # 此刻到期项
python <skill>/scripts/publish_queue.py run --queue $Q # 打印到期派发计划
# 按计划逐条委派对应平台 publisher 发布,完成后回填:
python <skill>/scripts/publish_queue.py mark --queue $Q --id 1 --status done
到期派发流程(编排)
due/run得到此刻到期项。- 对每条到期项:按
platform委派对应发布 SKILL 执行真实发布 (单平台或用 cross-platform-publish)。发布前按平台适配内容格式。 - 发布成功/失败后
mark回填状态(可配合 skill-publish-notify 推送结果、skill-publish-log 记录)。 - 需要"守护式到点触发"时,由当前执行引擎可用的定时功能或系统调度器周期性跑
run(本脚本只做单次到期计算,不常驻);没有调度能力时说明限制。
规则
- 本 SKILL 不直接驱动浏览器/API 发布——只做排期与状态管理,发布交给各平台 publisher。
--now可覆盖当前时间用于预演(查看某时刻会发哪些),不影响真实时间。- 发布时间用
YYYY-MM-DD HH:MM;同一时刻多平台会一并到期。 - 每条发布后务必
mark,避免重复发布。 - 定时触发依赖上层(执行引擎定时功能 / 系统调度器 / 手动周期跑),本脚本是无状态到期计算 + 持久化队列。
参考来源
排期→到期计算→派发→状态回填是内容日历落地发布的标准闭环。调度与真实发布分层: 调度纯脚本(可测),发布委派各平台 publisher(环境相关)。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |