content-scheduler

Content pipeline scheduling presets — delegates to armadillo-scheduler core skill with content-pumper defaults.

Model	Source
sonnet	pack: content-pumper

Full Reference

content-scheduler

Mandatory Announcement — FIRST OUTPUT before anything else:

┏━ 📅 content-scheduler ━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ [one-line description of scheduling operation]  ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

Thin wrapper around armadillo-scheduler with content-pumper presets. All scheduling operations delegate to the core scheduler.

Preset Schedules

Job	Cron	Prompt	Timeout
topic-scan	0 */6 * * * (every 6h)	Use the trend-scanner skill to scan for trending topics	600s
performance-review	0 9 * * 1 (Mon 9am)	Use the content-qa skill to review last week's published content	300s
auto-generate	event-driven	Triggered by topic-scorer when score > threshold	1200s

Usage

To register a content preset:

Use armadillo-scheduler to register the topic-scan preset:
- id: topic-scan
- cron: 0 */6 * * *
- prompt: "Use the trend-scanner skill to scan for trending topics"
- workingDirectory: <project root>
- maxTurns: 15

Delegation

All operations — register, unregister, list, status, run-now, history, logs — use armadillo-scheduler. This skill only provides content-specific defaults and prompt templates.

See armadillo-scheduler reference docs for full API.