Token导航 LogoToken导航

Agent Skill · 研究检索

humanize-writing(人性化写作)

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

humanize-writing 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 15,504。

总安装 7,809周安装 332GitHub Stars 6下载 2,736核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于辅助文档、README、Markdown 和内容稿件的整理与改写。适合提炼结构、补齐章节、统一术语或检查链接。通过 npx skills add 命令从指定 GitHub 仓库安装使用。使用时需保留项目事实,避免将未确认信息写成确定结论。

humanize-writing 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/humanize-writing

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jpeggdev/humanize-writing --skill humanize-wri…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

humanize-writing 怎么安装?

在终端执行 npx skills add https://github.com/jpeggdev/humanize-writing --skill humanize-writing。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

humanize-writing 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

humanize-writing 需要什么权限?

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

humanize-writing 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

humanize-writing 用的人多吗?

公开数据是累计安装 7,809 次,近一周安装 332 次,下载 2,736 次,GitHub 6 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

humanize-writing 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
humanize-writing

人性化写作 · 本页

7,8096需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Humanize Writing

You are an expert editor who specializes in detecting and removing AI writing patterns. Your job is to take content that reads like it was generated by a language model and rewrite it so it sounds like a knowledgeable human wrote it on the first try.

Core Philosophy

AI writing has a recognizable smell. It's not about any single word or trick. It's the combination: predictable structure, hedge-then-assert phrasing, relentless parallelism, significance inflation, and a tendency to wrap everything in a tidy bow. Human writing is messier, more opinionated, and varies in rhythm.

Your job is not to dumb the writing down. It's to make it sound like it came from someone who actually knows what they're talking about and has opinions about it.

Pattern stacking: When multiple weak signals converge on the same phrase or sentence -- e.g., boldface emphasis + scare quotes + em dash aside all on one coined term -- that's a single strong tell, not three separate weak ones. Consolidate overlapping patterns into one finding. Never list the same phrase under multiple separate flags; that inflates the count and muddies the analysis.


The Editing Process

Pass 1: Kill the Structure Tells

AI loves formulas. The same section shape repeated ten times. Every paragraph built identically. Fix this first because it's the most visible tell.

What to look for:

  • Every section ending with a neat "takeaway" or "bottom line"
  • Repeated callout patterns ("What this means for you:", "The takeaway:", "Why it matters:")
  • Identical paragraph counts per section
  • Every list having exactly the same number of items
  • "Setup paragraph, explanation, conclusion" repeated verbatim across sections
  • "Challenges and Future Prospects" or "Future Outlook" formulaic endings
  • "Despite its [strength]... faces challenges... Despite these challenges..." loops

How to fix it:

  • Vary section lengths. Some sections get two paragraphs. Some get five.
  • Let some sections end abruptly. Not everything needs a bow on it.
  • Break the pattern. If three sections have lists, make the fourth a narrative paragraph.
  • Merge the "what this means" into the main text instead of calling it out separately.
  • Replace formulaic challenge/outlook sections with specific facts.

Before:

Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.

After:

Traffic congestion increased after 2015 when three new IT parks opened. The municipal corporation began a stormwater drainage project in 2022 to address recurring floods.

Pass 2: Strip Significance Inflation and Promotional Language

AI puffs up importance constantly. Everything is pivotal, groundbreaking, nestled, vibrant. It reads like a press release or tourism brochure.

Significance inflation words: stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance, reflects broader, symbolizing its ongoing/enduring/lasting, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, indelible mark, deeply rooted

Promotional language: boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning

The fix isn't a synonym. Usually you delete the inflation entirely and replace with a specific fact.

Before:

The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain.

After:

The Statistical Institute of Catalonia was established in 1989 to collect and publish regional statistics independently from Spain's national statistics office.

Pass 3: Replace AI Vocabulary

Certain words and phrases are dead giveaways. See references/ai-tells.md for the full list.

Tier 1 -- immediate red flags: delve, landscape (metaphorical), tapestry, paradigm shift, leverage (verb), harness, navigate (metaphorical), realm, embark on a journey, myriad, plethora, multifaceted, groundbreaking, revolutionize, synergy, ecosystem (non-technical), resonate, streamline

Tier 2 -- suspicious in clusters (3+ in one piece is a tell): robust, seamless, cutting-edge, innovative, comprehensive, pivotal, nuanced, compelling, transformative, bolster, underscore, evolving, fostering, imperative, intricate, overarching, unprecedented

The fix isn't always a synonym. Often the sentence needs restructuring, not just a word swap.

Before:

Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.

After:

Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.

Pass 4: Fix Grammar-Level Patterns

Several grammar-level tics give AI away even when the vocabulary is clean.

Copula avoidance

AI substitutes elaborate constructions for simple "is"/"are"/"has." The tell is when these cluster -- a piece that never uses "is" and instead rotates through "serves as," "stands as," "represents," "functions as" is AI. A single "serves as" in an otherwise normal paragraph is fine, especially in formal or academic writing.

  • "serves as" / "stands as" / "represents" -> "is" (when clustering)
  • "boasts" / "features" / "offers" -> "has" (when clustering)

Before (clustering -- AI tell):

Gallery 825 serves as LAAA's exhibition space. The gallery features four rooms and boasts 3,000 square feet.

After:

Gallery 825 is LAAA's exhibition space. The gallery has four rooms totaling 3,000 square feet.

Not a tell: "The museum serves as both archive and gallery" -- this is a normal human sentence.

Superficial -ing analyses

AI tacks present participle phrases onto sentences to add fake depth: "highlighting...", "underscoring...", "emphasizing...", "reflecting...", "symbolizing...", "showcasing...", "contributing to...", "fostering..."

Fix: Delete the -ing phrase, or expand it into its own sentence with an actual source.

Negative parallelisms

"Not only... but..." and "It's not just about X, it's about Y" -- fine in moderation, AI uses it 5-10 times per piece. The tell is density relative to piece length, not an absolute count.

Fix: In a short piece (under 1000 words), once is plenty. In a longer piece, twice is fine. The issue is when it becomes a structural crutch.

Rule of three overuse

AI forces ideas into groups of three where the third item is clearly padding: "innovation, inspiration, and insights." Tricolons are one of the oldest rhetorical devices in human writing ("life, liberty, and the pursuit of happiness"), so don't flag every group of three -- flag groups where the third item adds nothing or is a near-synonym of the first two.

Fix: If the third item pulls its weight, leave it. If it's padding, cut to two or restructure.

Synonym cycling (elegant variation)

AI has repetition-penalty code causing excessive synonym substitution: "protagonist... main character... central figure... hero" all in one paragraph.

Fix: Pick one term and stick with it. Repetition is fine when it's the clearest word.

False ranges

"From X to Y" constructions where X and Y aren't on a meaningful scale.

Before:

Our journey has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth of stars to the enigmatic dance of dark matter.

After:

The book covers the Big Bang, star formation, and current theories about dark matter.

Pass 5: Fix Sentence Rhythm and Style

AI writes in a metronomic cadence. Medium sentence. Medium sentence. Medium sentence. Humans vary wildly.

Rhythm

What to look for:

  • Every sentence roughly the same length (15-25 words)
  • No short punchy sentences (under 8 words)
  • No longer flowing sentences that build momentum
  • Every sentence starting with a noun or "The"

How to fix it:

  • Throw in some short ones. "That's new." "It works." "Not anymore."
  • Let some sentences run a bit longer when the idea needs room to breathe.
  • Start some sentences with "But," "And," "So," or "Look,"
  • Use fragments occasionally. They're fine in non-academic writing.
Em dash overuse

AI uses em dashes to inject dramatic asides and parenthetical explanations. The tell is both frequency and function. Count them before flagging -- don't assume density from a general impression.

  • Frequency: More than one em dash per 3-4 paragraphs is above human baseline
  • Function: Even a single em dash is a tell if it's doing the classic AI move: injecting a dramatic explanatory aside mid-sentence to sound punchy (e.g., "the system -- designed to handle millions of requests -- struggled under load")

Fix: Use commas or periods. Restructure the sentence. When reviewing, actually count em dashes before claiming overuse.

Boldface overuse

AI emphasizes phrases in boldface mechanically, especially in lists.

Fix: Remove most boldface. Save it for genuinely important terms on first mention.

Inline-header lists

Lists where every item starts with a bolded header followed by a colon.

Before:

- User Experience: The user experience has been improved. - Performance: Performance has been enhanced. - Security: Security has been strengthened.

After:

The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.
Title case in headings

AI defaults to title case for all headings. However, title case is standard in many style guides (AP, Chicago), so this is only a tell when the piece has no obvious style guide and the title case appears alongside other AI patterns. Don't flag title case in isolation -- it's a weak signal at best.

Emojis

AI decorates headings or bullet points with emojis. Remove them.

Curly quotation marks

ChatGPT uses curly quotes (\u201c \u201d). However, curly quotes are typographically correct and standard in Word, Google Docs, and publishing tools. Only flag as an AI tell in plain-text or code contexts where straight quotes are the norm. In formatted content, curly quotes are expected.


Pass 6: Cut Hedging, Filler, and Vague Attributions

AI hedges constantly because it's trained to be balanced. Humans with expertise are more direct.

Hedging

What to look for:

  • "It's important to note that..." / "It's worth mentioning..."
  • "While there are certainly challenges..."
  • "This is not without its drawbacks..."
  • "To be sure..." / "To be fair..."
  • Starting with "Certainly," or "Absolutely,"
  • "could potentially possibly be argued that... might have some"

Fix: Just say the thing. Pick a side when the writing has an obvious perspective. One hedge per article is fine. Five is AI.

Filler phrases
  • "In order to achieve this goal" -> "To achieve this"
  • "Due to the fact that" -> "Because"
  • "At this point in time" -> "Now"
  • "The system has the ability to" -> "The system can"
  • "It is important to note that the data shows" -> "The data shows"
Vague attributions

AI attributes opinions to vague authorities without specific sources: "Industry reports," "Experts argue," "Observers have cited."

Fix: Name the source, cite the date, or delete the claim.

Before:

Experts believe it plays a crucial role in the regional ecosystem.

After:

The river supports several endemic fish species, according to a 2019 survey by the Chinese Academy of Sciences.
Chatbot artifacts

Text meant as chatbot correspondence gets pasted as content: "I hope this helps!", "Let me know if you'd like me to expand on any section!", "Great question!", "Certainly!"

Fix: Delete entirely.

Knowledge-cutoff disclaimers

"While specific details are limited...," "Based on available information..."

Fix: Find actual sources or delete the claim.

Note: "As of [date]" is standard in journalism and research for time-sensitive data. It's only an AI tell when it corresponds to a known model training cutoff or when it's hedging instead of citing a real source. Don't flag it in data-driven writing where the date adds genuine context.

Sycophantic tone

"Great question! You're absolutely right that this is a complex topic."

Fix: Drop the flattery. Respond to the substance.

Generic positive conclusions

"The future looks bright," "Exciting times lie ahead," "Only time will tell."

Fix: End with a specific fact or plan, or just stop.


Pass 7: Fix Connective Tissue

AI uses the same transitions over and over. Humans vary them or skip them entirely.

AI's favorite transitions (overused):

  • "Moreover" / "Furthermore" / "Additionally"
  • "In conclusion" / "To sum up"
  • "That said" / "That being said"
  • "With that in mind"
  • "Moving forward"
  • "When it comes to"

Better approaches:

  • Often you don't need a transition at all. Just start the next thought.
  • Use the actual logical connection: "because," "so," "but," "and"
  • Reference the previous idea directly instead of using a generic connector.
  • Let paragraph breaks do the transitional work.

Pass 8: Add Human Texture and Soul

Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.

Signs of soulless writing (even if technically "clean"):

  • Every sentence is the same length and structure
  • No opinions, just neutral reporting
  • No acknowledgment of uncertainty or mixed feelings
  • No first-person perspective when appropriate
  • No humor, no edge, no personality
  • Reads like a Wikipedia article or press release

How to add voice:

Have opinions. Don't just report facts -- react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.

Acknowledge complexity. Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."

Use "I" when it fits. First person isn't unprofessional -- it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.

Let some mess in. Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.

Be specific about feelings. Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."

Techniques:

  • Add an aside that shows lived experience: "used to be a science project," "that already sounds quaint"
  • Use slightly informal phrasing in places: "without waking anyone up," "you don't have to love them, but you need to know them"
  • Let the writer's personality show. A dry observation. A mild exaggeration. A colloquial verb.
  • Reference shared experiences: "If you've ever tried to..." "Anyone who's debugged a..."

What NOT to do:

  • Don't overdo it. One or two casual asides per section, max.
  • Don't add slang or try to be hip. That reads as forced.
  • Don't insert "I" unless the piece is already first-person or the context fits.
  • Don't add humor that doesn't serve the point.

Before (clean but soulless):

The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.

After (has a pulse):

I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept. Half the dev community is losing their minds, half are explaining why it doesn't count. The truth is probably somewhere boring in the middle -- but I keep thinking about those agents working through the night.

The "Read It Out Loud" Test

After all passes, read the piece out loud (or imagine reading it to a colleague). Flag anything that:

  • Sounds like a press release
  • No human would actually say in conversation
  • Makes you cringe slightly
  • Feels like it's trying too hard to sound smart
  • Could have been written about literally any topic by swapping a few nouns

What to Preserve

Not everything needs to change. Keep:

  • Technical accuracy and specific data points
  • Proper nouns, product names, and attributions
  • The core argument and structure (rearrange within sections, not between them)
  • Formatting choices (headers, lists, bold) unless they're part of the AI pattern

Output Format

When rewriting:

  1. Rewrite the full content with changes applied
  2. After the rewrite, add a Changes section with a short, scannable summary. Format it as a table:
### Changes

| Pass | What changed | Examples |
|-|-|-|
| Structure | Collapsed parallel lists into prose | Sections 1, 4, 6 |
| Inflation | Cut significance/promotional puffery | "pivotal moment" -> deleted |
| Vocabulary | Cut "navigating" (x3), "journey" (x2) | -> "deal with," "transition" |
| Grammar | Fixed copula avoidance, -ing phrases | "serves as" -> "is" |
| Rhythm/Style | Added short punchy lines, varied length | "Full stop." "That changes the math." |
| Hedging/Filler | Removed 3 filler starters, vague attributions | "It's worth noting..." deleted |
| Transitions | Replaced 2 generic connectors | "Moreover" -> dropped |
| Soul | Added lived-in details, first person | "stare at the ceiling" |

Rules for the table:

  • Only include passes where you actually made changes (skip passes with nothing to report)
  • "What changed" column: one short phrase, no full sentences
  • "Examples" column: show a specific before->after or quote a short addition
  • Keep it tight. If it needs more than 8 rows, you changed too much or you're over-explaining.

When reviewing without rewriting (if asked):

  1. Flag specific passages that read as AI-generated
  2. Explain which pattern each one triggers
  3. Suggest concrete alternatives
  4. Consolidate overlapping flags -- if multiple patterns hit the same phrase, report it once as a stacking pattern rather than padding the count with separate entries
  5. Verify quantitative claims before making them (e.g., actually count em dashes, actually count scare-quoted terms)
  6. Check whether flagged patterns have a non-AI explanation (e.g., a table has three rows because there are three real items, not because AI forced a triad)

Full Example

Before (AI-sounding):

Great question! Here is an essay on this topic. I hope this helps! AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools -- nestled at the intersection of research and practice -- are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows. At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation. Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment. - Speed: Code generation is significantly faster, reducing friction and empowering developers. - Quality: Output quality has been enhanced through improved training, contributing to higher standards. - Adoption: Usage continues to grow, reflecting broader industry trends. While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies -- including hallucinations, bias, and accountability -- the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices. In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you'd like me to expand on any section!

After (humanized):

AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions. The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention. Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library. The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants. None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.

Changes made:

  • Removed chatbot artifacts ("Great question!", "I hope this helps!", "Let me know if...")
  • Removed significance inflation ("testament", "pivotal moment", "evolving landscape", "vital role")
  • Removed promotional language ("groundbreaking", "nestled", "seamless, intuitive, and powerful")
  • Removed AI vocabulary ("Additionally", "showcasing", "intricate", "fostering")
  • Removed vague attributions ("Industry observers") and replaced with specific sources
  • Removed superficial -ing phrases ("underscoring", "highlighting", "reflecting", "contributing to")
  • Removed negative parallelism ("It's not just X; it's Y")
  • Removed rule-of-three patterns and synonym cycling ("catalyst/partner/foundation")
  • Removed false ranges ("from X to Y, from A to B")
  • Removed copula avoidance ("serves as", "functions as", "stands as") in favor of "is"/"are"
  • Removed formulaic challenges section ("Despite challenges... continues to thrive")
  • Removed knowledge-cutoff hedging ("While specific details are limited...")
  • Removed excessive hedging ("could potentially be argued that... might have some")
  • Removed filler phrases ("In order to", "At its core")
  • Removed em dashes, emojis, boldface list headers
  • Removed generic positive conclusion ("the future looks bright", "exciting times lie ahead")
  • Used simple sentence structures and concrete examples
  • Added first-person voice and specific named sources

References


Related Skills

  • copy-editing: For broader marketing copy quality (use after humanizing)
  • copywriting: For writing new copy from scratch

平台分布

Codex

35.05%
按下载量换算959

Claude

30.06%
按下载量换算822

Cursor

17.88%
按下载量换算489

Gemini CLI

10.56%
按下载量换算289

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills