editorial-ops — Claude Code skill: editorial calendar and GTM ops
editorial-ops is a Claude Code skill that plans multi-channel editorial calendars and coordinates GTM content production from ideation through distribution, with KPI guardrails set before assets ship.
Apache-2.0 ★ 450 updated 2026-04-03
npx skills add gtmagents/gtm-agents --skill editorial-ops -a claude-codeWhat editorial-ops does
The skill runs in Claude Code and builds an operational structure for GTM content teams. Its framework moves through five stages: setting the executive thesis and thematic pillars, mapping channels (blog, podcast, webinar, newsletter, LinkedIn) against owners and publish frequency, running production swimlanes from ideation to launch, branching a flagship asset into derivative formats, and locking KPI guardrails before drafting ends.
Two templates anchor the workflow — assets/editorial_calendar_template.md for tracking content and assets/distribution_brief.md for launch checklists. Tooling hooks tie into Serena for safe CMS snippet patching during QA, Context7 for current GA4 and HubSpot docs, Playwright for screenshots of landing pages before publish, and Sequential Thinking for working through campaign narratives or backlog reprioritization.
Content readiness requires a complete brief, stakeholder quotes, a cited SEO target, and CTA alignment — the checklist is explicit about each. Post-launch retros close within 5 business days; that step feeds insights back into the backlog and keeps the cycle honest.
What it helps with
- build a quarterly editorial roadmap tied to GTM objectives
- translate thematic pillars into weekly blog, newsletter, and social schedules
- audit production capacity and surface approval bottlenecks
- generate a distribution checklist signed off by Marketing Director and Sales
- document KPI guardrails for reach, CTR, and SQL influence before content launches
Example prompts for the agent
- Draft a quarterly editorial roadmap from our current GTM themes
- Map channels with owners, publish frequency, and CTAs for the next sprint
- Fill the content readiness checklist for this post before it goes to approval
How to install editorial-ops
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill editorial-ops -a claude-code2Manually: put the files in place
~/.claude/skills/editorial-ops/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/editorial-ops/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill editorial-ops -a codex2Manually: put the files in place
.agents/skills/editorial-ops/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill editorial-ops -a cursor2Manually: put the files in place
.cursor/skills/editorial-ops/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gtmagents/gtm-agents plugins/content-marketing/skills/editorial-ops2Manually: put the files in place
.github/skills/editorial-ops/SKILL.md1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill editorial-ops -a gemini-cli2Platform CLI
gemini skills install https://github.com/gtmagents/gtm-agents --path plugins/content-marketing/skills/editorial-opsManually: put the files in place
.devin/skills/editorial-ops/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about editorial-ops
How do I install editorial-ops in Claude Code?
Run npx skills add gtmagents/gtm-agents --skill editorial-ops -a claude-code. The skill then lives at ~/.claude/skills/editorial-ops/SKILL.md.
What does the editorial-ops skill do?
It structures GTM editorial operations: quarterly roadmaps, channel grids with owners, production swimlanes, distribution trees, and pre-launch KPI documentation — all within Claude Code.
Which tools does editorial-ops rely on for full functionality?
It integrates with Serena for CMS patching, Context7 for GA4 and HubSpot documentation, Playwright for pre-publish page screenshots, and Sequential Thinking for campaign narrative work. Without those tools, the corresponding steps fall back to manual handling.
Source text
SKILL.md · Apache-2.0
--- name: editorial-ops description: Use when planning multi-channel editorial calendars, enforcing publishing cadences, and coordinating distribution workflows across GTM teams. --- # Editorial Operations Skill ## When to Use - Building or refreshing quarterly editorial roadmaps tied to GTM objectives. - Translating thought-leadership pillars into weekly blog, newsletter, and social programming. - Auditing production capacity, approvals, and distribution SLAs to eliminate bottlenecks. ## Framework 1. **North Star & Themes** – lock the executive thesis and supporting pillars (see GTM Agents Marketing Director guidance @puerto/README.md#183-212). 2. **Cadence Grid** – map channels (blog, podcast, webinar, newsletter, LinkedIn) vs. frequency, owner, and CTA. 3. **Production Swimlanes** – ideation → outline → draft → edit → design → approvals → launch. 4. **Distribution Tree** – primary asset → derivative snippets → paid boosts → lifecycle inserts. 5. **Measurement Layer** – define KPI guardrails (reach, engagement, SQL influence, pipeline velocity) before content leaves drafting. ## Workflow Checklist - Weekly **Editorial Stand-up** (30 min): review status board, unblock owners, confirm launches. - **Content Readiness Criteria**: complete brief, stakeholder quotes, sources cited, SEO target, CTA alignment. - **Approval Paths**: highlight who signs off (Content Strategist, Brand, Legal) and expected turnaround. - **Escalation Matrix**: Marketing Director + Project Manager contacts for scope or timeline changes. ## Templates - **Editorial Calendar**: See `assets/editorial_calendar_template.md` for tracking content. - **Distribution Brief**: See `assets/distribution_brief.md` for launch checklists. - **Post-Launch Debrief** template capturing performance vs. guardrails, learnings, and follow-up actions. - **Ops Dashboard** view showing backlog aging, production velocity, and publication mix. ## Tips - Treat every flagship asset like a mini campaign: pair the lifecycle-mapping blueprint (Plan → Build → QA → Launch → Inspect) with editorial checkpoints. - Partner with Marketing Analytics to instrument dashboards early; no asset ships without a measurement plan. - Keep a "Parking Lot" section for emergent ideas so high-priority launches retain focus. - Borrow GTM Agents's status packet format (see lifecycle-mapping skill) for weekly exec updates. ## Tooling Hooks - **Serena**: patch CMS or marketing automation snippets safely during content QA. - **Context7**: fetch current GA4/HubSpot docs when defining measurement plans. - **Sequential Thinking**: reason through campaign narratives or backlog reprioritization. - **Playwright**: capture screenshots of new landing pages or gated assets before publishing. ## Deliverables 1. Quarterly editorial roadmap (themes, owners, launch dates). 2. Weekly status packet summarizing highlights, KPIs, blockers, and next five actions. 3. Distribution checklist signed by Marketing Director + Sales counterpart to ensure coverage. ## Quality Gates - KPI guardrails documented pre-launch (reach %, CTR, SQL influence, retention impact). - Approval sign-offs stored with links/timestamps for audit trail. - Post-launch retro completed within 5 business days, feeding insights back into the backlog.
© gtmagents · Apache-2.0 · gtmagents/gtm-agents