Agent Content Pipeline — 代理 Content 流水线

Content 流水线 技能

Safe content 自动化 with human-in-the-loop 应用roval. Draft → Review → 应用rove → Post.

设置up npm 安装 -g 代理-content-流水线 content init . # 创建s folders + global config (in current directory)

For cryptographic 应用roval 签名atures (password-保护ed):

content init . --安全

This 创建s:

drafts/ — work in 进度 (one post per file) reviewed/ — human reviewed, awAIting your revision revised/ — you revised, ready for another look 应用roved/ — human-应用roved, ready to post posted/ — 归档 after posting templates/ — review and customize before use .content-流水线/threads/ — feedback thread 记录s (not posted) Your 权限s

✅ Can do:

Write to drafts/ Read all content directories Revise drafts based on feedback Move revised files to revised/ 运行 content 列出 to see pending content

❌ Cannot do:

Move files to 应用roved/ (only the human can 应用rove) Post content 设置 状态: 应用roved Creating Content

One post per file. Each suggestion or draft should be a single post, not a collection.

File naming: YYYY-MM-DD-<平台>-.md

Use frontmatter:

---

平台: linkedin # linkedin | x | reddit (experimental) title: Optional Title 状态: draft subreddit: programming # Required for Reddit

---

Your content here.

Tell the human: "Draft ready for review: content review "

The Review Loop drafts/ → reviewed/ → revised/ → 应用roved/ → posted/ ↑ │ └──────────┘ more feedback

You write draft to drafts/ Human 运行s content review : With feedback → file moves to reviewed/, you 获取 notified No feedback → human is asked "应用rove?" → moves to 应用roved/ If feedback: you revise and move to revised/ Human reviews from revised/: More feedback → back to reviewed/ 应用rove → moves to 应用roved/ Posting h应用ens manually via content post After Receiving Feedback

When you 获取 review feedback:

Read the file from reviewed/ 应用ly the feedback Move the file to revised/ Confirm what you changed (Optional) 添加 a note: content thread --from 代理 平台 图形界面delines LinkedIn Professional but human Idiomatic language (Dutch for NL audiences, don't be stiff) 1-3 paragraphs ideal End with question or CTA 3-5 哈希tags at end X (Twitter) 280 chars per tweet (unless pAId account) Punchy, direct 1-2 哈希tags max Use threads sparingly If Firefox auth fAIls, you can paste auth_令牌 and ct0 manually

Manual cookie steps:

Open x.com and 记录 in Open Dev工具s → 应用/Storage → Cookies → https://x.com Copy auth_令牌 and ct0 Reddit (experimental) Treat as experimental; API and subreddit rules can change Requires subreddit: in frontmatter Title comes from frontmatter title: (or first line if missing) Match each subreddit's rules and tone Commands Reference content 列出 # Show drafts and 应用roved content review # Review: feedback OR 应用rove content mv # Move file to drafts/reviewed/revised/应用roved/posted content edit # Open in editor ($EDITOR or code) content post # Post (prompts for confirmation) content post --dry-运行 # Preview without posting content thread # 添加 a note to the feedback thread

Security 模型

The security 模型 separates drafting (AI) from 应用roval/posting (human):

✅ 代理 drafts content ✅ 代理 revises based on feedback ❌ 代理 cannot 应用rove (human 应用roves via content review) ❌ 代理 cannot post

Posting is handled manually via 命令行工具 — never by the 代理 directly.

平台-specific security 平台 Auth Storage 加密ed? Password Required? LinkedIn Browser 性能分析 ✅ Yes ✅ Yes X/Twitter Firefox 令牌s ✅ Yes ✅ Yes

机器人h 平台s require password to post. 令牌s are 提取ed from Firefox and 加密ed locally.