SuperAPI AI Directory

fb-post-writer

Writing & research

View repository

Updated 10-15 22:41

About this skill

FB Long-Form Writer

Deliver a complete long-form piece that has a stance, concrete material, and can still be revised. Before writing, read references/寫作與事實規則.md; when voice and source material are needed, read references/作者資料模板.md, and fill in only the missing pieces that would affect direction.

Gather Material

The topic is a required input. Obtain the audience, purpose, author's stance, real material, and specified length from the conversation; do not re-ask for information already known. When the audience or purpose is unclear and would change the content, ask at most three key questions at a time. When there is only a topic, you may state plainly that the draft will tentatively target beginner readers and aim to explain the method, without pretending to already understand the author.

With two or three of the person's own posts, calibrate the voice; it is also possible to write without samples. Without personal experience, use viewpoints and concrete operational explanations instead, and do not ask the author to make up stories. Preserve the original material and necessary attribution, and do not rewrite other people's cases as the author's achievements.

Seven-Stage Writing

Follow the seven steps of topic selection, ideation, material preparation, title, introduction, body, and conclusion, completing them internally.

  1. Topic selection: define in one sentence what the reader should understand or be able to do. Handle one core issue per piece.
  2. Ideation: start from the audience's specific situation and choose an angle that can be supported by the existing material.
  3. Material preparation: distinguish confirmed facts, the author's viewpoints, hypothetical examples, and items pending verification. Preserve limitations and counterexamples.
  4. Title: state the topic and applicable situation directly; do not insert unsupported numbers or effects for the sake of attracting attention. Title punctuation follows the author's habits; do not force 【】 or subtitles.
  5. Introduction: state a specific situation, judgment, or question in the first one to three sentences; a true story can enter the event directly without first announcing a secret.
  6. Body: connect viewpoints, material, and explanations into natural paragraphs. Use cases to support viewpoints, and add summaries only when they aid understanding; do not require the same template for every paragraph. When there is a basis, explain the reasons behind the method and its applicable boundaries, and do not force an abstract "level-up" or three-beat suffering arc.
  7. Conclusion: answer the opening question and leave an actionable next step or a complete viewpoint. Open questions and CTAs are both options, determined by purpose, and do not claim that a particular ending will increase reach.

Length and Tone

By default, in-depth long-form pieces use 1,500–3,000 Chinese characters as the editorial range; a user-specified length takes priority. When the material is insufficient to support a long piece, deliver a shorter but complete version and separately list material that could be added; do not pad the word count.

Divide paragraphs by meaning and mobile-reading rhythm, with sentence lengths naturally alternating. Do not force one sentence per line, a punchline in every paragraph, or opposing sentences. Use subheadings only when they aid reading. When facts and tone conflict, preserve the facts first.

Output

Deliver the complete main text first, and do not output the internal seven-stage reasoning. Then place "Internal Review Notes" after a divider: necessary sources, unverified material, voice not yet calibrated, or details needing author confirmation. Do not force questions when nothing is missing.

When the user asks only to revise one paragraph or preserve the original text, limit changes to the specified scope; do not rewrite the whole piece, add new viewpoints, or delete limitations without authorization. If archiving is needed, keep the main text and notes in separate files and preserve the original version.

Pre-Delivery Check

  • Does the first paragraph already state the key point? Does each paragraph advance the same topic?
  • Do first-person statements, numbers, cases, and promises have sources? Are the nature of examples clearly indicated?
  • Are there mechanical parallelism, fake questions and answers, formulaic reversals, or empty talk that only creates expectations?
  • When adapting one's own material, is it still shared directly by the person? When using others' methods, is attribution preserved?
  • Does the ending fulfill the promise? If there is a CTA, do the resources actually exist?
  • Are the public body text and internal notes kept separate? If unpublished, is it referred to only as a draft?