skill-content-calendar-log · Unified Content Calendar

A unified content-calendar skill: every publish, user schedule, and platform event/holiday is recorded on one timeline (authoritative store outputs/_schedule.json, the same file the web calendar page reads), for agents to read back before planning topics and schedules. Publishing pages and chat flows that go through the publisher scripts are logged automatically — no manual bookkeeping.

It complements skill-publish-log (the metrics base): this base tracks "what to publish and when", publish-log tracks "how each item performed".

Example invocation: "Show me the calendar for the next two weeks — any posting gaps on each platform?"

Full brief

Positioning

skill-content-calendar-log is the authoritative store and read-back entry point for the publishing timeline: it records publishes + schedules + platform events on one timeline, for agents to consult before planning. It tracks "what to publish and when" — never metrics analysis.

Core capabilities

• Unified authoritative store: outputs/_schedule.json, the same file served by the web calendar page's /api/schedule. Each entry is either content (post/publish) or event (platform event / holiday / special date).
• Automatic publish logging: publishing pages and chat flows all route through publisher scripts, which auto-record a published entry on --exec success and forward it to skill-publish-log — no duplicate manual entries.
• Read-back planning summary: context outputs per-platform cadence, posting gaps, pending schedules, upcoming rideable events, plus suggestions — required reading before agent planning.
• Holiday seeding: seed-holidays lays down a year's fixed holidays (solar dates + lunar conversion + "Nth weekday" rules), idempotent and re-runnable.
• Event recording & bulk import: add-event records platform events/holidays; import-events bulk-imports from skill-event-calendar JSON with same-name-same-day idempotent dedup.
• Filtered queries & manual backfill: list filters by kind/platform/time; record-publish is only for offline posts that bypassed the publisher scripts.
• Profile-aware: with a profile, platform can be inferred from the main platform, making gap reminders more relevant.

Workflow

1. Before planning, read back the context summary (cadence / gaps / pending / upcoming nodes + suggestions)
2. add-event / import-events to land platform events and holidays
3. Manual scheduling, or read upcoming before scheduling
4. Publisher scripts auto-log after publishing (record-publish only for offline backfill)

Inputs & outputs

Output: calendar planning summary (cadence / gaps / pending schedules / upcoming nodes / suggestions), schedule and event lists.

Boundaries with adjacent skills

• skill-content-calendar (plan): builds the monthly schedule; reads this base's context before scheduling and writes plans back afterwards.
• skill-event-calendar (discover): looks up upcoming holidays/nodes; findings can be import-events-ed into the calendar.
• skill-publish-log (attribute): the per-post metrics base (reads / likes / reviews); publish records are auto-synced by scripts, no duplicate calls needed.

Fit

• Checking per-platform cadence and posting gaps before planning topics/schedules
• Landing holidays, sales events, and platform campaigns in advance
• Multi-platform gap monitoring with top-up reminders
• Looking back at what went out, and ahead at what's coming

Before you start

• No special configuration; publishes via publisher scripts auto-log.
• Offline posts that bypassed the scripts need manual record-publish backfill.
• Read the context summary before planning; relay its gap reminders and node suggestions as-is.

skill-content-calendar-log is part of the Aiglade Skill library. Invoke it from the Aiglade chat box in plain language.

← All 155 skills