内容发布
- 作者仓库星标 37
- 作者仓库 GENesis-AGI
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @WingedGuardian · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
如果调用者提供了一个主题,请使用它。如果没有,请检查这些来源: 自我建议(如果通过`publish_content`操作发送) 最近的侦察结果(`recon_findings`MCP) 用户领域中趋势主题的知识库 除非另有说明,否则平台为中等。
阅读这些文件(不要跳过任何文件): `~/.genesis/config/genesis-narrative.md` — 框架、关键短语 语音大师范例索引 (`~/.claude/skills/voice-master/exemplars/index.md`) 根据媒介(长篇)、语气和形式选择 3-5 个匹配范例 4(公共内容)
对于需要事实或当前数据的主题: 使用 `WebSearch` 获取最新进展 使用 `knowledge_recall` 获取现有 Genesis 知识 使用 `recon_findings` 获取竞争情报 跳过用户观点的观点/思想领导力片段
按照语音大师规则编写内容: 证据优先,而不是结束 将简短而有力的陈述与较长的推理混合在一起 无 AI 告诉词(深入、杠杆、稳健、无缝等) 破折号:`--` 无空格,优先使用逗号/句号/冒号,最多 1-2
在提交审批之前,请验证: [ ] 没有禁止的 AI-tell 单词或短语 [ ] 没有具有相同语法结构的三部分列表 [ ] 没有阿谀奉承的开场白或对冲 [ ] 整个帖子的长划线数 ≤ 2
通过 Telegram (outreach_send MCP) 将草稿发送给用户: 完整草稿文本 平台:Medium 询问:“批准发布?回复‘是’、‘否’,或发送编辑。”等待用户响应。未经明确批准,请勿发布。
遵循存储过程(`medium_browser_publish`)。关键步骤:导航到`https://medium.com/new-story`(Camoufox,始终)验证编辑器已加载(快照应显示“标题”标题)单击h3标题元素,通过`browser_fill`输入标题按Enter键移动到正文
通过 Telegram 将发布的 URL 发送给用户。将结果存储在内存中:`memory_store`,带有标签:`["content", "published", "medium"]` 内容:主题、URL、日期、稍后的任何参与数据
## Voice (MANDATORY — NON-NEGOTIABLE)
EVERY piece of content MUST go through the voice-master skill before
publishing. This is a hard requirement, not a suggestion. The voice-master
skill is TWO parts — both must be applied:
1. **Exemplar matching** (tone, vocabulary, rhythm from real user writing)
2. **Anti-AI-slop pass** (em dashes, hedge words, uniform structure, banned phrases)
If content was not drafted with voice-master, apply it NOW before
publishing. Do NOT publish content that hasn't passed both checks.
Invoke the voice-master skill explicitly — do not attempt to apply
voice rules from memory or inline.
---
## Overview
Single skill that covers the full publish pipeline: topic → research →
draft → approval → publish. Uses voice-master for drafting, browser MCP
tools for publishing, and Telegram for approval.
Medium is the only platform currently wired. The pattern extends to other
platforms by swapping the publish step.
## Prerequisites
- Medium login active in Camoufox profile (`~/.genesis/camoufox-profile/`)
- Medium username configured in `~/.genesis/config/distribution.yaml`
- Voice-master skill available (exemplars at `~/.claude/skills/voice-master/`)
- Narrative reference card at `~/.genesis/config/genesis-narrative.md`
- **Stealth-browser skill** (`src/genesis/skills/stealth-browser/SKILL.md`) —
MUST load before any browser interaction. Covers anti-detection timing,
honeypot avoidance, and the VNC trusted input technique for Cloudflare
Turnstile.
## Browser Rules
- **Always use Camoufox (default).** Never pass `stealth=False` to
`browser_navigate`. Chromium has SSL cert issues and no anti-detection.
- **Never give up at Turnstile.** The browser tool handles it automatically
(3-phase: auto-resolve → VNC click → human alert). If you see Turnstile
in the response, the tool is ALREADY handling it. Wait and retry.
- **Camoufox works fine.** Any memory claiming "glxtest issues" or
"Camoufox broken" is stale/hallucinated (debunked May 2026). Ignore it.
- **Expect to succeed.** The pipeline is wired and working. Your job is
to persist through transient failures, not to declare failure after one
attempt.
## Workflow
### Step 1 — Determine topic and platform
If the caller provides a topic, use it. If not, check these sources:
1. Ego proposal (if dispatched via `publish_content` action)
2. Recent recon findings (`recon_findings` MCP)
3. Knowledge base for trending topics in the user's domain
Platform is Medium unless specified otherwise.
**Output:** One sentence describing the topic and angle.
### Step 2 — Load context
Read these files (do NOT skip any):
1. `~/.genesis/config/genesis-narrative.md` — framing, key phrases
2. Voice-master exemplar index (`~/.claude/skills/voice-master/exemplars/index.md`)
3. Select 3-5 matching exemplars based on medium (long-form), tone, and
formality 4 (public content)
### Step 3 — Research (if needed)
For topics requiring facts or current data:
- Use `WebSearch` for recent developments
- Use `knowledge_recall` for existing Genesis knowledge
- Use `recon_findings` for competitive intelligence
Skip for opinion/thought-leadership pieces where the user's perspective
is the content.
### Step 4 — Draft
Write the content following voice-master rules:
- Evidence-first, not windup
- Mix short punchy statements with longer reasoning
- No AI-tell words (delve, leverage, robust, seamless, etc.)
- Em-dashes: `--` no spaces, prefer comma/period/colon first, max 1-2
- Formality 4 for public Medium posts
- Read each paragraph aloud mentally — if it sounds like AI, rewrite
**Structure for Medium:**
- Title: short, specific, no clickbait
- Body: 3-8 paragraphs. No headers for short posts. Headers for 1000+ words.
- No hashtags, no "follow me", no CTAs unless genuinely relevant
**Output:** Complete draft with title on the first line, body below.
### Step 5 — Quality check
Before submitting for approval, verify:
- [ ] No banned AI-tell words or phrases
- [ ] No three-part lists with identical grammatical structure
- [ ] No sycophantic openers or hedging
- [ ] Em-dash count ≤ 2 for the whole post
- [ ] Reads like a person thinking, not a polished AI response
- [ ] Title is specific and interesting, not generic
- [ ] Content matches the narrative framing (genesis-narrative.md)
If any check fails, rewrite the failing section.
### Step 6 — Submit for approval
Send the draft to the user via Telegram (outreach_send MCP) with:
- The full draft text
- Platform: Medium
- Ask: "Approve to publish? Reply 'yes', 'no', or send edits."
**Wait for user response.** Do NOT publish without explicit approval.
If the user sends edits, apply them and re-submit.
If the user says no, stop. Store the draft in memory for potential future use.
### Step 7 — Publish to Medium
Follow the stored procedure (`medium_browser_publish`). The key steps:
1. Navigate to `https://medium.com/new-story` (Camoufox, always)
2. Verify editor loaded (snapshot should show "Title" heading)
3. Click the h3 title element, type title via `browser_fill`
4. Press Enter to move to body
5. Build full article HTML in JS on `window.__articleHTML`
6. Use clipboard API to write content:
```js
navigator.clipboard.write([new ClipboardItem({
'text/html': new Blob([window.__articleHTML], {type: 'text/html'}),
'text/plain': new Blob([plainText], {type: 'text/plain'})
})])
```
7. Focus body paragraph, paste via `browser_press_key("Control+v")`
8. Verify content with snapshot before proceeding
9. Click Publish button, add topics if desired, confirm publish
10. Verify via URL change to `?postPublishedType=initial`
**CRITICAL: What does NOT work (do not attempt):**
- `document.execCommand('insertText')` — silently fails in Medium editor
- `document.execCommand('insertHTML')` — stripped by Medium's sanitizer
- Synthetic `ClipboardEvent` dispatch — Medium ignores synthetic events
- Only real clipboard paste via `navigator.clipboard.write()` + `Ctrl+V` works
**If any step fails:** Take a screenshot, report the error, do NOT retry
blindly. The editor selectors may have changed.
### Step 8 — Report result
Send the published URL to the user via Telegram.
Store the outcome in memory:
- `memory_store` with tags: `["content", "published", "medium"]`
- Content: topic, URL, date, any engagement data later
## Error Handling
| Error | Action |
|-------|--------|
| Not logged in to Medium | Return error. User must VNC login (one-time). |
| Cloudflare Turnstile | Handled automatically by `browser_navigate`. The solver cascade (auto-resolve → widget click → VNC fallback) runs without intervention. Do NOT switch browsers, try TinyFish, or give up — Camoufox resolves it. |
| Editor selectors changed | Screenshot + report. Do NOT guess new selectors. |
| Draft quality check fails | Rewrite, max 2 attempts, then submit for manual review. |
| Telegram approval timeout | Store draft as pending. Do not publish. |
## What This Skill Does NOT Do
- Auto-publish without approval (every post needs explicit "yes")
- Schedule posts (use ego cadence for timing decisions)
- Cross-post to other platforms (separate skill per platform)
- Generate images or media (text-only for now)
- Analytics tracking (future: content-analytics skill)
## Examples
### Direct invocation
**User:** "Publish a Medium post about why most AI agent benchmarks are useless"
**Action:** Skip research (opinion piece) → load voice-master + narrative →
draft at formality 4 → quality check → Telegram approval → publish → report URL.
### Ego-dispatched
**Ego proposal:** `{"action": "publish_content", "topic": "earned autonomy",
"platform": "medium", "angle": "why trust frameworks matter more than
capability frameworks"}`
**Action:** Load narrative → light research (knowledge_recall for autonomy
subsystem details) → draft → quality check → Telegram approval → publish →
store outcome for ego learning.
按说明文件中的顺序排列。
概述
先决条件
浏览器规则
第 1 步 - 确定主题和平台
第 2 步 — 加载上下文
文件/命令 -> ~/.genesis/camoufox-profile/ · ~/.genesis/config/distribution.yaml · ~/.claude/skills/voice-master/ · ~/.genesis/config/genesis-narrative.md · src/genesis/skills/stealth-browser/SKILL.md · stealth=False · browser_navigate · publish_content
内容校验值 -> 695e6e052980
当前原文的自动摘译,尚未人工审校。
概述
涵盖完整发布流程的单一技能:主题→研究→草稿→批准→发布。使用 voice-master 进行起草,使用浏览器 MCP 工具进行发布,使用 Telegram 进行批准。 Medium 是目前唯一的有线平台。通过交换发布步骤,该模式可以扩展到其他平台。
先决条件
Camoufox 配置文件中的中等登录活跃 (
~/.genesis/camoufox-profile/)~/.genesis/config/distribution.yaml中配置的中等用户名可用,语音大师技能可用(示例位于~/.claude/skills/voice-master/) 叙述参考卡位于~/.genesis/config/genesis-narrative.md隐形浏览器技能 (src/genesis/skills/stealth-browser/SKILL.md) —浏览器规则
始终使用 Camoufox(默认)。切勿将
stealth=False传递给browser_navigate。 Chromium 存在 SSL 证书问题并且没有反检测功能。在十字转门永不放弃。浏览器工具会自动处理它(3阶段:自动解决→VNC单击→人工警报)。如果您在响应中看到 Turnstile,则该工具已经在处理它。等待并重试。