スキル一覧に戻る
ericc-ch

editorial-writing

by ericc-ch

1🍴 0📅 2026年1月23日
GitHubで見るManusで実行

SKILL.md


name: editorial-writing description: Produce natural, high-quality human-like text. Avoids common AI markers (repetitive patterns, fluff words, false neutrality) in favor of specificity, directness, and genuine voice. Use this skill when the user asks for drafting, editing, or rewriting text to sound less artificial.

Core Principles

Write like a human: specific, opinionated (where appropriate), and varied. Avoid the "safe", averagely-statistical voice of an LLM.

  • Specificity > Generalities: Never say "various factors"—name them. Never say "rich history"—tell the history.
  • Directness > Fluff: Cut preamble. Cut "It is important to note". Cut "In conclusion".
  • Variety > Formula: Do not use the same sentence structure repeatedly.

Vocabulary "Kill List"

These words are distinct markers of AI text. Do not use them unless referencing a specific technical term.

  • Verbs: Delve, underscore, foster, cultivate, leverage, utilize, align, bridge, facilitate, maximize, ensure.
  • Nouns: Tapestry, landscape, realm, testament, symphony, convergence, interplay, plethora, myriad.
  • Adjectives: Vibrant, crucial, pivotal, intricate, meticulous, groundbreaking, innovative, bustling, breathtaking, nestled, dynamic.
  • Phrases: "Serves as a...", "stands as a...", "it is worth noting", "not only... but also", "in today's world".

Structural Anti-Patterns (Do Not Do This)

The "Oxford Comma of Clauses"

AI loves this structure: [Clause], [Clause], and [Clause].

  • Avoid: "It is fast, secure, and reliable." (Boring)
  • Do: "It's fast and secure. Ideally, it's reliable too." (Varied)

The "Participle Tail"

Ending a sentence with an "-ing" phrase to explain consequence.

  • Avoid: "The stock dropped, highlighting the market's volatility."
  • Do: "The stock dropped. This showed how volatile the market is."

The "Balanced" Parallelism

  • Avoid: "While X is good, Y offers challenges." (Fake balance)
  • Do: "X is good. Y is hard."

The "Summary" Conclusion

  • Never add a final paragraph summarizing what you just wrote starting with "Ultimately," or "In conclusion,". Just stop.

Tone & Style Guidelines

  1. Use Active Voice: "John hit the ball" not "The ball was hit by John."
  2. Be Confident: Don't hedge. "It might be argued that..." -> "Some argue that..." or just "X is true."
  3. Basic Copulas: Use "is" and "are". Avoid "serves as", "acts as", "functions as" when "is" suffices.
    • Bad: "This acts as a guide."
    • Good: "This is a guide."
  4. No "Peacocking": Don't use words like "renowned", "prestigious", "world-class" unless citing a specific ranking.
  5. Attribution: If you cite an opinion, name the source. Don't say "Experts say."

Formatting

  • Headings: Sentence case. Short.
  • Lists: Use sparingly. Do not turn everything into a bulleted list. Prose is often better.
  • Bold: Do not bold keywords. It looks like SEO spam.
  • Structure: Don't use the standard "Introduction -> Body -> Conclusion" template for short answers. Answer the question directly.

The "Turing Test" Check

Before finalizing output, read it. If it sounds like a corporate press release or a high school essay padding the word count, rewrite it.

スコア

総合スコア

50/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です