X Master Skill — Master Routing for X/Twitter Operations
This skill is the single entry point for all X/Twitter work. Read it first, then route to the correct sub-tool based on your task. Never attempt raw x.com fetches. Never guess at routing.
⚠️ ABSOLUTE RULE: Never fetch x.com directly
Direct web_fetch of x.com or twitter.com URLs will fail silently or return garbage.
Always use fxtwitter for reading tweet content:
CODEBLOCK0
Extract username and tweet_id from the x.com URL:
- -
https://x.com/example/status/1234567890 → INLINECODE4 - INLINECODE5 → same pattern
This is a hard rule. No exceptions. See references/fxtwitter-pattern.md for full details.
Account Configuration
This skill routes posting operations to one or more X accounts. Before using, configure your target account(s):
| Configuration | What It Means | Approval Required? |
|---|
| Single account | All posts go to one account | Yes — always. Get human approval before posting. |
| Multiple accounts |
Route based on content type | Yes — always. Confirm account + text before posting. |
| Draft-only mode | Generate drafts, never auto-post | Recommended for new users. Learn the flow first. |
Golden rule: Never post autonomously to X. Always draft first, get human approval before publishing.
Posting flow:
- 1. Draft the post in your voice
- Share draft with the human for approval (via chat, email, or local review)
- Only after approval: execute posting script
- Log the URL and confirmation
Task Router
1. Read a tweet or thread by URL
Tool: fxtwitter API via
web_fetch
When: You have an x.com/twitter.com link and need to read the content
How:
web_fetch("https://api.fxtwitter.com/{username}/status/{id}")
Response includes: full text, author, engagement stats, media URLs, thread context via INLINECODE8
If fxtwitter is unavailable (5xx errors or timeout): fall back to x-research-skill for tweet content retrieval.
2. Search X for real-time opinions or discourse
Tool: xai-grok-search skill
When: "What are people saying about X", "search X for Y", real-time pulse check, breaking news context
Notes:
- - Responses may take 30–60s (involves reasoning)
- Results include citations with URLs
- Use for real-time social sentiment
3. Deep X research — threads, profiles, discourse
Tool: x-research-skill
When: Need to research a topic across many tweets, follow a conversation, understand discourse depth, or cache results
Supports: Filtering by handle, sorting by engagement, saving results for reuse
4. Multi-platform trend research (last 30 days)
Tool: last30days-skill
When: "What's trending about X topic", understanding broader cultural moments across Reddit + X + HN + YouTube
Triggers: Trend research requests, topic popularity analysis
5. Post a tweet, reply, or quote tweet
Tool: Custom posting script (see Setup)
When: Any posting action. Always requires human approval first.
Posting flow:
- 1. Draft the tweet in your voice
- Share draft with human for approval
- After approval: execute posting script
- Log the URL in your conversation/record
Never skip the approval step. Even if you think you have permission, confirm the exact text before executing.
6. Handle mentions / replies to your account
Tool: x-engage skill
When: Your account receives a mention, reply, or engagement
Notes:
- - Drafts replies automatically
- Always get human approval before posting
- Provides thread context for informed responses
7. Direct X API v2 calls
Tool: xurl skill (or your configured X API client)
When: Specific API operations — follower management, analytics, batch operations, anything not covered above
Requires: X OAuth configured in your environment
Decision Tree (Quick Reference)
CODEBLOCK2
Key Resources
| Resource | Location | Purpose |
|---|
| fxtwitter pattern | INLINECODE15 | How and why to use fxtwitter; error handling |
| Algorithm intelligence |
references/algo-intel.md | 2026 X ranking signals, engagement weights, strategy |
| Skill dependencies | README.md § Sub-Skills | What to install and when |
| Account config template |
config/accounts.json.example | Starting point for posting setup |
| Posting script |
scripts/x-post.js (if bundled) | Executes approved posts |
| xurl skill docs |
~/.openclaw/skills/xurl/ or clawhub | Direct X API v2 access |
| x-engage skill docs |
~/.openclaw/skills/x-engage/ or clawhub | Mention handling pipeline |
What Was Deprecated / Removed from X Tooling
If you're migrating from older X agent setups, be aware:
| Tool/Pattern | Status | Replacement |
|---|
| Herald/Barker agent | Deprecated — purpose-built X agents are fragile | x-engage skill handles mentions |
| x-twitter-api npm package |
Deleted — third-party duplicate | xurl (first-party) |
| x-react.js / x-poll.js | Archived — standalone reaction scripts | Covered by xurl |
| Direct x.com web_fetch | Never worked reliably | fxtwitter (mandatory) |
Algorithm Intelligence (Updated 2026-03-13)
For full details, see references/algo-intel.md
Key Takeaways
- - Engagement hierarchy: Replies (27x) and conversations (150x) beat likes (human accounts — see note below)
- Velocity window: Posts live or die in first 30 minutes
- Content format: Native video > threads > articles > images > text
- Account signals: X Premium, verification, consistency matter
- Posting frequency: >5x/day triggers suppression
⚠️ Bot/AI account note: Engagement weights above apply to human accounts. AI assistant or bot accounts are weighted differently by the algorithm. See references/algo-intel.md § "Strategy by Account Type" for bot-specific guidance.
⚠️ Freshness: Algorithm data last verified 2026-03-13. If today is past 2026-06-13, check references/algo-intel.md for a newer version before relying on specific weights.
For Best Results
- - Lead with video (15–30s, captions, motion hook)
- Reply to your own posts within 15 minutes of publishing
- Post at your audience's peak times
- Engagement pods and clickbait are algorithmically penalized
This skill was created for AI agents to route X/Twitter work correctly. Adapt the account routing and approval flow to your needs, but keep the fxtwitter rule and task router structure unchanged.
Version: 1.0.0 | License: MIT
X Master 技能 — X/Twitter 操作的主路由
本技能是所有 X/Twitter 工作的单一入口点。请先阅读此文档,然后根据您的任务路由到正确的子工具。切勿尝试原始 x.com 抓取。切勿猜测路由。
⚠️ 绝对规则:切勿直接抓取 x.com
直接对 x.com 或 twitter.com URL 进行 web_fetch 将静默失败或返回垃圾数据。
始终使用 fxtwitter 读取推文内容:
https://api.fxtwitter.com/{username}/status/{tweet_id}
从 x.com URL 中提取 username 和 tweet_id:
- - https://x.com/example/status/1234567890 → api.fxtwitter.com/example/status/1234567890
- https://twitter.com/example/status/1234567890 → 相同模式
这是硬性规则,没有例外。详见 references/fxtwitter-pattern.md。
账户配置
本技能将发布操作路由到一个或多个 X 账户。使用前,请配置您的目标账户:
| 配置 | 含义 | 是否需要批准? |
|---|
| 单一账户 | 所有帖子发到一个账户 | 是 — 始终需要。发布前必须获得人工批准。 |
| 多账户 |
根据内容类型路由 | 是 — 始终需要。发布前确认账户和文本。 |
| 仅草稿模式 | 生成草稿,从不自动发布 | 推荐新用户使用。先熟悉流程。 |
黄金规则: 切勿自主向 X 发布内容。始终先起草,发布前获得人工批准。
发布流程:
- 1. 以您的语气起草帖子
- 将草稿分享给人工审批(通过聊天、邮件或本地审查)
- 仅在批准后:执行发布脚本
- 记录 URL 和确认信息
任务路由器
1. 通过 URL 读取推文或帖子串
工具: 通过 web_fetch 的 fxtwitter API
时机: 您有 x.com/twitter.com 链接并需要读取内容
方法:
web_fetch(https://api.fxtwitter.com/{username}/status/{id})
响应包含: 完整文本、作者、互动统计、媒体 URL、通过 reply_to 的帖子串上下文
如果 fxtwitter 不可用(5xx 错误或超时):回退到 x-research-skill 获取推文内容。
2. 搜索 X 获取实时观点或讨论
工具: xai-grok-search 技能
时机: 人们怎么说 X、搜索 X 上的 Y、实时脉搏检查、突发新闻背景
注意:
- - 响应可能需要 30–60 秒(涉及推理)
- 结果包含带 URL 的引用
- 用于实时社交情绪
3. 深度 X 研究 — 帖子串、个人资料、讨论
工具: x-research-skill
时机: 需要跨多条推文研究某个主题、跟踪对话、了解讨论深度或缓存结果
支持: 按用户名过滤、按互动排序、保存结果以供复用
4. 多平台趋势研究(最近 30 天)
工具: last30days-skill
时机: X 主题有什么趋势、了解 Reddit + X + HN + YouTube 上更广泛的文化时刻
触发: 趋势研究请求、主题热度分析
5. 发布推文、回复或引用推文
工具: 自定义发布脚本(参见设置)
时机: 任何发布操作。始终需要人工批准。
发布流程:
- 1. 以您的语气起草推文
- 将草稿分享给人工审批
- 批准后:执行发布脚本
- 在对话/记录中记录 URL
切勿跳过审批步骤。 即使您认为已获得许可,也请在执行前确认确切文本。
6. 处理提及/回复您的账户
工具: x-engage 技能
时机: 您的账户收到提及、回复或互动
注意:
- - 自动起草回复
- 发布前始终获得人工批准
- 提供帖子串上下文以便做出知情回复
7. 直接 X API v2 调用
工具: xurl 技能(或您配置的 X API 客户端)
时机: 特定 API 操作 — 粉丝管理、分析、批量操作、上述未涵盖的任何内容
要求: 在您的环境中配置 X OAuth
决策树(快速参考)
有 x.com URL?
→ 读取:fxtwitter(切勿直接 web_fetch)
需要搜索 X 上的讨论?
→ 实时脉搏:xai-grok-search
→ 深度帖子串上下文:x-research-skill
→ 跨平台最近 30 天:last30days-skill
需要发布/回复?
→ 起草 → 获得人工批准 → 执行脚本
收到提及/回复?
→ x-engage(生成草稿,等待批准)
需要原始 API 访问?
→ xurl 或您配置的 X API 客户端
关键资源
| 资源 | 位置 | 用途 |
|---|
| fxtwitter 模式 | references/fxtwitter-pattern.md | 如何使用 fxtwitter 及原因;错误处理 |
| 算法情报 |
references/algo-intel.md | 2026 年 X 排名信号、互动权重、策略 |
| 技能依赖 | README.md § 子技能 | 安装什么及何时安装 |
| 账户配置模板 | config/accounts.json.example | 发布设置的起点 |
| 发布脚本 | scripts/x-post.js(如果捆绑) | 执行已批准的帖子 |
| xurl 技能文档 | ~/.openclaw/skills/xurl/ 或 clawhub | 直接 X API v2 访问 |
| x-engage 技能文档 | ~/.openclaw/skills/x-engage/ 或 clawhub | 提及处理管道 |
已弃用/移除的 X 工具
如果您正在从旧的 X 代理设置迁移,请注意:
| 工具/模式 | 状态 | 替代方案 |
|---|
| Herald/Barker 代理 | 已弃用 — 专用 X 代理很脆弱 | x-engage 技能处理提及 |
| x-twitter-api npm 包 |
已删除 — 第三方重复 | xurl(第一方) |
| x-react.js / x-poll.js | 已归档 — 独立反应脚本 | 由 xurl 覆盖 |
| 直接 x.com web_fetch | 从未可靠工作 | fxtwitter(强制) |
算法情报(更新于 2026-03-13)
完整详情见 references/algo-intel.md
关键要点
- - 互动层级: 回复(27 倍)和对话(150 倍)优于点赞 (人工账户 — 见下方说明)
- 速度窗口: 帖子在前 30 分钟内决定生死
- 内容格式: 原生视频 > 帖子串 > 文章 > 图片 > 文本
- 账户信号: X Premium、认证、一致性很重要
- 发布频率: >5 次/天会触发压制
⚠️ 机器人/AI 账户说明: 上述互动权重适用于人工账户。AI 助手或机器人账户的算法权重不同。关于机器人特定指导,请参见 references/algo-intel.md § 按账户类型的策略。
⚠️ 时效性: 算法数据最后验证于 2026-03-13。如果今天晚于 2026-06-13,请在依赖特定权重前检查 references/algo-intel.md 是否有更新版本。
最佳实践
- - 以视频开头(15–30 秒、字幕、动态钩子)
- 在发布后 15 分钟内回复自己的帖子
- 在受众高峰时段发布
- 互动群和点击诱饵会受到算法惩罚
本技能旨在帮助 AI 代理正确路由 X/Twitter 工作。根据您的需求调整账户路由和审批流程,但保持 fxtwitter 规则和任务路由器结构不变。
版本:1.0.0 | 许可证:MIT