content-pipeline-ops
Skill1 starsChanged 5 months agoMITView on GitHub
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".
In this repository17 other files it gives its agents.
- adsSkill
- ai-maropsSkill
- analyticsSkill
- casl-complianceSkill
- cold-emailSkill
- copywritingSkill
- croSkill
- emailsSkill
- freelancer-briefSkill
- ga4-attributionSkill
- marketing-budget-planningSkill
- martech-stack-auditSkill
- monday-maropsSkill
- paid-media-smbSkill
- plg-onboardingSkill
- revopsSkill
- seo-auditSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 41
All content requests come through one channel (form or Monday.com board)
- Very specific: line 47
Use freelancer-brief skill or ai-marops skill to generate brief
- Distinctive: line 56
No feedback on a draft without reading the brief first
- Distinctive: line 107
Every published piece must pass this checklist:
- Distinctive: line 126
When producing 20+ pieces per month:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- What types of content do you produce? (blog, email, social, video, ads, case studies?)
- How does a content request currently start? (Slack message / spreadsheet / nothing?)
- How long does it take from idea to published? (days / weeks / "it varies a lot")
- Where do pieces get stuck most often? (ideation / writing / review / approval / design?)
- Who reviews and approves content? (one person / a committee / no formal process?)
- 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-briefskill orai-maropsskill 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 type | Brief to first draft | Review time | Total pipeline |
| Blog post (800–1200 words) | 3–5 days | 2 days | 7–10 days |
| Long-form article (2000+ words) | 7–10 days | 3 days | 14 days |
| Email (single send) | 1–2 days | 1 day | 3–4 days |
| Email sequence (3–5 emails) | 3–5 days | 2 days | 7 days |
| Social post (set of 5) | 1 day | 1 day | 2–3 days |
| Case study | 5–7 days | 3 days | 10–14 days |
| Landing page | 3–5 days | 2 days | 7–10 days |
| Ad copy (3 variants) | 1 day | 1 day | 2–3 days |
Phase 4 — Editorial calendar
Build a 4-week rolling calendar with these fields:
| Field | Description |
| Content title | Working title |
| Content type | Blog / email / social / other |
| Channel | Where it publishes |
| Goal | Awareness / nurture / conversion |
| Target keyword | For SEO content |
| Owner | Who is writing |
| Brief due | Date |
| Draft due | Date |
| Review due | Date |
| Publish date | Date |
| Status | Idea / 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:
- Current pipeline audit — where pieces get stuck and why
- Five-stage pipeline design — stage-by-stage workflow
- SLA table — turnaround times by content type
- Editorial calendar template — ready to use in Monday.com or Google Sheets
- Quality checklist — pre-publish review checklist
- Scaling playbook — what to add when volume grows
Related skills
ai-marops— for AI-powered briefing and drafting inside this pipelinemonday-marops— for tracking pipeline stages in Monday.comfreelancer-brief— for briefing external writers and designerscopywriting— for the content quality standard at the writing stage
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.