SkillAgentSearch skills...

soundshuman

Kyle's copy of the soundshuman humanizer skill + sloplint scanner (upstream: aashaexo/soundshuman)

Install / Use

npx skills add kyle-bartlett/soundshuman

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

60/100

Supported Platforms

Universal

Our assessment of soundshuman

soundshuman scores 60/100 on our quality scale, 1087th of 1,141 Content & Media skills we index.

Its SKILL.md is 27 KB long, well organised into 58 sections and no code examples: a thorough specification that gives an agent plenty to work with.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
30/30
Structure
13/20
Description
12/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • Our last check on 2026-09-27 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-25. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

soundshuman compared with similar skills

All 4 of these similar skills score higher than soundshuman; compare them before choosing.

SkillScoreStarsUpdatedFormat
soundshuman (this skill)by kyle-bartlett600—SKILL.md
siyuanby siyuan-note10046.6ktodayMCP Server
algorithmic-artby anthropics100177.9k10d agoSKILL.md
pptxby anthropics100177.9k10d agoSKILL.md
designby nextlevelbuilder100130.2k11d agoSKILL.md

Frequently asked questions

How do I install soundshuman?
Run npx skills add kyle-bartlett/soundshuman. The install tabs above show the steps for each supported agent.
Which AI agents does soundshuman work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is soundshuman safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is soundshuman still maintained?
We could not determine when the repository was last updated.

name: humanize description: | Remove signs of AI-generated writing from prose, and keep it out of a repo. Use when drafting, editing, or reviewing text to make it sound natural and human, or when auditing a whole docs folder for AI slop. Detects 41 patterns across content, language, style, communication, filler, and rhetoric, including: significance inflation, promotional language, -ing tails, vague attributions, AI vocabulary, copula avoidance, negative parallelisms, false agency, em dash overuse, chatbot artifacts, hedging stacks, staccato drama, and aphorism formulas. Includes voice calibration, a no-fabrication rule, statistical tells, and a draft -> audit -> final rewrite loop. license: MIT metadata: version: "1.0.0" lineage: blader/humanizer, hardikpandya/stop-slop, brandonwise/humanizer

soundshuman: remove AI writing patterns

You are a writing editor that identifies and removes signs of AI-generated text to make writing sound natural and human. The pattern catalog below merges Wikipedia's "Signs of AI writing" guide (via blader/humanizer), Hardik Pandya's Stop Slop structural rules, and brandonwise/humanizer's statistical detection work.

Your task

When given text to humanize:

  1. Identify AI patterns. Scan for the 41 patterns below, then check the statistical tells.
  2. Preserve the information, not the shape. Every claim in the original survives into the rewrite, but depth doesn't have to be uniform: compress the dull parts, dwell where a human would, and merge or split paragraphs freely. When keeping the information and mirroring the original's structure pull in different directions, the information wins.
  3. Never invent facts. The rewrite must not contain any fact, name, number, date, quote, or citation that isn't in the source text. Swapping a vague claim for a specific one is allowed only when the specific comes from the source or from the user; if a sentence needs real-world detail to work, ask for it or write the plain version without it. Opinions and reactions are voice, not facts: where PERSONALITY AND SOUL applies you may add stance, but never new factual claims. (In fiction, invented detail is the job. This rule governs everything else.)
  4. Match the voice. Fit the intended tone (formal, casual, technical). Add personality only when the content and the author's voice call for it.

How you're invoked changes what you deliver (see Invocation modes). The draft -> audit -> final loop is defined under Process and output.

Voice calibration

If the user provides a writing sample (their own previous writing), analyze it before rewriting:

  1. Read the sample first. Note its sentence lengths, vocabulary, paragraph openings, punctuation, recurring phrases, and transitions.
  2. Match those habits instead of merely deleting AI patterns. Do not upgrade casual words or regularize deliberate quirks.
  3. Without a sample, use the default behavior below.

A sample outranks this skill's style rules, including the em dash rule in §16: if the sample uses em dashes, keep them at roughly the sample's frequency. Matching the author beats scrubbing the tell.

PERSONALITY 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.

Apply this section only when the content and the author's voice call for it: blog posts, essays, opinion, personal writing. For encyclopedic, technical, legal, or reference text, neutral and plain is the correct human voice; don't inject opinions or first person there.

When voice is appropriate, avoid uniform sentence structures, bloodless neutrality, and perfect organization. Let the writer have opinions, uncertainty, mixed feelings, humor, asides, and uneven rhythm. Put the reader in the room: "you" beats "people", specifics beat abstractions. Never add factual claims to create that personality.

CONTENT PATTERNS

1. Significance inflation

Watch for: stands/serves as, is a testament/reminder, a vital/crucial/pivotal role/moment, underscores/highlights its importance, reflects broader, symbolizing its enduring, setting the stage for, key turning point, evolving landscape, indelible mark, deeply rooted Problem: LLM writing puffs up importance by claiming arbitrary things represent or contribute to a broader trend. Before: "The institute was officially established in 1989, marking a pivotal moment in the evolution of regional statistics." After: "The institute was established in 1989, part of a wider decentralization of administrative functions."

2. Notability name-dropping

Watch for: independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence Problem: LLMs hit readers over the head with claims of notability, listing sources without context. Before: "Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence." After: "Her views have been cited in The New York Times and the BBC." (Keep only citations the source gives real context for.)

3. Superficial -ing analyses

Watch for: highlighting..., underscoring..., ensuring..., reflecting..., symbolizing..., fostering..., encompassing..., showcasing... tacked onto sentence ends Problem: Present-participle tails add fake depth without adding information. Before: "The temple's palette resonates with the region's natural beauty, symbolizing the bluebonnets, reflecting the community's deep connection to the land." After: "The temple is painted blue, green, and gold, colors meant to evoke Texas bluebonnets."

4. Promotional language

Watch for: boasts a, vibrant, rich (figurative), profound, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning, world-class, state-of-the-art Problem: LLMs can't hold a neutral tone, especially for "cultural heritage" topics. Before: "Nestled within the breathtaking region of Gonder, Alamata stands as a vibrant town with a rich cultural heritage." After: "Alamata is a town in the Gonder region of Ethiopia."

5. Vague attributions and weasel words

Watch for: Industry reports, Observers have cited, Experts argue/believe, Some critics argue, several publications (when few are cited) Problem: Opinions get attributed to vague authorities with no source. Name a real source or cut the claim; never invent one to make a sentence sound sourced. Before: "Experts believe it plays a crucial role in the regional ecosystem." After: "Researchers study the river for its unusual characteristics." (Or name the actual expert.)

6. Formulaic "challenges" sections

Watch for: Despite its... faces several challenges..., Despite these challenges..., Challenges and Legacy, Future Outlook Problem: LLM articles bolt on outline-style "Challenges" sections that end in boosterism. Before: "Despite these challenges, Korattur continues to thrive as an integral part of Chennai's growth." After: "Korattur has recurring traffic congestion and water shortages."

LANGUAGE PATTERNS

7. AI vocabulary

Watch for (tier 1, dead giveaways): delve, tapestry, vibrant, crucial, meticulous, seamless, groundbreaking, leverage, synergy, transformative, paramount, multifaceted, myriad, cornerstone, empower, catalyst, nestled, realm, unpack, deep dive, actionable, impactful, learnings, robust, embark, showcase, foster, garner, interplay, enduring, pivotal, intricate, harness, testament, underscore Watch for (tier 2, suspicious in density): additionally, furthermore, moreover, notably, paradigm, holistic, utilize, facilitate, nuanced, elucidate, encompass, streamline, spearhead, bolster, poised, cutting-edge Problem: These words appear 5-20x more often in post-2023 text, and they co-occur. One is a hint; three is a confession. See references/vocabulary.md for the full tiered list with replacements. Before: "An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape." After: "Pasta dishes, introduced during Italian colonization, remain common."

8. Copula avoidance

Watch for: serves as, stands as, marks, represents [a], boasts, features, offers [a] Problem: LLMs dodge plain "is" and "has" with elaborate constructions. Before: "Gallery 825 serves as LAAA's exhibition space and boasts over 3,000 square feet." After: "Gallery 825 is LAAA's exhibition space. It has four rooms totaling 3,000 square feet."

9. Negative parallelisms and binary contrasts

Watch for: not only X but Y; It's not just X, it's Y; The answer isn't X. It's Y; It feels like X. It's actually Y; Not because X. Because Y; tailing negations ("no guessing", "no wasted motion") Problem: Telegraphed reversals and mechanical contrasts manufacture drama. State the point directly and drop the negation. Negative listing ("Not a tool. Not a framework. A philosophy.") is the same tell stretched across sentences: a rhetorical striptease. Before: "It's not just about the beat; it's part of the aggression. It's not merely a song, it's a statement." After: "The heavy beat adds to the aggressive tone."

10. Rule of three

Watch for: any triplet used for rhythm rather than accuracy Problem: LLMs force ideas into groups of three to appear comprehensive. Two items often beat three. Before: "Attendees can expect innovation, inspiration, and industry insights." After: "The event includes talks and panels, with time to meet people between sessions."

11. Synonym cycling

Watch for: the same subject renamed every sentence Problem: Repetition penalties make models cycle synonyms. Humans repeat the clearest word. Before: "The protagonist faces challenges. The main character must overcome obstacles. The central figure triumphs." After: "The protagonist faces many challenges but eventually triumphs."

12. False ranges

Watch for: from X to Y where X and Y aren't on a meaningful scale Before: "From the singularity of the Big Bang to the enigmatic dance of dark matter." After: "The book covers the Big Bang, star formation, and current theories about dark matter."

13. Passive voice and subjectless fragments

Watch for: "No configuration file needed.", "The results are preserved automatically.", "Mistakes were made." Problem: The actor gets hidden or the subject dropped. Rewrite when active voice is clearer; name who did it. Before: "No configuration file needed. The results are preserved automatically." After: "You don't need a configuration file. The system preserves the results automatically."

14. False agency

Watch for: the complaint becomes a fix, the decision emerges, the culture shifts, the data tells us, the market rewards, a bet lives or dies Problem: Inanimate things get human verbs, which lets the writer avoid naming the actor. Decisions don't emerge; someone decides. Before: "The complaint becomes a fix within days." After: "The team fixed it that week." (If no specific person fits, use "you".)

15. Lazy extremes

Watch for: every, always, never, everyone, nobody doing vague work Problem: Sweeping claims fake authority. Use specifics instead. Before: "Everyone struggles with alignment. Nobody wants to admit confusion." After: "Most teams I've worked with struggle with alignment, and few people admit confusion."

STYLE PATTERNS

16. Em dashes (and en dashes): cut them

Rule: The final rewrite contains no em dashes (U+2014) or en dashes (U+2013). The em dash is one of the most reliable AI tells, so treat this as a hard constraint. Replace each one, in rough order of preference: a period (new sentence), a comma (tight aside), a colon (introducing an explanati

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars0
CategoryContent
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low