# Content Pipeline

> Manage the end-to-end content creation workflow from brief through research, drafting, review, formatting, publishing, and measurement. Use when the user asks to "write a blog post/article/newsletter about [topic]", "help me plan this week's content", "I have a content idea to develop", "review my content calendar", or shares a content brief.

- Skill: `ahnchen1983/content-pipeline` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ahnchen1983/content-pipeline`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ahnchen1983/content-pipeline/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: ahnchen1983 (https://skillmd.com/u/ahnchen1983)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ahnchen1983/content-pipeline

---


# Content Pipeline
# 內容產製流程

> *From idea to published piece — every step tracked, every standard met.*
> *從點子到發布——每個步驟被追蹤，每個標準被達到。*

---

## Identity 身份

- **Name**: content-pipeline
- **Type**: Process (end-to-end content creation workflow)
- **For**: Marketing teams, content creators, social media managers, editors, and anyone who produces content on a regular schedule — blog posts, social media, newsletters, press releases, or internal communications.
- **對象**: 行銷團隊、內容創作者、社群媒體經理、編輯，以及任何按照固定時程產出內容的人——部落格文章、社群媒體、電子報、新聞稿或內部通訊。

---

## Description 描述

Content creation looks creative and free-form from the outside, but professionals know it's actually a structured pipeline: ideation → research → outline → draft → review → revise → format → publish → measure. Drop any step and quality suffers. Skip tracking and you lose visibility into what's in progress, what's blocked, and what's about to miss its deadline.

內容創作從外面看起來是創意和自由的，但專業人士知道它其實是結構化的流程：構思→研究→大綱→草稿→審查→修改→排版→發布→衡量。省略任何步驟品質就下降。不追蹤就失去對進行中、被卡住和即將錯過截止日的可見度。

This Skill manages the entire content pipeline from idea to publication, adapting to the content type and platform requirements.

這個 Skill 管理從點子到發布的整個內容流程，適應內容類型和平台要求。

---

## Trigger Conditions 觸發條件

- "I need to write a [blog post/article/newsletter/social post] about [topic]"
  「我需要寫一篇關於 [主題] 的 [文章/電子報/社群貼文]」
- "Help me plan this week's content" / 「幫我規劃這週的內容」
- "I have a content idea I want to develop" / 「我有一個想發展的內容點子」
- "Review my content calendar" / 「審查我的內容行事曆」
- "This draft needs to go through our review process" / 「這份草稿需要走審查流程」
- User shares a content brief or topic assignment
  使用者分享內容簡報或主題指派

---

## Process Logic 流程邏輯

### Stage 1: Brief & Scope 簡報與範圍

1. **Define the content piece**:
   **定義內容**：
   - Content type: blog post, social media, newsletter, press release, case study, white paper, internal memo, other
     內容類型
   - Target platform: website, LinkedIn, Facebook, Instagram, email, internal, other
     目標平台
   - Target audience: who is this for? What do they care about?
     目標受眾
   - Objective: inform, persuade, entertain, educate, announce?
     目標：告知、說服、娛樂、教育、宣布？
   - Key message: the one thing the reader should take away
     關鍵訊息
   - Length/format constraints: word count, image requirements, template
     長度/格式限制

2. **Set the timeline**:
   **設定時程**：
   - Draft due: [date]
   - Review due: [date]
   - Publish date: [date]

### Stage 2: Research & Outline 研究與大綱

3. **Research the topic** (connect to research-and-summarize if deep research needed):
   **研究主題**：
   - Gather relevant facts, data, quotes, examples 收集相關事實、數據、引述、範例
   - Review competitor/peer content on the same topic 審視競爭者/同行在同一主題的內容
   - Identify the unique angle or value-add 辨識獨特角度或附加價值

4. **Create an outline**:
   **建立大綱**：
   - Hook / opening: how to grab attention 開場
   - Key sections with main points 關鍵段落和主要觀點
   - Supporting evidence for each point 每個觀點的支持證據
   - Call to action / conclusion 行動呼籲/結論
   - SEO considerations if applicable SEO 考量

5. **Get outline approval** (if workflow requires it):
   **取得大綱核准**（如果流程需要）：
   - Present outline to reviewer/stakeholder
   - Incorporate feedback before drafting

### Stage 3: Draft 草稿

6. **Write the first draft** following the approved outline:
   **按照核准的大綱撰寫初稿**：
   - Follow brand voice guidelines 遵循品牌語調指引
   - Write for the target audience's reading level 為目標受眾的閱讀水準寫
   - Include placeholder notes for images/media needed 包含需要的圖片/媒體的佔位備註
   - Mark any claims that need fact-checking 標記需要事實查核的聲稱

### Stage 4: Review & Revise 審查與修改

7. **Self-review** using a checklist:
   **自我審查**使用清單：
   - Does it deliver the key message? 有傳達關鍵訊息嗎？
   - Is the tone right for the audience? 語調適合受眾嗎？
   - Are all facts accurate and sourced? 所有事實正確且有來源嗎？
   - Is the length within constraints? 長度在限制內嗎？
   - Does the CTA make sense? CTA 合理嗎？

8. **Peer/editor review** (connect to document-reviewer):
   **同儕/編輯審查**（連接 document-reviewer）：
   - Send for review with specific feedback requests
   - Track review status and turnaround time

9. **Incorporate feedback** and produce final draft.
   **整合回饋**並產出最終稿。

### Stage 5: Format & Publish 排版與發布

10. **Format for platform**:
    **按平台排版**：
    - Apply templates, styles, or CMS formatting
    - Prepare images/media with proper sizing and alt text
    - Add metadata: tags, categories, SEO fields, author
    - Preview in target format

11. **Final approval check**:
    **最終核准檢查**：
    - All links work 所有連結可用
    - Images load correctly 圖片正確載入
    - Mobile display checked 行動裝置顯示檢查
    - No placeholder text remaining 沒有殘留的佔位文字

12. **Publish** according to content calendar.
    **按內容行事曆發布**。

### Stage 6: Measure (post-publish) 衡量（發布後）

13. **Track performance** (optional, if analytics available):
    **追蹤成效**：
    - Views, engagement, shares, conversions
    - Compare to previous content of same type
    - Note learnings for future content

---

## I/O Contract 輸入輸出合約

### Input 輸入
- Content brief: topic, audience, platform, deadline, key message
  內容簡報：主題、受眾、平台、截止日、關鍵訊息
- Optional: brand guidelines, templates, reference content, SEO keywords
  可選：品牌指引、模板、參考內容、SEO 關鍵字

### Output 輸出
- Completed content piece (formatted for target platform) 完成的內容（按目標平台排版）
- Content status tracker showing pipeline stage 內容狀態追蹤器
- Review feedback log 審查回饋日誌

```markdown
# Content Pipeline Status: [Title]
# 內容流程狀態：[標題]

| Stage 階段 | Status 狀態 | Date 日期 | Notes 備註 |
|---|---|---|---|
| Brief 簡報 | ✅ | [date] | [notes] |
| Research 研究 | ✅ | [date] | [notes] |
| Outline 大綱 | ✅ | [date] | [notes] |
| Draft 草稿 | 🔄 | [date] | [notes] |
| Review 審查 | ⬜ | [date] | |
| Revise 修改 | ⬜ | [date] | |
| Format 排版 | ⬜ | [date] | |
| Publish 發布 | ⬜ | [date] | |
| Measure 衡量 | ⬜ | [date] | |
```

---

## Validation Rules 驗證規則

1. **No stage skipped** — even for "quick" content, each stage gets at least a minimal pass. 沒有階段被跳過。
2. **Key message is present** — the reader can identify the main takeaway. 關鍵訊息存在。
3. **Brand voice is consistent** — matches the organization's tone guidelines. 品牌語調一致。
4. **Facts are verifiable** — no unsourced claims or statistics. 事實可驗證。
5. **Platform requirements met** — correct format, length, image specs for the target platform. 平台要求達標。
6. **Deadline tracked** — if content risks missing its publish date, flag early. 截止日被追蹤。

---

## Knowledge 知識庫

### Platform-Specific Guidelines 平台特定指引

- **Blog posts**: 800-2000 words, H2/H3 structure, 1 image per 300 words, SEO title + meta description
- **LinkedIn**: Professional tone, 1300 char for posts (for "see more" threshold), native images preferred, 3-5 hashtags
- **Facebook**: Conversational tone, shorter text, visual-first, link in comments for better reach
- **Instagram**: Visual-first, caption under 2200 chars, 20-30 hashtags, stories for time-sensitive
- **Newsletter**: Subject line under 50 chars, preview text, clear CTA, mobile-first design
- **Press release**: Inverted pyramid, dateline, boilerplate, quotes from spokesperson, contact info

### Content Quality Signals 內容品質信號
- **Strong opening**: Reader knows what they'll get within the first 2 sentences 讀者在前兩句就知道會得到什麼
- **Scannable**: Headers, short paragraphs, bullet points where appropriate 可掃讀
- **Specific**: Uses concrete examples and data, not vague generalities 具體
- **Actionable**: Reader knows what to do next 可行動

### Common Content Mistakes 常見內容錯誤
- Writing for yourself instead of the audience 為自己而不是受眾寫
- Burying the lead (key point too deep in the piece) 把重點埋太深
- All information, no story (or all story, no information) 全是資訊沒有故事
- Inconsistent publishing schedule undermining audience trust 不一致的發布時程削弱讀者信任

---

## Composition Hooks 組合接口

- **Upstream** 上游: research-and-summarize (deep topic research), meeting-notes-to-actions (content assignments from meetings)
- **Downstream** 下游: document-reviewer (review stage), social media scheduling tools, CMS publishing
- **Internal composition** 內部組合: Stage 3 (Draft) can itself invoke sub-Skills for specialized content types (e.g., a "press-release-writer" sub-Skill)

---

*Part of the [Agentic Substrate](../../../README.md) Example Skills Gallery.*