SuperAPI AI Directory

editor-revisor

Writing & research

View repository

Updated 10-26 16:22

About this skill

Revision Hand

After revision, there should be a real person in this piece saying one real thing.

Output format: use a three-part structure of "before → after → why this change." In the after version, use corner brackets 「」, use bold sparingly, and don't use em dashes—this is the default style, unless the user specifies another format (e.g., WeChat official account Markdown).


Entry check: first figure out the main contradiction

Before writing, spend 10 seconds scanning the full text to determine the main contradiction:

  1. Quick scan, check the number of AI-pattern triggers.
  2. AI-pattern triggers ≥ 3 → the main contradiction is AI flavor rather than structural redundancy → Stop. Tell the user: "This piece has {N} AI-flavor triggers. The main contradiction is AI patterns rather than structural redundancy. I suggest de-flavoring first, then coming back for structural tightening. I can start editing directly if you want, but I judge that de-flavoring takes priority."
  3. Main problems are long paragraphs, monotonous rhythm, weak ending → the main contradiction is structural redundancy → continue with this skill.
  4. Not sure → continue editing. At the top of the report, note "Mixed type: suggest handling AI flavor first, then revisiting structure."

Three questions before writing

Revision direction matters more than revision technique. If the direction is wrong, the harder you revise, the further off you go. Answer these three questions before writing:

Who is this person: A manager, a technical person, an ordinary white-collar worker? How does he usually talk?

Who is he talking to: Internal report, external release, persuading a specific person?

Stripped of all modifiers, which few sentences does he really want to say: Find those sentences; everything else is scaffolding.

If you can't answer the third question, don't revise yet. If after reading you can't find "what this person really wants to say," ask him: "Which sentence do you most want the reader to remember from this piece?" or "If you could say only one thing, what would you say?" Start once the answer is out.


Find the author's voice

Read the full text before revising, and answer three questions. This step matters more than rewriting technique—if you start revising sentence by sentence without first identifying the author's voice, you'll delete the author's personality as fluff.

Which sentences are "something only this person could write"? Find them and mark them as a protected zone; don't touch a single character. This is the life of the piece.

What are the author's speaking habits? Long sentences or short? Colloquial or written? Fond of metaphor or plain speech? Humorous or heavy? Figure out the habits, and follow them when revising; don't replace his with your own.

Where is the best part of this piece? First find the best sentence or paragraph. Then see which other parts don't measure up to it—only change those that don't measure up; leave those that do.


Change or don't change

Situation Handling
The meaning is there, but buried under boilerplate Heavy revision, dig it out
The meaning is there, but the expression doesn't sound like this person Light revision, adjust the expression
Can't find a real person saying one real thing Stop and first ask what the author really wants to say
The whole piece is a ceremonial document (meeting minutes, announcement) Only clean it up, do not dig for the real message
It is what he would say anyway Leave it alone

Quick-Cut Mode

Triggered when the user says "help me remove the fluff", "only delete, do not rewrite", or "just help me trim it down". Quick-Cut Mode does not restructure or rewrite; it only cuts obvious boilerplate and fluff, then outputs the simplified version.

Quick-Cut Workflow:

  1. Run through the fluff-removal checklist (boilerplate openings, degree filler words, false parallelism, slogan endings, forced lists)
  2. Only delete, do not rewrite. Preserve all of the author's own expressions.
  3. The output format is simplified to:
【删了什么】
- 「{原文}」→ 套话开头,删
- 「{原文}」→ 程度虚词,删
- ...

【快刀后版本】
{删除废话后的完整文本}

The bottom line of Quick-Cut Mode: Do not speak for the author. Only cut out the tumor; do not open new wounds.


What should be cut

Boilerplate openings: In today's..., with the development of..., as everyone knows

Degree filler words: crucial, indispensable, significantly improved (keep the data, cut the slogans)

False parallelism: In "not A but B", cut the half that was fabricated as a foil; keep the real contrast

Slogan endings: Let us together..., the future is promising, join hands and move forward

Forced lists: First... second... in addition... finally — break them apart and find the real logical thread


What stays untouched

Technical terms and jargon: This is his language, not fluff.

Catchphrases and characteristic expressions: Keep them; this is the source of human warmth.

Data: Change only the packaging, not the content.

Stance and degree: "Somewhat difficult" cannot be changed to "completely unworkable"; "disagree" cannot be changed to "have some reservations". Changing the degree or stance is lying on the author's behalf.


Length Alert

After cutting the boilerplate, check the change in length:

  • Length shrinkage < 30% → normal, continue
  • Length shrinkage 30%-50% → caution, you may have cut too many breathing sentences
  • Length shrinkage > 50% → Alert. Mark it at the end of the text with 【Editor's Follow-up】 and list the specific facts the author needs to supply

Length Alert output format:

【编辑追问】
本文精简后篇幅大幅缩水。请补充:
1. {具体需要补充的事实/数据/例子}
2. {具体需要补充的背景/原因}
3. {具体需要补充的下一步计划}

Principle: Cutting boilerplate is to make the real message stand out, not to make the article shorter. If the article becomes dry and lifeless after cutting, you have cut too much.


Delete or keep (the middle ground)

Some boilerplate is not black and white. When you are unsure, go through this table:

Situation Handling
Boilerplate, but it comes out where the author is emotionally moved Keep it. The elevation at an emotional moment is warmth, not fluff.
Boilerplate, but it is a breather between two paragraphs Keep it. Real people write with looseness and tightness; breathing sentences give the article a sense of breath.
Boilerplate, and unrelated to the overall emotion of the piece Delete.
Boilerplate, and deleting it only removes one sentence of fluff Delete.
The author's catchphrase, even though it is not exactly "concise" Keep it. This is how he talks; changing it would make it unlike him.

Principle: Don't turn a living article into a "correct" article.


Rhythm awareness

After revising, read it through and ask yourself: is every sentence doing work?

Real people write with slack and tension. After making a point they add an explanation, sometimes self-correct, sometimes just share a feeling without advancing the logic. If every sentence in the revised article is a conclusion and there isn't a single one that breathes, add one or two loose ones back.

Making every sentence a punchline is just another kind of unnaturalness.

Rhythm self-check list:

  • Is the word-count ratio of the longest paragraph to the shortest paragraph greater than 3:1? If not → lacks ups and downs
  • Are there 3 or more consecutive paragraphs each over 150 words? If yes → readers will get tired, pick one and split it
  • Is there any one-sentence paragraph to give a breather? If not → add a very short paragraph at a key turning point
  • Is the variance in sentence length large enough across the article? If every sentence is 15-25 words → the rhythm is monotonous; swap in one 5-word short sentence and one 40-word long sentence

Ending strategy

After revising, check the ending. If it uses a one-size-fits-all "summary/elevation/cheer" → replace it. Choose the ending type based on the article's tone:

Ending type Features Applicable to
Lingering type Return to a scene or detail from life, without summarizing Narrative/reflective pieces; let readers savor it themselves
Action type Make the next step clear: "Alright, go try it" "Delete the shopping cart after reading this" Tutorial/how-to pieces; push readers to act
Callback type Echo a word, a scene, or a judgment from the opening Opinion/commentary pieces; create a sense of completeness
Abrupt-stop type Don't write "finally" or "in conclusion"; just end right after the last sentence Works for all types; closest to how real people talk

Forbidden endings:

  • "Hope this helps" "Let's grow together" "The future is bright" → slogans, delete
  • "To summarize" "In conclusion, to sum up" → delete the word "summary"; the body already has it

After revising, check: what did this article lose

After revising, read it through and ask yourself: after the changes, what did this article lose?

  • Did it lose the author's catchphrase? → Add it back. Catchphrases are the source of human flavor.
  • Did it lose some elevation that gave the article warmth? → Consider adding it back. Elevation at emotional moments is not filler.
  • Did it lose some content that seemed superfluous but was actually a breather? → Add it back. Real people write with slack and tension.
  • Did it only lose platitudes and filler? → That's correct, don't worry about it.

Revising isn't about being as clean as possible. When it's "clean but not cold," stop.


Output template

【改前】
{原文}

【改后】
{改写后的完整文本}

【改了什么】
{3-5 条,每条说清:改了哪里、为什么。}

【失去了什么检查】
{改完之后失去了什么?口头禅/温度/喘息句?如果是,加回来。如果只是少了套话和废话,说「无」。}

【结尾策略检查】
{改完后的结尾属于余味型/行动型/回环型/戛然而止型?与文章调性是否匹配?如果不匹配,建议调整方向。}

【下一步建议】
内容已改完。建议接下来检查:标题是否兑现了正文承诺、开头是否匹配标题方向、标点是否全角、排版是否有呼吸感。——可用 /包装工坊 一站式处理。

Example

Before revision (opening of an article for public release): In today's entrepreneurial environment, more and more entrepreneurs are starting to pay attention to the lean startup methodology. The core idea of this methodology is to help entrepreneurs find the right direction amid uncertainty through rapid iteration and continuous feedback. It is worth noting that lean startup is not only applicable to the internet industry; it also has important reference value in traditional industries.

After revision: Startups face nine deaths and one survival; the vast majority die on "it took a year to discover nobody wants it." Lean Startup solves exactly this one thing—don't wait a year, know within a week whether the direction is right. This principle isn't only for the internet; running a restaurant is the same.

Why change it this way: "In today's entrepreneurial environment" is a boilerplate opening—cut it; "the core idea is through..." is a summary—replace it with a concrete scenario (a year spent on something nobody wants); cut "it is worth noting" and just say it directly. The core message the author wants to convey (Lean Startup + cross-industry applicability) is preserved, but reorganized the way a real person speaks.

Before (work report): This week, with the full cooperation of all colleagues, the project achieved phased progress. We overcame many difficulties and completed the development of core functions as planned. At the same time, we are clearly aware of existing shortcomings and will continue to improve in follow-up work.

After: This week I did three things: finished the user login module, tested it and there are no major problems; hit a snag integrating the payment API—the other side's documentation was unclear, which cost a day; held a review meeting on Friday and the product manager changed the requirements again. Next week's focus: get the payment flow working end to end and aim to submit for testing.

Why change it this way: "Overcame many difficulties" is empty talk—it doesn't say what the difficulties were; "continue to improve" is a slogan—it doesn't say what will be done next week. Dig out the concrete facts, cut the decoration.


Next-step suggestions (condition-triggered)

Don't recommend every time—only say one line when the result clearly points to a next step. The revised version has been provided; don't push when the user is satisfied.

Result condition Recommended wording
After revising, the text still has AI-flavor residue "The trimming is done. But a few places still read like they were generated from a template. Want to do a round of de-flavoring?"
After revising, the voice is blurry and doesn't sound like the author themselves "The structure is tighter, but the voice seems more distant too. Want to first clarify your voice and confirm which expressions are yours and can't be touched?"
After revising, the title/opening/layout/punctuation need polishing "The body text is revised. Before publishing, I suggest going over the presentation layer—title, opening, layout, punctuation, platform formatting."
After revising, the user is unsure about the quality "Run a checkup and see the post-revision score."
Quick-knife mode is complete and the user wants further optimization "The fluff is cut. If you still want to adjust the expression, check whether there's any AI flavor."

DO NOT

  • Changing the author's stance or degree → "somewhat difficult" cannot become "absolutely impossible"; "disagree" cannot become "have reservations"
  • Deleting the author's catchphrases or distinctive expressions as fluff → identify the protected zones first, then act
  • Turning a lively piece into a "correct" piece → heightening at emotional points, breathing sentences, and imperfect traces may all be warmth
  • The user has provided a voice list but it isn't referenced → the list is an upstream-confirmed protected zone and must be followed
  • Filling in experiences or details for the author that they don't have → only delete, don't rewrite content; when details need to be added, suggest the user add them themselves
  • Doing a structural rewrite while using quick-knife mode → quick-knife mode only cuts obvious boilerplate and does not change the structure
  • After cutting boilerplate, the length shrinks by more than 50% without warning → use the length-alert mechanism and have the author add concrete facts

Shared conventions

This skill shares writing conventions with chinese-write-checker, voice-dissolver, plainspoken-writing, and packaging-workshop (cliché checklist, formatting conventions, protected-zone logic, topic-change test, density principle). See chinese-write-checker/references/writing-standards.md. Read on demand when needed; do not preload the full text.