content-calendar

content-calendar is a skill for Claude Code from cogni-work/insight-wave. It costs 84 tokens per session (1,222 once invoked), scanned A, original, Apache-2.0.

An editorial-calendar skill for turning a content strategy and campaign timelines into dated publication schedules with assigned channels and statuses.

In plain words
What is it for?
It helps create and maintain calendars in YAML and Markdown, assign channels, track cadence, and mark content as planned, drafted, reviewed, or scheduled.
Why use it?
It connects planned content to actual publishing dates, making production and scheduling easier to track.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the cogni-marketing plugin — 11 skills, 11 commands, 3 agents shipped together

Good fit It helps create and maintain calendars in YAML and Markdown, assign channels, track cadence, and mark content as planned, drafted, reviewed, or scheduled.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cogni-work/insight-wave/content-calendar
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cogni-work/insight-wave --skill content-calendar
Clone the repo
git clone --depth 1 https://github.com/cogni-work/insight-wave

Made for: Claude Code.

Or install cogni-marketing, the plugin that ships this one along with the rest of its 11 skills, 11 commands, 3 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for content-calendar

README.md
[![agentmods](https://agentmods.dev/badge/skills/cogni-work/insight-wave/content-calendar.svg)](https://agentmods.dev/skills/cogni-work/insight-wave/content-calendar)
Your own site
<a href="https://agentmods.dev/skills/cogni-work/insight-wave/content-calendar"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/content-calendar.svg" alt="Measured on agentmods" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,222 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00084 $0.01222
Opus 5 $0.00042 $0.00611
Sonnet 5 $0.00017 $0.00244
Haiku 4.5 $0.00008 $0.00122

Measured 4d ago against content hash 84eed664f862, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

content-calendar scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cogni-marketing/skills/content-calendar/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Content Calendar

Purpose

Generate a structured editorial calendar from the content strategy and campaigns. The calendar is the operational plan — it turns the strategic content matrix into dated, assigned, trackable publication slots.

Prerequisites

  • Marketing project with content strategy defined
  • Recommended: at least one campaign built

Output Formats

The calendar is maintained in two synchronized formats:

  1. calendar/content-calendar.yaml — Machine-readable source of truth
  2. calendar/content-calendar.md — Human-readable rendered view
  3. CSV export (on request) — For import into HubSpot, Notion, Asana, etc.

Workflow

Step 1: Load Content Inventory

  1. Read content-strategy.json — all planned content across markets and GTM paths
  2. Read campaigns/*.json — touchpoint timelines with day offsets
  3. Scan content/ — identify what's generated (draft) vs. still planned
  4. Read marketing-project.json — cadence defaults

Step 2: Build Calendar

For each content piece, assign:

  • Publication date: Based on campaign timeline or cadence defaults
  • Channel: From content format → channel mapping
  • Status: planned → drafted → reviewed → scheduled → published
  • Owner: Marketing (default) or Sales (for enablement content)
  • Dependencies: e.g., "LinkedIn promo post depends on blog being published"

Apply cadence rules from marketing-project.json:

  • linkedin-post: 3x/week → Mon, Wed, Fri
  • blog: 2x/month → 1st and 3rd Tuesday
  • email-nurture: triggered by download (not scheduled)
  • webinar: 1x/quarter → align with campaign timing

Step 3: Write Calendar Files

YAML source (content-calendar.yaml):

calendar:
  start_date: "2026-04-01"
  end_date: "2026-06-30"
  entries:
    - date: "2026-04-01"
      day: "Mon"
      market: "mid-market-saas-dach"
      gtm_path: "ai-predictive-maintenance"
      type: "demand-generation"
      format: "linkedin-post"
      title: "Trend hook: AI predictive maintenance"
      file: "content/demand-generation/mid-market--ai-pred--linkedin-post-01.md"
      channel: "linkedin"
      status: "drafted"
      campaign: "ai-pred-q2"
      owner: "marketing"
      notes: ""

Read the full file on GitHub · 126 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 126 lines · 84 tokens per session scan A 84eed664f862

Subscribe to this mod's changes

content-calendar is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 84 tokens to every session and 1,222 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens