editorial-calendar-planner

editorial-calendar-planner is a skill for Claude Code from ur-grue/autopunk-media-skills. It costs 38 tokens per session (10,642 once invoked), scanned A, original, MIT.

A scheduling tool for publications that maps stories across weeks or months, tracks their production stages, and balances staff workload.

In plain words
What is it for?
Use it to plan coverage, coordinate writers and editors, schedule seasonal work, and manage a publication pipeline.
Why use it?
It helps editors see what is planned, what is in progress, and where deadlines or shared resources may create bottlenecks.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the autopunk-media-skills plugin — 187 skills shipped together

Good fit Use it to plan coverage, coordinate writers and editors, schedule seasonal work, and manage a publication pipeline.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ur-grue/autopunk-media-skills/editorial-calendar-planner
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 ur-grue/autopunk-media-skills --skill editorial-calendar-planner
Clone the repo
git clone --depth 1 https://github.com/ur-grue/autopunk-media-skills

Made for: Claude Code.

Or install autopunk-media-skills, the plugin that ships this one along with the rest of its 187 skills.

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 editorial-calendar-planner

README.md
[![agentmods](https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/editorial-calendar-planner/github.svg)](https://agentmods.dev/skills/ur-grue/autopunk-media-skills/editorial-calendar-planner)
Your own site
<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/editorial-calendar-planner"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/editorial-calendar-planner/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 editorial-calendar-planner

Your own site · 80×15
<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/editorial-calendar-planner"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/editorial-calendar-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,642 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Memory Poisoning · line 456
    Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.
    Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
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.00038 $0.10642
Opus 5 $0.00019 $0.05321
Sonnet 5 $0.00008 $0.02128
Haiku 4.5 $0.00004 $0.01064

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

Security

Grade A, and why

editorial-calendar-planner 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 8d 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.

skills/magazine-journalism/ideation/editorial-calendar-planner/SKILL.md · 503 lines

How it starts

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

Editorial Calendar Planner

What This Skill Does

Generates a structured editorial calendar for a publication — mapping content across weeks or months, balancing evergreen and timely pieces, tracking production stages, and aligning coverage with external events.

When To Use This Skill

  • You are planning the next quarter's coverage and need a skeleton calendar before assigning stories
  • Your publication has a seasonal peak (awards season, festival coverage, holiday gift guides) and you need to reverse-engineer the production timeline from the publish dates
  • You have recently expanded or shrunk your team and need to redistribute workload across writers
  • An editor-in-chief is onboarding and wants to see the full pipeline visualised in one document
  • You are launching a new publication or section and need to build the first production schedule from scratch
  • You need to coordinate coverage across multiple beats that share the same production bottleneck (a single photographer, one copy editor, a shared designer)
  • You want to stress-test an existing rough plan: you have a list of stories you want to run but have not mapped them against the calendar to check for bottlenecks, workload peaks, or deadline conflicts
  • You are preparing a planning document for a stakeholder meeting (editorial board, publisher, funder) and need to show what the team will produce over the next period

What You Need To Provide

Required:

  • Publication type and frequency (weekly, biweekly, monthly, daily digital)
  • Team size — how many writers, editors, and other production staff
  • Beat coverage — which subjects your publication covers
  • Planning period — the timespan you want the calendar to cover (4–12 weeks)

Optional:

  • Upcoming external events relevant to your beats (festivals, elections, legislative sessions, industry conferences, awareness weeks, holidays)
  • Existing recurring content (regular columns, series, reviews sections)
  • Any hard editorial commitments already on the schedule (commissioned features, pre-sold advertorial adjacencies, special issues)
  • Preferred content mix (e.g., "we want more long-form features and fewer news recaps")
  • Historical patterns — which types of content perform best, which weeks are slow for readership
  • Production bottleneck information — does photography take longer than writing? Is the copy desk a single person?
  • Writer availability notes — part-time schedules, planned leave, other commitments
  • Whether you want the calendar to include web/digital slots alongside print, or print only

Read the full file on GitHub · 503 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. 8d ago First seen · 503 lines · 38 tokens per session scan A 233c1ed01fa0

Subscribe to this mod's changes

editorial-calendar-planner is a skill published in the GitHub repository ur-grue/autopunk-media-skills (32 stars, last pushed 12d ago), licensed MIT. It adds 38 tokens to every session and 10,642 once invoked, about $0.0002 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

contact-cache

Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.

gooseworks-ai/goose-skills · 38 tokens

atlassian

Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via…

sanjay3290/ai-skills · 96 tokens

beta-program-management

Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…

rampstackco/claude-skills · 155 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens

estimating-and-contingency

Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…

cbrock84/headcount · 87 tokens

requirement-forge-refiner

Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution…

techygarg/lattice · 121 tokens