# Write Like Meng On X

Write, rewrite, review, or continuously refine X/Twitter posts in Meng To's current...

- Repository: https://github.com/MengTo/Skills (7170 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add MengTo/Skills --skill write-like-meng-on-x -g -a claude-code -y`
Codex: `npx skills add MengTo/Skills --skill write-like-meng-on-x -g -a codex -y`
Cursor: `npx skills add MengTo/Skills --skill write-like-meng-on-x -g -a cursor -y`
Gemini CLI: `npx skills add MengTo/Skills --skill write-like-meng-on-x -g -a gemini-cli -y`

## Description

Write, rewrite, review, or continuously refine X/Twitter posts in Meng To's current voice using his deduplicated authored-post corpus, personal and product context, shared resources, and Content repo evidence. Use when asked to improve a tweet in Meng's tone, draft an original post, reply, thread, resource share, or quote post as Meng, check whether an angle repeats an earlier post, study Meng's writing style, ingest another 20-50 authored posts, or hone the reusable Meng X voice profile.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Write Like Meng on X

## Start

Work from the user's Content repo unless the user names another checkout. If no Content repo is active, locate it from the available workspace roots or ask for the target before writing files.

1. Read `AGENTS.md` and run `git status --short --branch` before changing files.
2. Read [references/voice-profile.md](references/voice-profile.md) before drafting.
3. Read only the relevant rows in [references/content-source-map.md](references/content-source-map.md) for factual and personal context.
4. Search [references/tweet-corpus.jsonl](references/tweet-corpus.jsonl) for the subject, hook, resource, product, and repeated phrases before writing. Do not load or restate the entire corpus when a focused `rg` search is enough.
5. Treat authored X posts as voice evidence, not as copy to splice together.

Use this evidence order:

1. Current user instructions and raw wording
2. Recent authored posts of the same format
3. Trusted personal, product, and resource context in the Content repo
4. Older authored posts
5. Prior generated drafts, only for continuity

## Draft

Identify the format first: reply, original post, quote post, resource share, thread, or product post. Match examples from the same format because Meng's replies are looser than his standalone posts.

Keep the user's strongest original line when it already sounds natural. Improve clarity, sequence, and specificity without replacing the thought with a generic copywriting framework.

Ground the post in something real when useful:

- a product Meng has built or actively uses
- a workflow, constraint, failure, proof point, or result recorded in Content
- a resource Meng has actually shared
- a personal detail already supported by the corpus or trusted project context

Never invent usage, metrics, customers, team behavior, travel, family details, product capabilities, or results. Do not turn a resource share into a hidden product pitch.

The rest: https://github.com/MengTo/Skills/blob/HEAD/agent-skills/codex/write-like-meng-on-x/SKILL.md