Back to Details

x-writing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

X Writing Skill

X 写作技能

Overview

概述

Transform your notes, work updates, and observations into engaging X (Twitter) content. This skill analyzes your notes to identify the most shareable insights, then crafts authentic posts that match your voice and drive engagement.
Supports two idea sources — a markdown file (
X_SOURCE_FILE
) and/or macOS Notes (
X_NOTES_APP_SOURCE
). If both are configured, asks which to use.
将你的笔记、工作更新和观察转化为有吸引力的X（Twitter）内容。此技能会分析你的笔记，找出最适合分享的见解，然后撰写符合你个人风格、能提升互动量的真实帖子。
支持两种想法来源 —— 一个Markdown文件（
X_SOURCE_FILE
）和/或macOS备忘录（
X_NOTES_APP_SOURCE
）。如果两者都已配置，会询问使用哪一个。

Process

流程

Phase 1: Preparation and Analysis

第一阶段：准备与分析

1.1 Load Writing Guides (REQUIRED - Load First)
Before any other work, load the following:
  1. Growth Principles (
    references/x-strategy.md
    ) - Content selection criteria, what makes posts shareable, engagement patterns, and what to prioritize from notes. This guides WHAT to share.
  2. Writing Style Guide (from 
    WRITING_STYLE_GUIDE_PATH
    env var) - Voice, tone, structure, banned phrases, and signature patterns. This guides HOW to share it. Skip if the env var is not set.
  3. Anti-Patterns - Run 
    echo "$WRITING_ANTI_PATTERNS_PATH"
    to check the env var. If set, load that file. If not set, fall back to 
    references/anti-patterns.md
    . AI writing patterns to avoid. Critical for ensuring posts sound human and authentic, not AI-generated. Avoid patterns like "It's not X, it's Y", formal transitions, hedging language, and AI-specific vocabulary.
PRIORITY RULE: When guides conflict, 
references/x-strategy.md
wins. Content value and shareability take precedence over stylistic preferences. When the style guide and anti-patterns conflict, anti-patterns win.
1.2 Understand the Source Material
Get clarity on what notes to work with:
  • Ask which notes, ideas, or updates they want to transform into posts
  • Check for idea sources:
    • Run 
      echo "$X_SOURCE_FILE"
      — if set, a markdown ideas file is available
    • Run 
      echo "$X_NOTES_APP_SOURCE"
      — if set, a macOS Notes note is available (use 
      scripts/fetch-notes.sh get
      to fetch)
    • If both are configured and the user says "check my ideas" or similar without specifying, ask which source to use
    • If one is configured, use it directly
    • If neither is configured, work from whatever the user provides (pasted content, markdown files, etc.)
  • Read the source material and identify the core insights, learnings, or updates
  • Note any specific tools, projects, numbers, or details mentioned
Multiple ideas/notes workflow:
  • When the user provides multiple distinct ideas or notes, work through them ONE AT A TIME
  • Create post options for the first idea
  • Wait for user approval/feedback before moving to the next idea
  • This prevents overwhelming the user and allows for refinement as you go
1.3 Apply Selection Criteria
Evaluate notes using the Content Selection Framework in 
references/x-strategy.md
. Prioritize shipped work with learnings, non-obvious insights, and specific tool recommendations. Skip engagement bait, vague hype, and complaints without solutions.
1.1 加载写作指南（必填 - 优先加载）
在进行任何其他操作之前，先加载以下内容：
  1. 增长原则（
    references/x-strategy.md
    ）- 内容选择标准、帖子的可分享性因素、互动模式以及笔记中的优先内容。这指导了要分享什么。
  2. 写作风格指南（来自
    WRITING_STYLE_GUIDE_PATH
    环境变量）- 语气、语调、结构、禁用短语和标志性模式。这指导了如何分享。如果未设置该环境变量则跳过。
  3. 反模式 - 运行
    echo "$WRITING_ANTI_PATTERNS_PATH"
    检查环境变量。如果已设置，加载对应文件；如果未设置，默认使用
    references/anti-patterns.md
    。需要避免的AI写作模式，这对于确保帖子听起来真实自然、而非AI生成至关重要。需避免的模式包括“不是X，而是Y”的重构、正式过渡语、模糊措辞以及AI专属词汇。
优先级规则：当指南发生冲突时，
references/x-strategy.md
优先级最高。内容价值和可分享性优先于风格偏好。当风格指南与反模式冲突时，反模式优先级更高。
1.2 理解源材料
明确要处理的笔记内容：
  • 询问用户想要将哪些笔记、想法或更新转化为帖子
  • 检查想法来源：
    • 运行
      echo "$X_SOURCE_FILE"
      —— 如果已设置，则存在一个Markdown想法文件
    • 运行
      echo "$X_NOTES_APP_SOURCE"
      —— 如果已设置，则存在一个macOS备忘录笔记（使用
      scripts/fetch-notes.sh get
      获取）
    • 如果两者都已配置，且用户仅说“查看我的想法”等未明确指定的内容，询问使用哪个来源
    • 如果仅配置了一个，直接使用该来源
    • 如果都未配置，使用用户提供的任何内容（粘贴的文本、Markdown文件等）
  • 阅读源材料，识别核心见解、经验或更新
  • 记录提到的特定工具、项目、数字或细节
多想法/笔记工作流：
  • 当用户提供多个不同的想法或笔记时，逐一处理
  • 为第一个想法创建帖子选项
  • 等待用户的批准/反馈后再处理下一个想法
  • 这样可以避免使用户感到不知所措，并允许逐步优化
1.3 应用选择标准
使用
references/x-strategy.md
中的内容选择框架评估笔记。优先选择包含经验的已完成工作、非显而易见的见解以及特定工具推荐。跳过互动诱饵、模糊炒作和无解决方案的抱怨。

Phase 2: Content Creation

第二阶段：内容创作

2.1 Select the Best Angle
Identify one clear idea, the specific details that prove it, and the hook (first line).
2.2 Choose the Format
Default to single tweets. Only thread (2-5 tweets) when the story requires steps, multiple related insights, or before/after context. See Thread Strategy in 
references/x-strategy.md
.
2.3 Draft the Content
Apply all three guides loaded in Phase 1 during drafting, not just as a post-check:
  • x-strategy.md — formatting rules, content strategy, High-Engagement Patterns, and Signature Patterns. Formatting is critical: one sentence per line, white space between lines, hook in first line, 180-250 chars, no italics.
  • Writing style guide (
    WRITING_STYLE_GUIDE_PATH
    ) — voice, tone, banned phrases, language simplification. Apply casing preference from X_CASE_STYLE env var (standard by default). When set to 
    "lowercase"
    , use all lowercase including "i" as a pronoun — only capitalize personal names, WordPress, and product names.
  • Anti-patterns — actively avoid during drafting. If a draft uses any anti-pattern, rewrite before presenting. HARD RULE: NEVER use the "It's not X, it's Y" reframing pattern in any form. This includes: "isn't X, it's Y", "not because X, because Y", "isn't about X, it's about Y", "less about X, more about Y". Say the positive claim directly instead. Also avoid: em dashes, generic observations without specifics, and intensifiers.
2.4 Engagement Optimization
End ~70% of posts with engagement (specific question, teaser, or invitation). Let the rest land with a hard stop. See "What Makes Content Shareable" in 
references/x-strategy.md
.
2.5 Quality Check
After drafting, re-read every post against the anti-patterns guide and fix any violations before presenting. Then verify:
  • Did I get to the point in line 1?
  • Is this specific? (names, numbers, examples)
  • Would I actually say this out loud?
  • Does it sound like ME, not ChatGPT?
  • Did I use any banned phrases from the writing style guide?
  • Did I avoid ALL anti-patterns? (reframing, em dashes, intensifiers, generic observations)
  • If it's a reaction, did I add MY angle?
2.1 选择最佳角度
确定一个清晰的想法、支撑该想法的具体细节以及钩子（第一行内容）。
2.2 选择格式
默认使用单条推文。仅当内容需要分步说明、多个相关见解或前后对比背景时，才使用推文串（2-5条推文）。详情请见
references/x-strategy.md
中的推文串策略。
2.3 起草内容
在起草过程中而非仅作为事后检查应用第一阶段加载的所有三个指南：
  • x-strategy.md —— 格式规则、内容策略、高互动模式和标志性模式。格式至关重要：每行一个句子、行间距留白、第一行是钩子、长度180-250字符、无斜体。
  • 写作风格指南（
    WRITING_STYLE_GUIDE_PATH
    ）—— 语气、语调、禁用短语、语言简化。应用
    X_CASE_STYLE
    环境变量指定的大小写偏好（默认标准格式）。当设置为
    "lowercase"
    时，所有内容均使用小写，包括代词“i”——仅人名、WordPress和产品名保留大写。
  • 反模式 —— 起草时主动避免。如果草稿使用了任何反模式，在呈现前重写。硬性规则：绝不使用任何形式的“不是X，而是Y”重构模式。包括：“不是X，而是Y”、“不是因为X，而是因为Y”、“不是关于X，而是关于Y”、“更少关于X，更多关于Y”。直接说出正面主张即可。此外还需避免：破折号、无具体内容的泛泛观察以及强化词。
2.4 互动优化
约70%的帖子以互动引导结尾（具体问题、预告或邀请）。其余帖子可直接收尾。详情请见
references/x-strategy.md
中的“什么让内容更具可分享性”部分。
2.5 质量检查
起草完成后，对照反模式指南重新阅读每篇帖子，修复所有违规内容，然后再进行验证：
  • 第一行是否直接点题？
  • 内容是否具体？（有名称、数字、示例）
  • 我实际会这样说吗？
  • 听起来像我，而不是ChatGPT？
  • 是否使用了写作风格指南中的禁用短语？
  • 是否避免了所有反模式？（重构、破折号、强化词、泛泛观察）
  • 如果是回应内容，是否添加了我的个人角度？

Phase 3: Output

第三阶段：输出

3.1 Present the Content
For each post created:
  1. The Post(s) - Show the actual tweet(s) ready to copy/paste
  2. Format - Indicate if it's a single tweet or thread
  3. Character Count - Show length (target: 180-250 chars)
  4. Pattern Used - Which pattern from x-strategy.md was applied
  5. Key Elements - What specifics, tools, or projects were highlighted
3.2 Offer Options
When appropriate, provide 2-3 variations:
  • Different angles on the same insight
  • Single tweet vs thread format
  • Different engagement endings
3.3 Explain Selections
Briefly note what was prioritized and why:
  • Which insights from notes were selected
  • Why certain details were emphasized
  • What was intentionally left out
3.4 Save Approved Posts
When the user approves a post, save it to the drafts file (create if missing).
File location (resolve before saving):
  1. Run 
    echo "$X_DRAFTS_FILE"
    to check the env var
  2. If set, append to that file path
  3. If not set, default to 
    .x/posts.md
    (top-level, create if missing)
Markdown format:
markdown
---

**Category:** Learning
**Date:** 2026-01-01

WordPress.com AI adds conversation alongside block editing.


People who couldn't navigate the UI before are shipping sites now. Others still use blocks for fine-tuning.

Both work. The conversation path just removes the skill barrier.

---
For threads, use 
[Tweet N]
markers:
markdown
---

**Category:** Learning
**Date:** 2026-01-01

[Tweet 1]
WordPress.com AI changes how people build sites.


[Tweet 2]
People who couldn't navigate block editing are shipping now.

[Tweet 3]
The UI is still there for fine-tuning. But conversation removes the skill barrier.

[Tweet 4]
Ask or click. Both paths work.

---
Categories:
  • Learning - Insights, shipped updates with learnings
  • Update - Project progress
  • Tool - Recommendations
  • Observation - Industry takes
Workflow:
  1. Present the post(s) to the user
  2. When approved, append to 
    X_DRAFTS_FILE
    or 
    .x/posts.md
  3. User can copy-paste directly into X (text is ready with proper line breaks)
  4. User removes the section after posting, or asks you to remove it
3.1 呈现内容
对于创建的每篇帖子：
  1. 帖子内容 - 展示可直接复制粘贴的推文内容
  2. 格式 - 标明是单条推文还是推文串
  3. 字符数 - 显示长度（目标：180-250字符）
  4. 使用的模式 - 应用了x-strategy.md中的哪种模式
  5. 核心元素 - 突出了哪些具体内容、工具或项目
3.2 提供选项
适当时提供2-3种变体：
  • 同一见解的不同角度
  • 单条推文 vs 推文串格式
  • 不同的互动结尾
3.3 解释选择理由
简要说明优先选择的内容及原因：
  • 从笔记中选择了哪些见解
  • 为什么强调某些细节
  • 故意省略了哪些内容
3.4 保存已批准的帖子
当用户批准帖子后，将其保存到草稿文件（如果不存在则创建）。
文件位置（保存前确认）：
  1. 运行
    echo "$X_DRAFTS_FILE"
    检查环境变量
  2. 如果已设置，追加到该文件路径
  3. 如果未设置，默认保存到
    .x/posts.md
    （顶层目录，不存在则创建）
Markdown格式：
markdown
---

**Category:** Learning
**Date:** 2026-01-01

WordPress.com AI adds conversation alongside block editing.


People who couldn't navigate the UI before are shipping sites now. Others still use blocks for fine-tuning.

Both work. The conversation path just removes the skill barrier.

---
推文串格式，使用
[Tweet N]
标记：
markdown
---

**Category:** Learning
**Date:** 2026-01-01

[Tweet 1]
WordPress.com AI changes how people build sites.


[Tweet 2]
People who couldn't navigate block editing are shipping now.

[Tweet 3]
The UI is still there for fine-tuning. But conversation removes the skill barrier.

[Tweet 4]
Ask or click. Both paths work.

---
分类：
  • Learning - 见解、包含经验的已完成更新
  • Update - 项目进展
  • Tool - 工具推荐
  • Observation - 行业观点
工作流：
  1. 向用户展示帖子
  2. 获得批准后，追加到
    X_DRAFTS_FILE
    或
    .x/posts.md
  3. 用户可直接复制粘贴到X（文本已设置好正确的换行）
  4. 用户发布后可删除该部分，或要求你删除

Output Format

输出格式

After creating social content, provide:
📱 Post 1 (Single Tweet, 210 chars)
─────────────────────────────────
[Actual tweet text ready to copy/paste]

Pattern: "Shipped X, learned Y"
Specifics: agents.foo, conversational context matching
Engagement: Specific question

─────────────────────────────────

From your notes, I prioritized:
✓ The discovery insight (most shareable)
✓ Why traditional search failed (specific learning)
✗ Timeline details (not core value)

Alternative angles:
• Focus on the technical implementation
• Thread breaking down the 3 attempts
创建社交内容后，按以下格式提供：
📱 帖子1（单条推文，210字符）
─────────────────────────────────
[可直接复制粘贴的推文文本]

模式：“完成X，学到Y”
具体内容：agents.foo、对话上下文匹配
互动引导：具体问题

─────────────────────────────────

从你的笔记中，我优先选择了：
✓ 发现类见解（最具可分享性）
✓ 传统搜索失败的原因（具体经验）
✗ 时间线细节（非核心价值）

替代角度：
• 聚焦技术实现
• 用推文串拆解3次尝试

Example Interaction

示例交互

User: "Help me create a post from these notes about building the curation feature"
Response:
Let me analyze your notes and create X content.

[Phase 1: Loads references/x-strategy.md and writing style guide]
[Reads the notes, identifies key insights and specific details]

─────────────────────────────────
📱 Post (Single Tweet, 218 chars)
─────────────────────────────────

Shipped curation v1 for agents.foo today.

Discovery is way harder than app stores. Agents are conversations, not static features.

Had to rebuild around context matching instead of keyword search.

Pattern: "Shipped X, learned Y"
Key specifics: agents.foo, context matching vs keyword search
Engagement: Implicit (landing the insight)

─────────────────────────────────

From your notes, I selected:
✓ Core insight: agent discovery is different
✓ Specific solution: context matching
✓ Concrete detail: agents.foo
✗ Number of rebuild attempts (not essential to the insight)

Would you like me to:
• Save this approved post for tracking
• Create a thread version breaking down why search patterns failed
• Add a question ending for more engagement
• Draft additional posts from other insights in your notes
用户：“帮我从这些关于构建精选功能的笔记中创建一篇帖子”
回复：
我将分析你的笔记并创建X内容。

[第一阶段：加载references/x-strategy.md和写作风格指南]
[阅读笔记，识别核心见解和具体细节]

─────────────────────────────────
📱 帖子（单条推文，218字符）
─────────────────────────────────

今日为agents.foo推出精选功能v1版本。

发现功能比应用商店难得多。Agent是对话式的，而非静态功能。

不得不围绕上下文匹配而非关键词搜索重构。

模式：“完成X，学到Y”
核心细节：agents.foo、上下文匹配vs关键词搜索
互动引导：隐含式（传递见解）

─────────────────────────────────

从你的笔记中，我选择了：
✓ 核心见解：Agent发现与众不同
✓ 具体解决方案：上下文匹配
✓ 具体细节：agents.foo
✗ 重构尝试次数（对非核心见解）

你希望我：
• 保存这篇已批准的帖子以便追踪
• 创建拆解搜索模式失败原因的推文串版本
• 添加问题结尾以提升互动量
• 从笔记中的其他见解起草更多帖子

Tips for Best Results

最佳实践提示

  1. Provide context: "Notes from building curation feature" vs just pasting notes
  2. Mention specific parts: "Focus on the learning about context matching" helps prioritize
  3. Indicate quantity: "Create 3 posts from these notes" vs "create posts"
  4. Specify format preference: "Single tweets only" or "open to threads"
  5. Request variations: "Show me a few angles" gives options to choose from
  6. Iterate: After the draft, request adjustments: "Make it more specific" or "Add a question ending"
  1. 提供上下文：“关于构建精选功能的笔记”比直接粘贴笔记效果更好
  2. 指定重点：“聚焦关于上下文匹配的经验”有助于优先处理内容
  3. 说明数量：“从这些笔记中创建3篇帖子”比“创建帖子”更明确
  4. 指定格式偏好：“仅单条推文”或“接受推文串”
  5. 请求变体：“展示几个不同角度”可提供更多选择
  6. 迭代优化：草稿完成后，可要求调整：“更具体些”或“添加问题结尾”

Environment Variables

环境变量

VariableRequiredDescription
WRITING_STYLE_GUIDE_PATH
NoPath to shared writing style guide. Loaded in Phase 1.1
WRITING_ANTI_PATTERNS_PATH
NoPath to shared anti-patterns. Overrides 
references/anti-patterns.md
X_DRAFTS_FILE
NoFile path for saving approved posts. Default: 
.x/posts.md
X_SOURCE_FILE
NoPath to a markdown file containing post ideas. Read when the user asks to check ideas.
X_NOTES_APP_SOURCE
NomacOS Notes note name to fetch ideas from (e.g. 
"Tweets"
). Uses 
scripts/fetch-notes.sh
.
X_CASE_STYLE
No
"standard"
(default) or 
"lowercase"
变量是否必填描述
WRITING_STYLE_GUIDE_PATH
否共享写作风格指南的路径。在第一阶段1.1加载
WRITING_ANTI_PATTERNS_PATH
否共享反模式文件的路径。覆盖
references/anti-patterns.md
X_DRAFTS_FILE
否保存已批准帖子的文件路径。默认：
.x/posts.md
X_SOURCE_FILE
否包含帖子想法的Markdown文件路径。当用户要求查看想法时读取
X_NOTES_APP_SOURCE
否要从中获取想法的macOS备忘录名称（例如
"Tweets"
）。使用
scripts/fetch-notes.sh
脚本。
X_CASE_STYLE
否
"standard"
（默认）或
"lowercase"