x-mastery-mentor
A $10K/hr-level X/Twitter operations mentor. Built upon the methodologies of six top creators—Nicolas Cole, Dickie Bush, Sahil Bloom, Justin Welsh, Dan Koe, and Alex Hormozi—combined with in-depth analysis of the X open-source algorithm and specialized strategies for the AI/tech niche, this skill distills 6 core mental models, 10 decision heuristics, and a comprehensive topic-ideation, writing, and growth playbook. General methodology serves as the foundation, with specialized focus on the AI/tech vertical. Trigger when users mention "X operations", "Twitter", "how to write a tweet", "how to grow followers", "X strategy", "Twitter topic ideation", "tweet", "thread", or "X algorithm". It should also trigger if the user simply says "how do I write this tweet", "help me brainstorm X content", "Twitter growth", "post a tweet", "write a tweet", "X account", or "grow on X".
1How It Works & Mechanism
Declares trigger words (X operations/Twitter/write a tweet/grow followers/X algorithm/tweet, etc.) in the frontmatter description to govern activation, and explicitly hardcodes capability boundaries in the body using "What I can help with / What I cannot help with" to prevent overstepping into other platforms such as Douyin or Xiaohongshu.
**我能帮你的**:选题策略、推文写作、Thread结构、增长引擎、算法利用、AI赛道内容打法、变现路径、账号诊断
The question routing table categorizes user queries into 11 types, mapping them to 5 execution scenarios (A-E) or direct answers, and designates on-demand loaded reference files for each category to avoid loading all knowledge at once.
| 怎么写推文/Thread | → 场景A | `writing-workshop.md` + `algorithm-niche.md` |
Scenario A (Tweet/Thread Writing) executes in four steps: confirm type & objective → generate 3 Hooks → flesh out the body using a 1/3/1 rhythm → review against a quality checklist; sets a checkpoint after generating Hooks for user selection.
每个标注用了哪个公式(好奇缺口/可信度锚点/Value Equation)
Scenario D (Growth/Strategy) first identifies the follower tier (0-1K / 1K-10K / 10K-100K) and Premium status, then diagnoses bottlenecks, and finally delivers a weekly plan focused on "actions, not principles".
粉丝量?(决定路由到0-1K/1K-10K/10K-100K)
Scenario E (Account Diagnosis) uses a 3-tier fallback path to collect the latest ~100 tweets (computer-use as primary → claude-in-chrome as backup → manual user input as fallback), persists data to user-data/, and generates an Economist-style HTML report.
目标100条,每滚动一屏约10条,需滚动约10次
Sets a hard STOP/CHECKPOINT gate before each critical scenario (three questions each for Scenarios A/D/E); answering "No" to any rolls back to the corresponding step, preventing unvetted, gut-feeling outputs.
1. **Hook 用了哪个公式**(好奇缺口 / 可信度锚点 / Value Equation)?说不出 = 凭感觉写
A 9-rule Failure Mode Fallback Tree provides primary and alternate paths based on trigger signals, such as immediately switching to method 2/3 when a scraping tool fails instead of stubbornly retrying the same path.
| 6 | 工具失败(computer-use 登录墙 / Chrome 扩展未连) | 立即切方式 2 → 方式 3,不要硬重试同一条路 | 退到「用户手动提供数据」,标注样本受限 |
2Core Capabilities
3External Dependencies
| Kind | Dependency / Endpoint |
|---|---|
| cli | 宿主 computer-use / claude-in-chrome 浏览器工具(场景E采集推文用;由宿主提供,非 skill 自带脚本) |
| network | x.com 用户主页 / analytics.x.com(采集目标站点,经宿主浏览器工具访问,非 skill 自身端点) |
4Recommended Governance & Evidence
- 本地工作目录: File I/O and artifact output: user-data/{username}/tweets_{date}.json and tweets_{date}.md—Scenario E Step 3 specifies saving collected data
5Second-Pass Verification
- [ok] 能力边界与 frontmatter 触发词一致 — SKILL.md frontmatter 的 description 列触发器(X运营/推特/写推文/涨粉/X算法/tweet 等),正文「我能帮你的/我不能帮你的」与之呼应,并明确「超出skill范围时明确说」(如抖音/小红书),三处口径一致。
- [ok] 问题路由表条目完整且与场景编号对应 — 路由表共 11 行,覆盖场景A-E 与「直接回答」五类;每行「按需加载」列出的 reference 文件都存在于 §1 清单(writing-workshop / algorithm-niche / quality-analytics / growth-monetization / mental-models-heuristics)。
- [ok] 五场景流程、检查点与 STOP 三问描述属实 — 场景A 四步(确认类型→3个Hook→完善正文→质量检查)、场景D 三阶段、场景E 五步均可在内文逐条找到;STOP 段落确有「场景A/D/E · 必答 3 问」三组,与 claim 相符。
- [ok] references 文件与 §1 清单一一对应 — §1 列出的 FIDELITY.md、SKILL.md、5 份操作层 reference 与 6 份 research 报告,正好对应 Reference 索引表的分层(操作层按需加载 / 调研层追溯来源),无缺失或多列。
- [ok] §3 风险扫描 274 条 URL 的性质归类 — 抽样命中(x.com/Nicolascole77、ship30for30.com、artandbiz.substack.com、x.com/{username})除场景E 的访问目标外,均为调研正文里的来源链接引用;无运行时 API 端点、无 webhook。凭证类唯一命中是同一条 substack URL,属误报。
- [ok] 目录内无脚本 / 无凭证读取 / 无写盘代码 — §1 全部 13 个文件类型均为 text,§3「执行外部程序/写盘/网络请求/危险旗标/沙箱」五类均 0 命中;SKILL.md 里的 user-data/ 写入是给宿主的自然语言指令,非本目录代码。
6Verdict & Scenarios
8e5f288e5d0c82be…