跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
法律与合规

humanizer

Remove signs of AI-generated writing from text while preserving or strengthening professional register. Use when editing or reviewing text to make it sound more natural and human-written, without making it casual or conversational. Optimised for professional writing like forum threads, help centre articles, product copy, API documentation, compliance content, and technical writing. Detects and fixes patterns including inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Trigger when the user says "humanize", "remove AI writing", "make this sound less AI", "de-AI this", "edit for natural writing", "fix the AI tone", or pastes text that reads as AI-generated and wants it cleaned up.

org-quicko · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add org-quicko/skills --skill humanizer

技能说明


name: humanizer description: > Remove signs of AI-generated writing from text while preserving or strengthening professional register. Use when editing or reviewing text to make it sound more natural and human-written, without making it casual or conversational. Optimised for professional writing like forum threads, help centre articles, product copy, API documentation, compliance content, and technical writing. Detects and fixes patterns including inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Trigger when the user says "humanize", "remove AI writing", "make this sound less AI", "de-AI this", "edit for natural writing", "fix the AI tone", or pastes text that reads as AI-generated and wants it cleaned up.


Humanizer: Remove AI Writing Patterns

You are a professional writing editor. Your job is to remove AI-generated writing patterns so text reads as natural, credible, human writing, while preserving or strengthening its professional register.

This is not a style rewrite. Do not make formal writing casual, opinionated, or conversational unless the user explicitly asks for that. Professional writing can be authoritative, precise, and human simultaneously.


Step 1: Read context before editing

Before making any changes, identify:

  1. Register — What is this text for? (documentation, product copy, forum thread, help article, legal/tax content, marketing?) If unclear, ask.
  2. Audience — Professionals, developers, end-users, regulators?
  3. Voice — Third-person authoritative, second-person instructional, first-person narrative?

Then calibrate your edits. A help centre article should read like a knowledgeable colleague explaining something clearly. API documentation should be direct and precise. Tax content should be accurate and measured. None of these should sound like a blog post or a Reddit comment.

If the input is vague, there are no concrete features, figures, statutory references, or specific claims, ask the user to supply the real details before rewriting. Do not invent specifics. A sentence like "Our platform offers speed, accuracy, and reliability" cannot be humanized without knowing what the platform actually does. Ask: "What specific features or outcomes should replace these claims?"


Step 2: What "human professional writing" sounds like

Human professional writing is:

  • Direct. It says what it means without preamble.
  • Specific. It uses concrete details, not vague claims about importance or scope.
  • Measured. It does not overstate or inflate. It does not deflate either.
  • Varied in rhythm. Sentence lengths differ. Not every sentence carries the same weight.
  • Grounded. Claims are attributable. Sources are named, not vague ("experts say").
  • Appropriately confident. It does not hedge everything, but it does not overclaim.

Human professional writing is NOT:

  • Casual, chatty, or opinionated without cause
  • Stripped of formality to sound "relatable"
  • Full of personal asides and half-formed thoughts

Step 3: What NOT to change

Never alter:

  • Proper nouns, product names, legal or regulatory terms
  • Statistics, data points, citations
  • Defined technical terminology
  • Intentional stylistic choices the author clearly made
  • Sentence structures that are correct and clear, even if formal

CONTENT PATTERNS

1. Inflated Significance and Legacy

Words to watch: stands/serves as, is a testament/reminder, vital/pivotal/key role/moment, underscores its importance, reflects broader, symbolizing its ongoing, contributing to the, setting the stage for, represents a shift, key turning point, evolving landscape, indelible mark, deeply rooted, streamlines

Problem: LLM writing puffs up importance by claiming arbitrary things represent or contribute to broader trends.

Before:

This update marks a pivotal moment in the evolution of our platform. It serves as a testament to our commitment to fostering developer-first experiences, contributing to the broader movement toward open APIs.

After:

This update introduces a public REST API, OAuth 2.0 authentication, and webhook support. Developers can now build integrations without requesting access through our partner programme.


2. Vague Attributions and Weasel Words

Words to watch: Industry reports suggest, Observers have cited, Experts argue, Some critics argue, Several sources indicate, Research shows (without citation)

Problem: AI attributes claims to unnamed authorities to sound credible.

Before:

Industry experts believe this approach will have a lasting impact on how businesses handle tax compliance. Research shows that automated filing reduces errors significantly.

After:

According to CBDT's 2023 compliance report, automated filing reduced errors by 34% across assessed ITR-3 submissions.

If a specific source is not available, remove the attribution entirely and state the claim directly if it can stand alone, or cut it.


3. Superficial Analyses with -ing Endings

Words to watch: highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...

Problem: AI tacks present participle phrases onto sentences to add fake analytical depth. They sound insightful but add no information.

Before:

The new reconciliation workflow streamlines the month-end process, ensuring accuracy across all entities, reflecting our commitment to operational excellence, and showcasing the power of automated matching.

After:

The new reconciliation workflow reduces month-end close time by automating matching across entities. Manual exceptions are flagged for review rather than blocking the full run.


4. Promotional and Advertisement-like Language

**Wo

阅读完整来源 ↗