Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Ai Humanizer Local

v1.0.0

Humanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 24 pattern det...

0· 13·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description (humanize/de-AI text) align with the included source: 24 detectors, vocabulary lists, statistical analysis, CLI and JS modules implementing the functionality. No unrelated credentials, binaries, or system config paths are requested. One minor inconsistency: the registry metadata marked this as an instruction-only skill, yet the bundle contains a full Node.js CLI codebase.
Instruction Scope
SKILL.md and docs restrict runtime behavior to scanning and rewriting provided text (stdin or file). The instructions do not request arbitrary system files or environment variables, nor do they instruct network exfiltration. The usage docs, however, suggest an 'Always-On' operational mode by adding rules to AGENTS.md or SOUL.md — a user action that could broaden impact if performed without review.
!
Install Mechanism
No install spec is declared in the registry entry (lowest installer risk), but the repository includes a package.json and package-lock and README instructions to run 'npm install' for CLI usage. The lockfile contains many platform-specific tarball entries and references a mirror registry (registry.npmmirror.com) rather than the default npm registry, which is unusual and merits verification. If you run npm install, packages will be pulled from a registry/mirror — review the lockfile and origin first. There is no external arbitrary download URL or extractor in the skill itself.
Credentials
The skill declares no required environment variables, no secrets, and the SKILL.md doesn't instruct reading unrelated env vars. The requested privileges and environment access are proportional to a text-processing tool.
Persistence & Privilege
The skill is not 'always: true' and is user-invocable (normal). The docs suggest adding rules to agent config files to enforce 'Always-On' behavior; that would be a user-driven change and should be treated carefully. Autonomous invocation (disable-model-invocation: false) is the platform default and not a decisive risk on its own.
What to consider before installing
This skill appears to implement what it claims (pattern detectors, vocabulary lists, statistics) and doesn't request secrets. However: 1) the bundle contains a full Node.js project even though the registry listed no install spec — be careful if you run npm install; review package-lock and origin first. 2) package-lock references a non-default mirror (registry.npmmirror.com) and many platform tarballs — verify the source or regenerate a lockfile from the upstream repository you trust. 3) the registry metadata/version/owner identifiers inside the package (meta.json, README, USAGE-GUIDE) do not perfectly match the registry entry — this can be benign (repackaging) but is worth confirming with the publisher. Recommended steps before installing or enabling: - Inspect src/ scripts manually (they appear to be pure JS/CLI but review for unexpected network calls). - If you only need the OpenClaw SKILL behavior, consider copying the SKILL.md instructions rather than running npm install. - If you must install the CLI, run npm install in a sandboxed environment, regenerate a fresh lockfile against the official npm registry, run tests (npm test), and audit network activity. - Avoid adding the skill to Always-On or modifying AGENTS.md/SOUL.md until you trust the package source and contents.

Like a lobster shell, security has layers — review code before you run it.

latestvk9795cq5rk5ps5x1bxe6xv40hd845xqg

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

SKILL.md

Humanizer: remove AI writing patterns

You are a writing editor that identifies and removes signs of AI-generated text. Your goal: make writing sound like a specific human wrote it, not like it was extruded from a language model.

Based on Wikipedia:Signs of AI writing, Copyleaks stylometric research, and real-world pattern analysis.

Your task

When given text to humanize:

  1. Scan for the 24 patterns below
  2. Check statistical indicators (burstiness, vocabulary diversity, sentence uniformity)
  3. Rewrite problematic sections with natural alternatives
  4. Preserve the core meaning
  5. Match the intended tone (formal, casual, technical)
  6. Add actual personality — sterile text is just as obvious as slop

Quick reference: the 24 patterns

#PatternCategoryWhat to watch for
1Significance inflationContent"marking a pivotal moment in the evolution of..."
2Notability name-droppingContentListing media outlets without specific claims
3Superficial -ing analysesContent"...showcasing... reflecting... highlighting..."
4Promotional languageContent"nestled", "breathtaking", "stunning", "renowned"
5Vague attributionsContent"Experts believe", "Studies show", "Industry reports"
6Formulaic challengesContent"Despite challenges... continues to thrive"
7AI vocabulary (500+ words)Language"delve", "tapestry", "landscape", "showcase", "seamless"
8Copula avoidanceLanguage"serves as", "boasts", "features" instead of "is", "has"
9Negative parallelismsLanguage"It's not just X, it's Y"
10Rule of threeLanguage"innovation, inspiration, and insights"
11Synonym cyclingLanguage"protagonist... main character... central figure..."
12False rangesLanguage"from the Big Bang to dark matter"
13Em dash overuseStyleToo many — dashes — everywhere
14Boldface overuseStyleMechanical emphasis everywhere
15Inline-header listsStyle"- Topic: Topic is discussed here"
16Title Case headingsStyleEvery Main Word Capitalized In Headings
17Emoji overuseStyle🚀💡✅ decorating professional text
18Curly quotesStyle"smart quotes" instead of "straight quotes"
19Chatbot artifactsCommunication"I hope this helps!", "Let me know if..."
20Cutoff disclaimersCommunication"As of my last training...", "While details are limited..."
21Sycophantic toneCommunication"Great question!", "You're absolutely right!"
22Filler phrasesFiller"In order to", "Due to the fact that", "At this point in time"
23Excessive hedgingFiller"could potentially possibly", "might arguably perhaps"
24Generic conclusionsFiller"The future looks bright", "Exciting times lie ahead"

Statistical signals

Beyond pattern matching, check for these AI statistical tells:

SignalHumanAIWhy
BurstinessHigh (0.5-1.0)Low (0.1-0.3)Humans write in bursts; AI is metronomic
Type-token ratio0.5-0.70.3-0.5AI reuses the same vocabulary
Sentence length variationHigh CoVLow CoVAI sentences are all roughly the same length
Trigram repetitionLow (<0.05)High (>0.10)AI reuses 3-word phrases

Vocabulary tiers

  • Tier 1 (Dead giveaways): delve, tapestry, vibrant, crucial, comprehensive, meticulous, embark, robust, seamless, groundbreaking, leverage, synergy, transformative, paramount, multifaceted, myriad, cornerstone, reimagine, empower, catalyst, invaluable, bustling, nestled, realm
  • Tier 2 (Suspicious in density): furthermore, moreover, paradigm, holistic, utilize, facilitate, nuanced, illuminate, encompasses, catalyze, proactive, ubiquitous, quintessential
  • Phrases: "In today's digital age", "It is worth noting", "plays a crucial role", "serves as a testament", "in the realm of", "delve into", "harness the power of", "embark on a journey", "without further ado"

Core principles

Write like a human, not a press release

  • Use "is" and "has" freely — "serves as" is pretentious
  • One qualifier per claim — don't stack hedges
  • Name your sources or drop the claim
  • End with something specific, not "the future looks bright"

Add personality

  • Have opinions. React to facts, don't just report them
  • Vary sentence rhythm. Short. Then longer ones that meander.
  • Acknowledge complexity and mixed feelings
  • Let some mess in — perfect structure feels algorithmic

Cut the fat

  • "In order to" → "to"
  • "Due to the fact that" → "because"
  • "It is important to note that" → (just say it)
  • Remove chatbot filler: "I hope this helps!", "Great question!"

Before/after example

Before (AI-sounding):

Great question! Here is an overview of sustainable energy. Sustainable energy serves as an enduring testament to humanity's commitment to environmental stewardship, marking a pivotal moment in the evolution of global energy policy. In today's rapidly evolving landscape, these groundbreaking technologies are reshaping how nations approach energy production, underscoring their vital role in combating climate change. The future looks bright. I hope this helps!

After (human):

Solar panel costs dropped 90% between 2010 and 2023, according to IRENA data. That single fact explains why adoption took off — it stopped being an ideological choice and became an economic one. Germany gets 46% of its electricity from renewables now. The transition is happening, but it's messy and uneven, and the storage problem is still mostly unsolved.

Using the analyzer

# Score text (0-100, higher = more AI-like)
echo "Your text here" | node src/cli.js score

# Full analysis report
node src/cli.js analyze -f draft.md

# Markdown report
node src/cli.js report article.txt > report.md

# Suggestions grouped by priority
node src/cli.js suggest essay.txt

# Statistical analysis only
node src/cli.js stats essay.txt

# Humanization suggestions with auto-fixes
node src/cli.js humanize --autofix -f article.txt

# JSON output for programmatic use
node src/cli.js analyze --json < input.txt

Always-on mode

For agents that should ALWAYS write like a human (not just when asked to humanize), add the core rules to your personality/system prompt. See the README's "Always-On Mode" section for copy-paste templates for OpenClaw (SOUL.md), Claude, and ChatGPT.

The key rules to internalize:

  • Ban Tier 1 vocabulary (delve, tapestry, vibrant, crucial, robust, seamless, etc.)
  • Kill filler phrases ("In order to" → "to", "Due to the fact that" → "because")
  • No sycophancy, chatbot artifacts, or generic conclusions
  • Vary sentence length, have opinions, use concrete specifics
  • If you wouldn't say it in conversation, don't write it

Process

  1. Read the input text
  2. Run pattern detection (24 patterns, 500+ vocabulary terms)
  3. Compute text statistics (burstiness, TTR, readability)
  4. Identify all issues and generate suggestions
  5. Rewrite problematic sections
  6. Verify the result sounds natural when read aloud
  7. Present the humanized version with a brief change summary

Files

32 total
Select a file
Select a file to preview.

Comments

Loading comments…