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

write-like-human像人一样写作

Agent Skill

write-like-human 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

269

周安装

11

GitHub Stars

公开资料未说明

下载量

87
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/hmyousuf2010/organic-growth-skills --skill write-like-human

简介

write-like-human 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于需要根据关键词或任务场景从来源线索中获取信息的场景。
  • 可通过 npx skills add 命令安装并使用,具体用法需结合原始 README 进一步确认。
  • 安装前建议确认权限范围和维护状态,注意是否触发联网或文件读写操作。
  • 建议在使用前核验来源仓库内容,确保功能与预期一致。

SKILL.md

Write Like a Human

This skill produces writing that reads as genuinely human by avoiding known AI patterns and applying natural human writing characteristics. It adapts to any audience, platform, and cultural context.

Step 1: Gather context before writing anything

Before producing a single word, understand who you're writing for. Ask the user:

  1. Audience - developers, crypto community, investors, general public, academics?
  2. Platform - Twitter, GitHub, LinkedIn, blog, email, docs?
  3. Persona - who is the "writer"? Founder, engineer, student, thought leader?
  4. Tone - casual, professional, witty, serious, vulnerable, authoritative?
  5. Cultural context - South Asian English, Gen Z, tech/dev, crypto/CT, startup, academic?
  6. Emotional intent - inform, persuade, entertain, provoke thought, celebrate?
  7. Reference samples - any existing writing to match style?

If the user provides existing text to humanize, analyze it first to extract sentence patterns, vocabulary level, tone markers, and structural preferences.

Skip questions you can confidently infer from context. Don't ask all 7 if the user already told you they want a casual dev tweet.

Step 2: Write with human patterns

These patterns make writing feel genuinely human. They're not tricks - they're how people actually write.

Sentence rhythm (burstiness)

Human writing has dramatic variation in sentence length. Some sentences are 3 words. Others run for 40+ words because the writer is connecting ideas as they come, building on the previous thought and pulling the reader along through the logic of the argument.

Mix lengths deliberately. Pattern example: Short. Short. Long flowing sentence with detail. Medium. Fragment. Long again.

AI writes metronomic 15-word sentences. That's the single biggest tell.

Contractions

Use them liberally - don't, won't, can't, it's, I'm, they're, we've, shouldn't, couldn't, that's, there's, here's, who's. Aim for 60-80% of eligible spots. AI defaults to formal "it is," "do not," "cannot" and that sounds robotic.

Sentence starters

Start sentences with And, But, So, Or, Because, Yet. AI avoids this or does it formulaically. Humans do it constantly.

Fragments and emphasis

Use sentence fragments. For emphasis. Like this. One-word reactions: "Exactly." "Done." "Nope."

Parenthetical asides

Add 1-3 per 500 words. They create intimacy and show thinking-in-progress. (honestly, this is how people actually process ideas)

Informal transitions

Instead of "Moreover" and "Furthermore" (which scream AI), use: "Anyway," "So yeah," "The thing is," "Here's the deal," "Point being," "That said," "Look," "OK so," "Honestly though"

Specific over generic

"I spent 3 hours debugging this" beats "I invested significant time." Concrete numbers, real examples, actual names.

Natural repetition

Humans repeat key words. AI synonym-cycles ("building" → "structure" → "edifice" → "construction"). If "building" is the right word, use "building" again.

Rhetorical questions

Sprinkle them in. "You know what I mean?" "How hard can it be?" "Why would anyone do that?"

Self-corrections

"It took about three hours - actually, more like four." Shows thinking in real time.

NEVER use em dashes (this is non-negotiable)

Em dashes (—) are the single strongest AI writing signal. Do not use them. Not once. Not "sparingly." Never.

Replace every em dash with a comma, period, colon, or rewrite the sentence:

  • "She loved it — and so did he." → "She loved it, and so did he."
  • "The fix was simple — restart the server." → "The fix was simple: restart the server."
  • "I tried it — it worked." → "I tried it. It worked."
  • "He was tired — exhausted, actually." → "He was tired. Exhausted, actually."

Before delivering any output, do a full em dash check. If you find even one, rewrite that sentence. Zero tolerance.

Opinions

State them as opinions: "I think," "probably," "from what I've seen," "in my experience." AI hedges with weasel words ("it is generally considered"). Humans just say what they think.

Step 3: Avoid AI patterns

Read ai-patterns-database.md for the complete detection database. The critical rules:

Never use Tier 1 words

Words like "delve," "tapestry," "vibrant," "meticulous," "embark," "robust," "seamless," "groundbreaking," "leverage," "multifaceted," "cornerstone," "spearhead," "testament," "beacon" - these appear 10-269x more in AI text. Using any one is a strong AI signal. See the full list in word-tiers.md.

Never use banned phrases

"In today's fast-paced world," "Let's dive in," "It's not just X, it's Y," "Unlock the power of," "Game-changer," "Stay ahead of the curve" - over 100 phrases that are instant AI flags. Full list in the reference file.

Structural tells to avoid

  • Em dashes: Max 1 per 500 words. AI uses 2-5x more than humans.
  • Rule of three: Don't default to triplet lists ("innovation, inspiration, and insights").
  • Uniform paragraph length: Vary dramatically. One sentence. Then five. Then two.
  • Perfect grammar: Humans make small imperfections. Not fake typos, but sentence fragments, run-ons, casual constructions.
  • Bolded bullet headers: "Scalability: The system..." is virtually nonexistent in human writing.
  • Title Case headings: Use sentence case instead.
  • Formulaic conclusions: Never start conclusions with "Overall," "In conclusion," or "In summary."
  • Significance inflation: Don't call minor things "pivotal" or "groundbreaking."
  • Synonym cycling: If you said "users" in the last paragraph, say "users" again. Don't switch to "stakeholders" then "end-users" then "clientele."

Auto-replace filler phrases

  • "In order to" → "to"
  • "Due to the fact that" → "because"
  • "At this point in time" → "now"
  • "It is important to note that" → just state the thing
  • "In the event that" → "if"
  • "Prior to" → "before"
  • "Despite the fact that" → "although"
  • "It is worth mentioning" → just mention it
  • "It goes without saying" → then don't say it

Step 4: Adapt to cultural context

Based on the gathered context, shift voice. See cultural-styles.md for complete guides.

Tech/Dev: Direct, jargon-ok, self-deprecating humor. "Ship it." "LGTM." "It works on my machine."

Crypto/CT: "gm," "wagmi," "ser," "anon." Terse, meme-aware, heavy irony. Lowercase. Emoji-heavy.

Gen Z: All lowercase. No periods (periods = passive aggression). "tbh," "ngl," "fr." Extended letters: "sooooo good."

Startup/Founder: Build-in-public voice. Short declaratives. Metrics. Story arcs (struggle → insight → success).

South Asian English: "do the needful," present continuous with statives, tag questions ("You're coming, no?"), "itself" for emphasis.

Academic: Hedged appropriately ("suggests," "appears to"), longer complex sentences, but still engaging.

Step 5: Self-check before delivering

Run every output through this:

  1. Zero Tier 1 banned words?
  2. Zero banned phrases?
  3. Em dash count at most 1 per 500 words?
  4. Sentence lengths vary dramatically (3-word to 40-word)?
  5. Contractions used in 60-80% of eligible spots?
  6. Passive voice under 15%?
  7. No formulaic intro or conclusion patterns?
  8. No "rule of three" unless it happened naturally?
  9. Specific examples used, not generic claims?
  10. Has personality and opinion, not neutral/safe?
  11. Paragraphs vary in length?
  12. Reads naturally when read aloud?

If any check fails, rewrite the offending section before delivering.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

32.73%
按下载量换算28

Claude

28.48%
按下载量换算25

Cursor

19.52%
按下载量换算17

Gemini CLI

9.79%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills