li-human
Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out
Install / Use
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-humanInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of li-human
li-human scores 82/100 on our quality scale, 3415th of 4,702 Development & Engineering skills we index.
Its SKILL.md is 4.4 KB long, split into 6 sections with 1 code example: a solid amount of guidance for an agent.
It has 671 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so li-human is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur 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-10-05. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
li-human compared with similar skills
All 4 of these similar skills score higher than li-human; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| li-human (this skill)by Jakeschincariol | 82 | 671 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.9k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
Frequently asked questions
- How do I install li-human?
- Run
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-human. The install tabs above show the steps for each supported agent. - Which AI agents does li-human 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 li-human 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 is MIT-licensed and scores 100/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 li-human still maintained?
- The repository was last updated about 2 months ago, so li-human is actively maintained.
Skill content
View source on GitHubname: li-human description: >- Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out. Use whenever text needs to sound human, when the user says humanize, "does this sound like AI", "remove the em dashes", "de-slop this", "will this get flagged", or before any LinkedIn post, comment, reply or DM is shown to the user.
li-human
Two tools live in this folder and they both actually run. Use them. Do not eyeball this.
python3 humanize.py draft.txt --report # clean it, show what changed
python3 detect.py draft.txt # score it, five checks
python3 detect.py before.txt after.txt # prove the delta
Both read slop.json, which is the lexicon: 100+ stock words and phrases with
plain-English replacements, 17 invisible character classes, 11 typographic
substitutions, and 11 structural tells. It is meant to be edited. If the user
has a word they always use that the lexicon strips, remove it from the file.
What gets fixed automatically
1. Invisible characters. Zero-width spaces and joiners, word joiners,
soft hyphens, byte-order marks, Unicode tag characters, non-breaking and
narrow spaces. A keyboard does not produce these. They survive copy-paste,
they are invisible in every editor, and they are the single most mechanical
thing in generated text. humanize.py deletes every one, including any
remaining Unicode format character it does not have a name for.
2. Typography. Em dash to comma, en dash to hyphen, curly quotes to
straight, ellipsis to three dots, bullet character to hyphen. The em dash pass
is the one that matters: it collapses — to , and then cleans up the
double punctuation that leaves behind.
3. The slop lexicon. delve, leverage, robust, seamless, crucial, tapestry, testament to, moreover, "in today's fast-paced world", "let that sink in" and the rest, each swapped for a plain word, with capitalisation preserved and URLs left untouched.
What does NOT get fixed automatically
Structural tells get flagged, not rewritten, because changing the shape of a sentence needs judgement:
- "It's not just X, it's Y" and "not only X but also Y"
- Rule-of-three triads
- Rhetorical one-word question lines: "The result?"
- Rocket, fire, bulb, sparkle and dart emoji
- Hashtag walls
- Reflex engagement bait: "Thoughts?", "Agree?", "Who else?"
- Uniform sentence length and uniform bullet length
That list is your job. Rewrite each flagged line by hand, keeping the meaning,
then re-run detect.py. This is the part that moves the score from REVIEW to
PASS, and it is the part a script cannot do.
The five checks
detect.py scores five signals 0-100, higher is more human:
| check | what it measures | machine looks like | | --- | --- | --- | | BURSTINESS | sentence-length variation | every sentence the same length | | SPECIFICITY | numbers, names, concrete markers per 100 words | abstract nouns, no figures | | SLOP DENSITY | lexicon hits per 100 words | stock vocabulary | | FINGERPRINT | invisible chars, em dashes, curly quotes per 1k chars | typographically perfect | | VOICE | contractions, person, structural tells | no contractions, staged reveals |
The verdict weights the mean at 60% and the weakest single check at 40%, because a detector only needs one signal to fire. PASS needs an overall of 70+ with no check below 55.
Say this honestly
These are five local heuristics modelled on the signals public detectors key on. They run entirely on the user's machine and nothing is uploaded. They are not GPTZero, Originality, Copyleaks, Winston or Turnitin, they do not call those APIs, and they cannot promise those verdicts. Fixing what they measure does tend to move those numbers, because they are measuring the same underlying things. That is the claim. Do not make a bigger one on the user's behalf, and do not tell a user their text is undetectable.
Order of operations
humanize.py draft.txt -o clean.txt --report- Read the structural flags. Rewrite those lines yourself.
detect.py draft.txt clean.txtto show the before and after.- If the verdict is not PASS, fix the weakest check named in the output and go again. Two rounds is normal. Five means the draft was written by formula, and the fix is a different draft, not more passes.
- Show the user the cleaned text and the score. Never the score alone.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.9kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
