Content Pipeline

SKILL运维和基础设施
运维和基础设施 未标注权限 许可证不明确

Orchestrator for the 3-article content pipeline — runs research phase, spawns parallel article sub-agents, creates Typefully drafts. Use when running the full content pipeline (usually via cron at 3am).

一句话选型结论

按资料字段整理

Content Pipeline是运维和基础设施类的 Agent Skill,安装方式:GitHub 仓库,权限级别未标注,许可证不明确,没有现成安装命令,需按说明手动放置 SKILL.md。技能本质是给模型读的说明书,效果取决于模型与客户端;装完先用一个小任务验证,再放进正式流程。

分类运维和基础设施 安装方式GitHub 仓库 权限级别未标注权限 许可证许可证不明确
累计安装 未标注 本周 未标注
GitHub 星标 未标注 仓库 skills
下载量 未标注 技能市场下载数
权限级别 未标注权限 安装前请确认风险范围
许可证 许可证不明确 未说明

安装

GitHub 仓库
在支持 Skills 的客户端里执行,装完问一句「你有哪些技能」验证
  1. 1
    确认客户端支持

    确认你的客户端支持 Skills(Claude、Codex、Cursor 等),并升级到较新的版本。

  2. 2
    拿到技能文件

    按安装说明或仓库 README,把 SKILL.md 放到客户端的 skills 目录(一般一个技能一个文件夹)。

  3. 3
    刷新技能列表

    重新打开客户端,或刷新技能列表,让新放进来的技能被加载。

  4. 4
    验证是否生效

    问一句「你有哪些技能」,确认列表里出现它,再拿一个小任务试跑。

技能档案

运维和基础设施
字段来自技能仓库与公开索引,中文说明由本站标注
作者 / 维护方exiao仓库 skills · 版本 未标注
宿主客户端未标注技能可被这些客户端加载
安装方式GitHub 仓库安装包 exiao/skills
权限级别未标注权限安装前请确认风险范围
许可证未说明许可证不明确,商用前请自行确认条款
仓库可用性available技能仓库当前是否可访问
最近核验未标注上游最后核验时间 · 数据更新 2026-05-12
正文体量6.3 KBSKILL.md 原文大小,越大说明说明书写得越细

典型使用场景

3 类
按分类整理的常见用法,具体以 SKILL.md 为准
查服务与日志

按现象定位服务状态与日志线索。

写部署与巡检脚本

把重复的部署、巡检写成脚本。

故障排查

按步骤排查网络、依赖与配置。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 基础信息齐全,可以先按说明装一个试试。

先想清楚的地方

  • 没有标注权限级别,实际能做什么要装好后确认。
  • 许可证不明确,商用或二次分发前先到仓库确认条款。
  • 没有现成安装命令,要按安装说明或仓库 README 手动放置。
  • 没有做站内核验,内容以作者仓库为准。
  • 技能只是说明书,实际效果取决于模型与客户端,装完先用小任务试一遍。

更适合

  • 需要在运维和基础设施场景里给模型补一套做法的人。
  • 愿意先读一遍 SKILL.md、确认它会让模型做什么的人。

不太适合

  • 对许可证要求很严、必须明确可商用的人。
  • 只想装完就自动变强、不打算看说明书的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
技能权限级别安装方式累计安装宿主客户端安装命令
Content Pipeline当前 未标注权限 GitHub 仓库 未标注 未标注 无
Azure 部署 调用外部服务 GitHub 仓库 664.2 万 Codex、Claude、Cursor 有
Azure diagnostics 问题管理 调用外部服务 GitHub 仓库 657.6 万 Codex、Claude、Cursor 有
Azure aigateway 部署 调用外部服务 GitHub 仓库 655.3 万 Codex、Claude、Cursor 有
Azure AI 搜索 调用外部服务 GitHub 仓库 651.4 万 Codex、Claude、Cursor 有
Azure Cloud migrate 部署 调用外部服务 GitHub 仓库 650.7 万 Codex、Claude、Cursor 有

SKILL.md 全文

6.3 KB
模型实际读到的说明书原文,来自技能仓库

Content Pipeline Orchestrator

Produces 3 article drafts per run: research once, then spawn 3 parallel sub-agents (one per article). Sub-agents handle their own skill reads. This orchestrator only handles the research phase and final reporting.

Do NOT publish anything. Everything stays as drafts.


Phase 0 — Deduplication Check (MANDATORY FIRST)

  1. Read ~/clawd/memory/content-published.md — topics already covered are off-limits
  2. Run bird tweets --user $TWITTER_USER -n 30 --plain — note angles the author published in the last 30 days
  3. Check recent Substack: web_fetch https://$SUBSTACK_URL — find recent post titles
  4. Build an EXCLUSION LIST. Do not pick any topic overlapping with it.
  5. After picking topics, append them to ~/clawd/memory/content-published.md

Phase 1 — Research (run once, takes ~15 min)

Read ~/marketing/WRITING-STYLE.md first.

1a. Gather engagement data

  • X/Twitter: Pull @$TWITTER_USER's last 30 posts via bird. Note which topics/angles got most engagement (likes, replies, retweets).
  • Grok X search: Run /grok-search with --x to find what's trending in the author's niches (AI, investing, indie dev, fintech).
  • Trend research: Run /last30days across YouTube, X, Reddit, and Substack to find viral formats, hooks, and topics with momentum.

1b. Find 3 topics

Topics should come from what's actually resonating on social, not from a fixed theme list. Look for:

  • High-engagement angles from the author's own X data (what got traction in the last 30 days)
  • Trending conversations where the author has a unique perspective (builder, investor, AI power user, solo founder)
  • Viral formats that can be adapted (data tables, outrage comparisons, contrarian takes, build-in-public threads)

Not every article needs to be about Bloom. Pick topics because they're genuinely interesting and the author has something real to say. Bloom integration only if it's natural and adds to the piece.

Pick topics where the author has unique credibility. Avoid angles anyone could write. Validate with X engagement data from Step 1a.

1c. Competitive gap check

For each topic: quick web search for what's already been written. Find the contrarian angle or data point competitors missed.

1d. Save research

Write all findings to ~/marketing/substack/drafts/[YYYY-MM-DD]-research.md:
- X engagement patterns (which topics resonated)
- Trending topics and viral formats found
- 3 chosen topics with positioning angle for each
- Key SEO keywords per topic


Phase 2 — Parallel Article Agents

Spawn 3 sub-agents in parallel using sessions_spawn, one per topic. Each sub-agent receives:

Topic: [topic]
Positioning angle: [angle from research]
X engagement insight: [what angle resonated with the author's audience]
Output directory: ~/marketing/substack/drafts/[slug]/

Your job:
1. Read ~/marketing/WRITING-STYLE.md
2. Run /hooks — generate 5 options, pick strongest → hooks.md
3. Run /outline-generator → outline.md
4. Run /writer → draft.md (must pass "only the author could write this" test: use specific numbers, named frameworks, personal experience. Reference Bloom only if naturally relevant to the topic.)
5. Run /editor-in-chief — max 5 iterations → editing-log.md + draft-final.md
6. Generate a hero image → hero.png
7. Write LinkedIn post directly → linkedin-post.md
   - Re-read ~/marketing/WRITING-STYLE.md kill phrases list before writing
   - Write a native LinkedIn post from draft-final.md. Do NOT reframe into "here's what most people get wrong" or "X isn't Y, it's Z" patterns. Lead with the most specific, surprising fact or data point from the article. Let the story carry the reader — no interpretive sentences telling them what to feel.
   - Run /evaluate-content on the post (Voice + Leanness scores only). If either scores below 4/5, rewrite and re-check. Max 2 revision passes.
   - Save final version to linkedin-post.md (post body only — no metadata headers)
8. Write X thread → x-thread.md
   - Run writer to create 5 standalone tweets from draft-final.md and sequence them as a thread.
   - No promotional framing, no article links in thread body (link goes in reply)
9. Format for Substack → substack-ready.md

Do NOT publish. Do NOT send messages unless blocked.

File structure per article

~/marketing/substack/drafts/[slug]/
  hooks.md            # 5 options + winner
  outline.md
  draft.md
  editing-log.md
  draft-final.md
  substack-ready.md
  hero.png
  x-thread.md
  linkedin-post.md

Phase 3 — Substack Drafts

After all 3 sub-agents complete, for each article save a Substack draft using the Substack skill with profile=clawd.

NEVER click Publish. Draft only.

Steps per article:
1. Read ~/marketing/substack/drafts/[slug]/substack-ready.md for title, subtitle, and body
2. Open Substack editor: browser action=open targetUrl="https://$SUBSTACK_URL/publish/post" profile=clawd
3. Paste title, subtitle, body
4. Upload hero.png as the cover image
5. Save as draft (never publish)
6. Capture the draft URL and include it in the Phase 4 report


Phase 4 — Typefully Drafts

After Substack drafts are saved, create Typefully drafts for each article:

IMPORTANT: Save as UNSCHEDULED drafts only. Do NOT schedule or publish anything.

# X thread draft — unscheduled draft only
cd ~/clawd/skills/typefully && node scripts/typefully.js drafts:create $TYPEFULLY_SOCIAL_SET_ID \
  --platform x --text "$(cat ~/marketing/substack/drafts/[slug]/x-thread.md)"

# LinkedIn draft — unscheduled draft only
node scripts/typefully.js drafts:create $TYPEFULLY_SOCIAL_SET_ID \
  --platform linkedin --text "$(cat ~/marketing/substack/drafts/[slug]/linkedin-post.md)"

Phase 5 — Report

Do NOT send via the message tool. Just output the summary as your reply. Cron delivery handles routing.

Include:
- 3 topics chosen (one line each with positioning angle)
- Substack draft URLs (one per article — ready to review and publish)
- Typefully draft links (LinkedIn + X thread, unscheduled)
- Source data and trending topics that informed each article

常见问题

5 问
答案由本站依据条目字段整理
Content Pipeline怎么安装?

没有现成安装命令:按安装说明或仓库 README,把 SKILL.md 放进客户端的 skills 目录(一般一个技能一个文件夹)。

Content Pipeline支持哪些客户端?

资料没有标注宿主客户端,但只要客户端支持 Skills(Claude、Codex、Cursor 等),一般都能加载。

Content Pipeline权限高吗,安全吗?

权限级别为未标注权限。安装前先看它会读取或写入哪些内容。

Content Pipeline收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于技能本身和所用的模型或客户端,正式使用前按作者说明确认。

Content Pipeline用什么许可证?

许可证标注为 未说明(许可证不明确)。商用或二次分发前请到仓库确认条款原文。

热门专题

按场景挑技能
全部专题 →

技能内容以作者仓库为准;分类、权限级别与许可证状态的中文说明为中文整理,最近核验 未标注。