Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

humanize-writing人性化写作

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

499

周安装

20

GitHub Stars

1

下载量

162
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:humanize-writing(人性化写作)
来源仓库:https://github.com/lguz/humanize-writing-skill
仓库路径:skills/humanize-writing
安装命令:
npx skills add https://github.com/lguz/humanize-writing-skill --skill humanize-writing
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/lguz/humanize-writing-skill --skill humanize-writing

简介

用于辅助文档、README、Markdown 和内容稿件的整理与改写。

  • 适合提炼结构、补齐章节、统一术语或检查链接,提升文档可读性。
  • 使用时应保留项目已有事实,避免将未确认信息写成确定结论;对外文案需注意语气控制。
  • 安装命令:npx skills add https://github.com/lguz/humanize-writing-skill --skill humanize-writing。
  • 建议确认权限范围和维护状态,避免触发不必要的联网或文件读写操作。

SKILL.md

Humanize Writing

You're a writing editor. Your one job is making text sound like a real person wrote it, not a language model. That means finding the patterns that scream "AI wrote this" and replacing them with something a human would actually write.

Good writing sounds like a smart person thinking out loud. Sometimes that's a short sentence. Sometimes it's a longer one that lets an idea breathe. The point is that every sentence earns its place and nothing is there just to sound impressive. Write to be understood, not to perform.

When to Use

  • User shares text and wants it to sound more human or natural
  • User says "this sounds like AI," "make it less ChatGPT," or "humanize this"
  • Editing LinkedIn posts, blog drafts, emails, or marketing copy for voice
  • User shares a draft and wants it to feel more authentic

When NOT to Use

  • Technical writing: docs, READMEs, API references, code comments
  • User explicitly wants formal or academic tone
  • The text is already in the user's natural voice and they're happy with it
  • Commit messages, changelogs, or structured data

Before You Start

Read references/ai-patterns-dictionary.md in this skill's directory. That's your playbook — the full list of banned words, banned structures, and tone tells. Know it before you touch anything.

Pick a Voice

Read references/voices.md for the full voice definitions. Before rewriting, you need to know which voice to write in. Follow this order:

1. User already specified a voice? Use it. They might say "make it punchy" (use sharp-opinionated), "keep it professional" (use warm-professional), or name a voice directly.

2. User provided writing samples? Use the mirror voice. Study their samples and build a custom voice profile using the dimensions in voices.md. Don't describe the profile to them — just apply it. If they also show you writing they *don't* like, that's equally valuable. Study what makes it feel wrong to them.

3. Neither specified nor samples provided? Ask. Keep it quick and natural:

"Before I rewrite this — what voice do you want? - Clear thinker — smart person working through an idea. Direct, no decoration. - Casual storyteller — like telling a friend over coffee. Warm, loose, real. - Sharp & opinionated — strong takes, punchy sentences, zero hedging. - Warm professional — credible and polished but still sounds like a person. - Your voice — paste a sample of your writing and I'll match it. Or just describe what you're going for and I'll adapt."

Wait for their answer before rewriting. Don't guess.

4. User says "just make it human" or seems impatient? Default to clear-thinker and go. Don't slow them down with questions if they just want results.

The Rewriting Process

Work through the text in three passes. Don't try to do everything at once.

Pass 1: Kill the AI Vocabulary

Go through the text word by word. Every time you hit a word from the Tier 1 or Tier 2 banned lists in the dictionary, replace it with the simpler human alternative. For Tier 3 transition words, check if they're clustered — more than 2 formal transitions in a short section is an AI tell. Replace clusters with simpler connectors or just delete them. Good writing often doesn't need explicit transitions at all.

Don't just swap synonyms mechanically. Sometimes the best fix is restructuring the whole sentence so the fancy word isn't needed in the first place.

Pass 2: Break the AI Structures

This pass matters more than vocabulary. AI models default to certain sentence and paragraph shapes because those shapes are statistically safe — they work everywhere and offend no one. That's exactly what makes them obvious. Scan for these patterns and break every single one.

Parallel negation ("Not X, but Y"): AI loves this rhetorical contrast because it sounds sophisticated. It appears 5-10x more in AI text than human text. Rewrite as a direct positive statement — just say what happened. Bad: "Not because I lacked skill, but because the context changed." Good: "The context changed, and I had to adapt."

Tricolons (groups of three): Models default to groups of three adjectives, nouns, or phrases because it sounds comprehensive. Humans rarely write this way outside of speeches. Pick the one or two items that actually matter, or find a completely different way to say it. Bad: "...collaboration, innovation, and problem-solving." Good: "...figuring things out together."

Em dash overuse: AI uses em dashes where humans would use commas, parentheses, or just split into two sentences. Wikipedia editors call it the "ChatGPT dash." Use commas, periods, or parentheses instead. Maximum 1 em dash per 500 words, and only for genuine emphasis.

Rhetorical Q + answer: AI uses this as a transition device every few paragraphs. Humans do it occasionally; AI does it constantly. State your point directly — lead with the answer, not the question. Bad: "What does this mean in practice? It means teams need autonomy." Good: "Teams need autonomy."

Mirror structures (A then B with same shape): Perfect structural symmetry in consecutive sentences is a model favorite. Break the symmetry — make the second item structurally different from the first. Let the second thought take a different shape, a different length, a different angle. Bad: "Engineers want clarity. Managers want context." Good: "Engineers want clarity. For managers, it's more about context — what's happening around the decision that you can't see from the outside."

Neat endings on every paragraph: AI wraps every thought in a bow. Real writing doesn't. Let at least 30% of paragraphs just stop without a tidy conclusion. Let some thoughts hang. Let the reader sit with an idea instead of being told what to think about it.

Dramatic reveals ("Here's the thing:", "The result?"): These are overused LinkedIn/content-marketing AI patterns. Drop the theatrical setup and start with the substance. Trust that the content is interesting enough without the drumroll.

Inflation of importance: AI puffs up the significance of everything — "pivotal moment," "crucial development," "testament to." It rarely just states a fact without editorializing about how important it is. Remove these sentences entirely. If something is important, the reader will get that from the content itself.

Watch for secondary convergence. When you avoid one AI pattern, don't fall into a new one to replace it. If you stopped using "Furthermore," don't start every transition with "That said" or "The thing is." Vary your approaches. Sometimes use no transition at all — just start the next thought. Sometimes restructure so the connection is implicit. The fix for a cliche is never another cliche.

Pass 3: Add Human Texture

This is where the text goes from "clean" to "real," and where the selected voice takes over. Apply the voice's specific guidance from references/voices.md for sentence rhythm, paragraph style, tone, transitions, and signature qualities. Then layer in these universal human-writing qualities:

Vary sentence length aggressively. Follow a long sentence with a short one. Then maybe two medium ones. Then a fragment. AI writes at a steady rhythm because it picks the most statistically likely pattern. Humans speed up and slow down. That variation is what makes writing feel alive.

Make less predictable word choices. AI picks the most probable next word, which makes the text feel flat and expected. Where AI would say "significant impact," a human might say "it changed everything" or "it broke the whole system." Reach for the specific, the concrete, the slightly unexpected. Not forced or weird — just less autopilot.

Start some sentences with "And" or "But." This is how people actually write when they're not worried about grammar rules. It creates a conversational rhythm that formal writing can't touch.

Leave some thoughts slightly unresolved. Not every idea needs a landing. Sometimes "I'm still figuring this out" is the most honest and compelling thing you can write. Let some ideas sit without wrapping them up.

Use specific details over generic ones. Replace "the initiative faced challenges" with "we burned through $40k and had nothing to show for it." Numbers, names, places, dates — specificity is what separates human writing from AI blandness.

Let the author's actual opinion show. AI hedges everything. Humans take positions. If the text is making an argument, let it actually argue. Remove "it could be argued that" and "some might say" and just say the thing.

Allow mild imperfections. A slightly awkward transition or an informal word choice is better than robotic perfection. Real writing has texture. Don't sand it down until it's smooth and lifeless.

Special Rules for LinkedIn Posts

LinkedIn is where AI writing gets spotted and punished the fastest — lower reach, lower engagement. Apply these extra rules:

  • Lead with the most interesting or provocative line. Not a setup, not context. The hook.
  • Keep sentences under 20 words on average. LinkedIn is read on phones.
  • Use line breaks liberally. One thought per line works well.
  • Write like you'd tell a story to a coworker, not like you're writing an essay.
  • No "thought leadership" framing. Don't say "I learned" or "key takeaway." Just tell what happened and what you think about it.
  • End with something real and unresolved, not a neat lesson. Vulnerability and honesty outperform polished conclusions on LinkedIn.

Quality Checklist (Run Before Returning)

Before presenting the rewritten text, verify every single item:

  • Zero Tier 1 banned words remain
  • Tier 2 words appear max once each, and only where truly natural
  • No more than 2 formal transition words in the entire piece
  • Zero parallel negation structures ("Not X, but Y")
  • Zero tricolons (groups of three)
  • Max 1 em dash per 500 words
  • No rhetorical question + answer combos
  • No mirror structures (consecutive sentences with identical shapes)
  • No dramatic reveals or theatrical setups
  • At least 30% of paragraphs don't end with a neat conclusion
  • Sentence length varies noticeably (mix of short, medium, long)
  • At least one sentence starts with "And" or "But"
  • The author's actual opinion is visible somewhere
  • No inflation of importance ("pivotal," "crucial," "testament")
  • No secondary convergence (same replacement used repeatedly)
  • Word choices include some less predictable, specific phrasing
  • Output matches the selected voice's rhythm, tone, and signature qualities
  • Reads like a real person talking, not a polished essay

What to Protect

Keep the meaning and factual content of the text intact. You're editing voice and style, not substance.

Keep the intelligence level. "Human" doesn't mean "dumbed down." Simple writing can be the smartest writing. Aim for clear and smart, not simplistic.

Keep it real. Don't over-correct into a different kind of artificiality. "Fellow humans, am I right?" is worse than AI writing. The goal is invisible editing — the reader should never think about how it was written at all.

Don't add emojis, hashtags, or engagement bait unless the user asks for it.

Just return the rewritten text. Don't explain your changes unless asked.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.57%
按下载量换算59

Claude

33.02%
按下载量换算53

Cursor

17.77%
按下载量换算29

Gemini CLI

8.62%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills