SuperAPI AI Directory

gzh-short-post

General & other

View repository

Updated 10-16 04:56

About this skill

WeChat public account short article writing

Within 1000 characters, plain text, no images. Write an observation, a hands-on test, a judgment.

This is not a shrunk-down version of a long article. Long articles win through structure and argument, while short articles win throughone sufficiently sharp point + clean rhythmto win. Cramming three viewpoints into 1000 characters is the same as explaining none of them clearly.

Platform facts (remember these first to avoid writing in vain)

Format Limit Description
Image-text message(default for this Skill) No limit on body text Has a title, has a cover, can be formatted. 1000 characters is the editing target, not a platform limit
Mass-sent plain text message 300 characters No title or cover, and it cannot be sent if it exceeds the limit
Auto-reply plain text 600 characters

By default, write as an image-text message(with a title). When the author explicitly says they want to send a "plain text mass message," cut it to within 300 characters and remove the title.


Core style rules

1. First person, no preaching

The most important rule. The whole piece should feel like sharing your own observation, not instructing the reader.

❌ ✅
the software you use daily the software I use daily / the software we use daily
you will find will find / I find
you need to pay attention what needs attention is
everyone can try I gave it a try

The word "you" appears no more than once in the whole piece, preferably 0 times. It reads like someone overhearing you talk to yourself, not like lecturing from a stage.

Exception: the closing call to action can use "you" ("if you're using it too, come chat in the comments").

2. Tone: have a viewpoint, don't put on airs

  • Dare to make a judgment: "this is just creating anxiety" "to put it bluntly, it's an IQ tax" "it really works, but it's absurdly expensive"
  • Don't please both sides: you can add the other side, but don't write every sentence as "on one hand... on the other hand..."
  • Don't use academic tone: "the author believes" "in summary" "it is worth noting that"
  • Don't use chicken-soup tone: "hope this helps everyone" "mutual encouragement" "let's cheer together"

3. AI-tone blacklist (delete on sight)

The common feature of these sentence patterns:they read like translating for the reader, rather than expressing your own thoughts.

  • "essentially it's" "essentially it is..."
  • "to put it plainly, it's" "simply put, it's"
  • "from another angle" "in other words"
  • "the logic behind it is the same"
  • "not X, but Y" (at most once in the whole piece)
  • Three-part parallel ending ("is..., is..., and even more is...")

One exception that must be distinguished: asking and answering yourself is a good thing.

A question stands alone as its own paragraph, immediately followed by aspecificanswer. This is a rhythm tool, not AI-speak. It becomes AI-speak because what follows is a vague generalization.

  • ✅ 这意味着什么? → 以前是我盯着它写,现在是它自己拆任务、自己跑、自己回来报错。
  • ❌ 这意味着什么? → 这意味着 AI 正在深刻改变我们的工作方式。

How to judge:Delete the question and the answer together. If the article loses no information, it's AI-speak.

4. Punctuation and formatting

  • Use straight quotes consistently: "",don't use 「」
  • Em dashes —— at most 2 times in the whole piece; if more, break the sentence with a comma or start a new sentence
  • No emoji, no hashtags (except WeChat Official Account topic tags)
  • Keep English product names as they are: Claude Code, MCP, 飞书 CLI
  • Don't bold the titles of numbered points, just write 1 命令行, don't write **1 命令行**. Keep it plain, like jotting down notes casually
  • Pure text with no images to carry it,it relies entirely on paragraphing to breathe. A line on a phone screen is about 22–24 characters,a single paragraph over 70 characters should be broken

5. Structural skeleton

A short piece only needs two kinds of skeletons,use only one per piece:

Skeleton A: numbered-points style(suitable for several parallel observations)

一句引入(一个疑问 / 一个具体场景)

1 观点
2-3 句展开

2 观点
2-3 句展开

3 观点
2-3 句展开

串联段:这几个点加在一起说明了什么
收尾:一个具体画面

At most 4 numbered points,more than 4 and it should be a long-form piece。

The connecting paragraph is the crux of this skeleton. Without it, the article is just a list, not an insight. After reading, readers will feel they "read a few pieces of information" rather than "figured out one thing."

Skeleton B: single-point progression style(suitable for one cognitive shift)

一个切身的事件 / 感受开头

三到四段递进的分析,每段 3-5 句

收尾:回到个人立场,一个干脆的判断

In a short piece, B is usually better than A—explaining one point thoroughly in 1000 characters is more memorable than listing four points. When unsure, choose B.

6. Opening: no warm-up

WeChat Official Account readers are subscribers, not passersby scrolling a feed, so there's no need to prove who you are at the start. But precisely because of that,no one has the patience to read buildup。

  • ❌ "Recently, everyone may have noticed a phenomenon..."
  • ❌ "Today I want to talk with you about the topic of XXX"
  • ✅ "After last night's update, the first thing I did was go through its connector list."
  • ✅ "Spent 68 yuan, ran it for three hours, and the conclusion was a bit unexpected."

The first sentence should contain specific information. If the summary is left blank, it will automatically take the beginning of the body text, and this sentence will appear as-is in readers' message list.

7. Ending: concrete image > abstract judgment

Don't end with something like "this is a paradigm shift." Land on a scene that can be imagined.

  • ❌ "AI is profoundly changing the content industry."
  • ✅ "Friends around me who write WeChat Official Accounts, the first thing they do when they open their computer now isn't create a new document, it's throw the material to an Agent, then go pour a glass of water."

After the ending, you can addonecall to action (comment / Wow / read the previous post),only one。


Writing process

  1. Define the single point. What is the one sentence you want readers to remember from this short piece? If you can't write that sentence, don't start writing yet
  2. Choose a skeleton(A or B), if unsure choose B
  3. Write the opening: A concrete scene or number, no warm-up
  4. Write the body: 3-5 sentences per paragraph, cut every word that doesn't add information
  5. Write the connecting paragraph(required for skeleton A)
  6. Write the ending: a concrete image + one call to action
  7. Go through the checklist(see below)

Pre-output checklist

Go through each item,no skipping:

□ 字数 ≤1000(纯文字群发则 ≤300)
□ 搜"你"字:出现几次?除结尾引导外应为 0
□ 搜 AI 腔黑名单:本质上 / 说白了 / 换句话说 / 不是…而是
□ 自问自答处:答句是不是具体的?删掉会不会损失信息?
□ 搜「」符号:全部换成""
□ 数破折号——:≤2 次
□ 编号标题有没有被加粗(**)
□ 最长段落多少字?超过 70 字(约 3 行)要断
□ 骨架 A:有没有串联段?
□ 收尾是具体画面还是抽象判断?
□ 行动引导是不是只有一个?
□ 全篇只讲了一个点吗?

When outputting,attach the check results, don't just hand in the draft.


Complete example

Below is a short piece of about 700 words, as a reference for style and rhythm.


Title: For 68 yuan, I had an Agent organize three months of article archives

More than sixty articles I'd written were piled up in the Feishu knowledge base, just sitting there, never systematically reviewed.

Last night I thought I'd give it a try, so I threw the directory at the Agent, without giving it any other material.

It went in on its own, read through each one, and pulled out a topic distribution. The result was a bit surprising.

I'd always thought I was writing "AI tool reviews."

In fact, twenty-nine of the fifty-nine articles were about engineering practices for Agents and Skills, a full half.

The rest split into three parts: the cloud computing and K8s branch was left over from an earlier period and no longer connects to the main line; AI video is another independent line; and what remained were scattered product tests.

In other words—I thought I was writing A, but I was actually writing B.

This in itself isn't much. What's interesting is that I couldn't have seen this conclusion by reading sixty articles myself.

People have a severe recency bias about what they've written; the few most recent pieces take over the whole impression, and the dozens before them have long since blurred.

The Agent doesn't have this problem. It reads through in one go and is only responsible to the text.

I later turned this into a fixed routine: every time I accumulate twenty or thirty articles, I have it rerun the distribution. It doesn't give me advice, it just tells me what I actually wrote. The judgment is still mine to make.

This is a bit different from my original expectations for AI writing tools.

I used to assume their value was in "helping me write," but now I find the more reliable value is in "telling me what I wrote." The former requires it to have taste; the latter only requires it not to forget.

Not forgetting—it's far better at that than I am.

People who write public accounts more or less all have this problem: after writing for a few years, ask "what is this account actually writing about," and they can't answer. It's not that they don't know, it's that they can't remember clearly.

Now this problem has a solution, and the cost is the price of a cup of coffee and a three-minute wait.

If you've also stored up a pile of things you've written, it's worth running once. Whatever comes out, let's talk about it in the comments.


Note the features of this example:

  • The first sentence is a concrete scene ("more than sixty piled up" "just sitting there"), with no warm-up
  • Skeleton B, the whole piece makes only one point: the value of AI writing tools may be in "looking back" rather than "generating"
  • Concrete numbers hold up the judgment: 59 articles / 29 articles / half
  • 换句话说 appears once—this is a blacklist word; it's kept in the example to show that it can be an exception: When it connects two concrete statements ("thought you were writing A / actually wrote B") rather than being used to summarize, it is a rhythm tool. Rules are fixed; the criterion is always "would deleting it lose information"
  • All paragraphs are within 70 characters (about 3 lines), using whitespace for breathing
  • The ending lands on a specific flaw of a specific group ("ask them what they're writing, and they can't answer"), not an abstract judgment
  • Only one call to action: the comment section
  • "You" appears only once in the whole piece, and it's in the closing call to action; the longest paragraph is within 70 characters. These two points were checked one by one against the checklist above

Special notes

  • This Skill can both write from scratch and compress a long article into a short one.Compression is not excerpting, it is re-distilling—Pick the single sharpest point and rewrite it; do not keep one sentence from every section of the long article
  • When the material contains more than 4 viewpoints, proactively suggest: either cut down to 1 and write a short piece, or switch to gzh-longform-writer to write a long article
  • Keep the author's own stance and edge,do not neutralize the original text's judgments
  • Do not fabricate data, cases, or experiences. Test results the author has not mentioned must not be written

Style

Follow the general rules above by default.

When the author says "use my style", read ../references/my-voice.md, and apply the rules inside on top (in case of conflict, my-voice takes precedence).


Coordination with other Skills in this repository

Scenario Switch to
Too many points, should write a long article gzh-longform-writer
Write a title baokuan-title-generator
Need to format for pasting into a WeChat official account space-wechat-layout
Need to convert to a Jike / X post External x-post Skill