cf-calendar

cf-calendar is a skill for Claude Code from teachskillofskills-ai/ContentForge-techshu. It costs 158 tokens per session (3,970 once invoked), scanned A, a copy of cf-calendar, MIT.

A planner for scheduling content work over 30, 60, or 90 days. It works backward from publication dates and shows the plan as a text timeline similar to a Gantt chart.

In plain words
What is it for?
Use it to assign topics, schedule production and review time, track milestones, and optionally create Google Calendar events.
Why use it?
It reveals deadline conflicts, bottlenecks, and unclear ownership before they cause missed publication dates.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the contentforge plugin — 22 skills, 9 commands, 13 agents shipped together

Good fit Use it to assign topics, schedule production and review time, track milestones, and optionally create Google Calendar events.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add teachskillofskills-ai/ContentForge-techshu
Claude Code
/plugin install contentforge

Made for: Claude Code.

Or install contentforge, the plugin that ships this one along with the rest of its 22 skills, 9 commands, 13 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 cf-calendar

README.md
[![agentmods](https://agentmods.dev/badge/skills/teachskillofskills-ai/contentforge-techshu/cf-calendar/github.svg)](https://agentmods.dev/skills/teachskillofskills-ai/contentforge-techshu/cf-calendar)
Your own site
<a href="https://agentmods.dev/skills/teachskillofskills-ai/contentforge-techshu/cf-calendar"><img src="https://agentmods.dev/badge/skills/teachskillofskills-ai/contentforge-techshu/cf-calendar/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for cf-calendar

Your own site · 80×15
<a href="https://agentmods.dev/skills/teachskillofskills-ai/contentforge-techshu/cf-calendar"><img src="https://agentmods.dev/badge/skills/teachskillofskills-ai/contentforge-techshu/cf-calendar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 158 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,970 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.
Origin 100% copy Near-identical to another mod 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.00158 $0.03970
Opus 5 $0.00079 $0.01985
Sonnet 5 $0.00032 $0.00794
Haiku 4.5 $0.00016 $0.00397

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

Security

Grade A, and why

cf-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 10d 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.

Origin

This is a copy

100% identical to cf-calendar — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/cf-calendar/SKILL.md · 396 lines

How it starts

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

Content Calendar Planner

Plan and manage content production calendars with intelligent scheduling, deadline tracking, team assignments, and optional Google Calendar event creation. The calendar works backward from publish dates to calculate production start times, identifies bottlenecks, and generates a visual text-based Gantt chart timeline.

When to Use

Use /contentforge:cf-calendar when:

  • You need a 30/60/90-day content plan with specific dates and deadlines
  • You want to schedule production timelines that account for ContentForge processing time + review buffers
  • You need to assign content to team members and track who's responsible for what
  • You want Google Calendar events with reminders for each production milestone
  • You're onboarding a new client and need a structured editorial calendar
  • You want to identify scheduling conflicts before they become missed deadlines

For producing content, use /contentforge:create-content or /contentforge:batch-process. For auditing what needs refreshing, use /contentforge:cf-audit first to identify candidates.

What This Command Does

  1. Load Content Plan — Import topics from manual input, Google Sheets, or audit recommendations
  2. Calculate Production Timelines — Work backward from publish dates to determine production start dates, accounting for ContentForge processing time (20-30 min per piece) and review buffer
  3. Schedule Production Windows — Assign production start/end dates and publish dates for each piece
  4. Team Assignment — Distribute pieces across team members with workload balancing
  5. Conflict Detection — Identify deadline bottlenecks where multiple pieces need production on the same day
  6. Calendar Event Creation — Create Google Calendar events (optional) with reminders for production start, review deadline, and publish date
  7. Visual Timeline — Generate a text-based Gantt chart showing the full calendar

Required Inputs

Minimum Required:

  • Time Period — 30, 60, or 90 days (from today or from a specified start date)
  • Content Plan — Topics to schedule (manual input, Google Sheets, or array)

Read the full file on GitHub · 396 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. 10d ago First seen · 396 lines · 158 tokens per session scan A c93dcfc79550

Subscribe to this mod's changes

cf-calendar is a skill published in the GitHub repository teachskillofskills-ai/ContentForge-techshu (1 stars, last pushed 21d ago), licensed MIT. It adds 158 tokens to every session and 3,970 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cf-calendar, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

meta-tags-optimizer

Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…

nowork-studio/notfair-plugin · 91 tokens

google-ads-audit

Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…

nowork-studio/notfair-plugin · 86 tokens

sxo

Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…

nowork-studio/notfair-plugin · 235 tokens

influencer-prospecting

Use when the user wants to find creators, influencers, affiliates, or social accounts in a niche for outreach, partnerships, sponsorships, UGC, seeding, or competitive research. Produces scored prospect lists from public social data.

ScrapeCreators/social-media-research-skills · 54 tokens

critical-code-reviewer

Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.

posit-dev/skills · 67 tokens

shiny-bslib

Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…

posit-dev/skills · 107 tokens