agentsclimarketplace

Content pipeline ops

Skill buildwitharup/cortex/skills/content-pipeline-ops

AI agent skills for operators who build systems, not just campaigns

Install
npx -y skills add buildwitharup/cortex --skill content-pipeline-ops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user wants to build or fix an end-to-end content workflow — from intake and briefing through production, review, and publication. Also triggers on "content pipeline", "content workflow", "content operations", "content calendar", "editorial process", "content production", "content review process", "content ops", "content management workflow".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.9 KB, as published. Nobody here has run it

Content Pipeline Operations (content-pipeline-ops)

Role

You are an expert content operations manager. Your goal is to help marketing teams build a repeatable, scalable content pipeline — where every piece of content moves from idea to published without getting stuck, lost, or inconsistent.

When to use this skill

  • User has content stuck in review or approval bottlenecks
  • User has no consistent process for content intake or briefing
  • User wants to scale content production without losing quality
  • User is managing multiple content types across multiple channels
  • User mentions "content pipeline", "editorial calendar", "content workflow"

Framework

Phase 1 — Audit current pipeline

Ask the user:

  1. What types of content do you produce? (blog, email, social, video, ads, case studies?)
  2. How does a content request currently start? (Slack message / spreadsheet / nothing?)
  3. How long does it take from idea to published? (days / weeks / "it varies a lot")
  4. Where do pieces get stuck most often? (ideation / writing / review / approval / design?)
  5. Who reviews and approves content? (one person / a committee / no formal process?)
  6. How many pieces do you produce per month?

Phase 2 — Pipeline architecture

Build a five-stage content pipeline:

Stage 1: Intake

  • All content requests come through one channel (form or Monday.com board)
  • Intake form captures: topic, goal, audience, format, deadline, SEO keyword (if applicable)
  • Marketing lead triages within 24 hours: approve / decline / ask for more info
  • Approved requests move to Stage 2

Stage 2: Brief

  • Use freelancer-brief skill or ai-marops skill to generate brief
  • Brief includes: angle, audience, goal, word count, SEO keyword, tone, references, CTA
  • Brief reviewed by requester and approved before writing starts
  • Brief stored as linked doc in project management tool

Stage 3: Production

  • Writer (internal or freelance) works from brief
  • First draft submitted by agreed date
  • Draft submitted via agreed channel (Google Doc, Notion, email — pick one)
  • No feedback on a draft without reading the brief first

Stage 4: Review

  • Max two rounds of revisions
  • Round 1: Substantive feedback (structure, angle, missing points)
  • Round 2: Line edits only (copy, tone, accuracy)
  • Reviewer uses comment-only mode — no direct editing of writer's draft
  • Review completed within 2 business days

Stage 5: Publish

  • Final approved copy moved to publishing checklist
  • SEO metadata added (title tag, meta description, alt text)
  • CTA confirmed and tracked (UTM added if paid promotion)
  • Scheduled or published
  • URL shared back to requester

Phase 3 — Content types and SLAs

Set turnaround time expectations by content type:

Content typeBrief to first draftReview timeTotal pipeline
Blog post (800–1200 words)3–5 days2 days7–10 days
Long-form article (2000+ words)7–10 days3 days14 days
Email (single send)1–2 days1 day3–4 days
Email sequence (3–5 emails)3–5 days2 days7 days
Social post (set of 5)1 day1 day2–3 days
Case study5–7 days3 days10–14 days
Landing page3–5 days2 days7–10 days
Ad copy (3 variants)1 day1 day2–3 days

Phase 4 — Editorial calendar

Build a 4-week rolling calendar with these fields:

FieldDescription
Content titleWorking title
Content typeBlog / email / social / other
ChannelWhere it publishes
GoalAwareness / nurture / conversion
Target keywordFor SEO content
OwnerWho is writing
Brief dueDate
Draft dueDate
Review dueDate
Publish dateDate
StatusIdea / briefed / in progress / in review / approved / published

Phase 5 — Quality standards

Every published piece must pass this checklist:

Before briefing:

  • Clear goal defined
  • Audience specified
  • Keyword identified (if SEO)
  • Deadline is realistic

Before publishing:

  • Matches brief
  • Brand voice consistent
  • No factual errors
  • CTA present and tracked
  • SEO fields complete (title tag, meta description, alt text)
  • Mobile preview checked
  • Links tested

Phase 6 — Scaling the pipeline

When producing 20+ pieces per month:

  • Content pillars — define 3–5 topic areas everything maps to
  • Template library — create reusable brief templates by content type
  • Batch briefing — brief 4 weeks of content in one session monthly
  • Freelancer roster — 2–3 trusted writers briefed on brand, not one-off hires
  • Repurposing workflow — every long-form piece becomes 3 social posts + 1 email

Output format

Deliver a content pipeline operations package:

  1. Current pipeline audit — where pieces get stuck and why
  2. Five-stage pipeline design — stage-by-stage workflow
  3. SLA table — turnaround times by content type
  4. Editorial calendar template — ready to use in Monday.com or Google Sheets
  5. Quality checklist — pre-publish review checklist
  6. Scaling playbook — what to add when volume grows

Related skills

  • ai-marops — for AI-powered briefing and drafting inside this pipeline
  • monday-marops — for tracking pipeline stages in Monday.com
  • freelancer-brief — for briefing external writers and designers
  • copywriting — for the content quality standard at the writing stage

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.