write-like-meng-on-x
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
Install / Use
npx skills add MengTo/Skills --skill write-like-meng-on-xInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of write-like-meng-on-x
write-like-meng-on-x scores 93/100 on our quality scale, 200th of 1,155 Content & Media skills we index (top 18%).
Its SKILL.md is 7.7 KB long, well organised into 9 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 6,252 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so write-like-meng-on-x is actively maintained.
- Our last check on 2026-10-26 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
write-like-meng-on-x compared with similar skills
All 4 of these similar skills score higher than write-like-meng-on-x; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| write-like-meng-on-x (this skill)by MengTo | 93 | 6.3k | 54d ago | SKILL.md |
| LocalAIby mudler | 100 | 50.4k | today | MCP Server |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install write-like-meng-on-x?
- Run
npx skills add MengTo/Skills --skill write-like-meng-on-x. The install tabs above show the steps for each supported agent. - Which AI agents does write-like-meng-on-x work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is write-like-meng-on-x safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is write-like-meng-on-x still maintained?
- The repository was last updated about 2 months ago, so write-like-meng-on-x is actively maintained.
Skill content
View source on GitHubname: write-like-meng-on-x 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.
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.
- Read
AGENTS.mdand rungit status --short --branchbefore changing files. - Read references/voice-profile.md before drafting.
- Read only the relevant rows in references/content-source-map.md for factual and personal context.
- Search 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
rgsearch is enough. - Treat authored X posts as voice evidence, not as copy to splice together.
Use this evidence order:
- Current user instructions and raw wording
- Recent authored posts of the same format
- Trusted personal, product, and resource context in the Content repo
- Older authored posts
- 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.
For every rewrite or drafting request, return exactly five finished options unless the user explicitly requests another count. Put the strongest option first. Make the five options materially different in angle, structure, rhythm, or intent instead of producing five surface-level paraphrases.
Adapt the remix mix to the post, using distinct types such as:
- Closest polish that preserves the user's original thought and phrasing
- Punchier hook or tighter structure
- Conversational, personal, or more casually spoken
- Proof-led, mechanism-led, or practical
- Playful, contrarian, unexpected, or use-case-driven
Label each option by its remix type when useful. Keep all five grounded in the same verified facts. Do not bury the copy under analysis.
Default to casual, spoken language unless the user asks for a more formal tone. Prefer the words Meng would naturally say out loud over polished brand-copy phrasing.
Make every sentence advance the thought. Do not let the second sentence or paragraph merely restate the hook or describe the same feature again. Use it to add a reason, mechanism, use case, proof point, constraint, contrast, question, or conclusion. If it adds nothing new, cut it.
Prevent Repetition
Check two kinds of duplication before finalizing:
Corpus duplication
- Match by post ID, canonical status URL, and normalized text hash.
- Store only Meng's authored text as voice evidence. Keep quoted-source text out of the voice field.
- Never append the same authored post twice.
- Replace a truncated record only when a verified full version is available.
Editorial duplication
- Search for the same hook, claim, resource bundle, anecdote, proof point, and ending.
- Do not reuse a distinctive line merely by changing a few words.
- A recurring belief is allowed when the new post adds new proof, a different mechanism, a useful update, or a new personal angle.
- Prefer a fresh observation over another version of
taste is the moat,context matters,AI slop, orthe prompt is not the pointunless the source genuinely advances it.
Refresh The Voice Corpus
Use the Codex in-app browser only. Never use Chrome. Keep X read-only: do not post, reply, quote, like, repost, bookmark, follow, DM, or change account state.
Open the signed-in profile and the Latest search:
https://x.com/MengTo
https://x.com/search?q=from%3AMengTo&src=typed_query&f=live
On each refresh:
- Collect 20-50 unseen authored posts when X exposes enough history. Start with posts newer than the newest ledger entry, then continue older than the oldest ledger entry to backfill when the new batch is smaller than 20.
- Include original posts, replies, and quote posts. Exclude pure reposts written by someone else.
- Record post ID, canonical URL, UTC timestamp, authored text, and format.
- Expand every truncated authored post on its status page. Report any post that remains incomplete.
- Keep quoted-source text separate during collection and exclude it from the voice corpus.
- Save the collected batch as JSON or JSONL and ingest it with the script bundled beside this skill:
node <skill-dir>/scripts/update-tweet-corpus.mjs --input <batch-path>
- Read the script receipt. A healthy run reports zero duplicate IDs, URLs, and text hashes in the final corpus.
- Update references/voice-profile.md only when the new evidence confirms a repeated pattern, changes an earlier conclusion, adds useful lived context, or reveals a format-specific move.
- Update references/content-source-map.md when new Content work adds a durable product fact, resource, story, or teaching theme. Link to the source instead of copying whole passages.
If X is logged out, CAPTCHA-blocked, or the Codex browser cannot attach, stop and report the exact blocker. Do not use public search, Chrome, or guessed posts as a fallback.
Hone The Profile
Measure the batch before editing the profile:
- sample count and date range
- original, reply, and quote-post mix
- first-person usage
- paragraph and list patterns
- recurring openings, transitions, and endings
- concrete nouns, tools, resources, products, and proof
- rough edges that are natural versus artifacts that should not become rules
Use replies for conversational vocabulary, capitalization, curiosity, gratitude, and disagreement. Use original posts for hooks, story, pacing, lists, proof, and endings. Use quote posts and resource shares for how Meng adds a reason, mechanism, or related resource.
Do not manufacture typos to imitate authenticity. Preserve natural directness, contractions, occasional fragments, and lower-case phrasing when the format supports it.
Validate And Commit
After changing the skill or corpus:
node <skill-dir>/scripts/update-tweet-corpus.mjs --check
python3 <skill-creator-dir>/scripts/quick_validate.py <skill-dir>
git diff --check -- <skill-dir>
Stage only the source-controlled write-like-meng-on-x/ skill folder and commit the narrow change. Leave unrelated modified and untracked files alone.
Report the sampled and added counts, date range, profile changes, duplicate checks, browser status, validation result, and commit hash. If no new post or durable voice insight was found, report a no-op instead of creating churn.
Related Skills
LocalAI
50.4kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
