li-audit
Post-mortem on what the user has already published - which posts actually worked, why, and…
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",
$ npx -y skills add Jakeschincariol/linkedin-agent-skill --skill li-human --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/li-humanContext preview
The summary Claude sees to decide when to auto-load this skill.
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",
name: 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.
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.
**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.
Structural tells get **flagged, not rewritten**, because changing the shape of a sentence needs judgement:
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.
`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.
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.
1. `humanize.py draft.txt -o clean.txt --report` 2. Read the structural flags. Rewrite those lines yourself. 3. `detect.py draft.txt clean.txt` to show the before and after. 4. 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. 5. Show the user the cleaned text and the score. Never the score alone.
Eleven Claude skills that run a LinkedIn account. Free, MIT, no signup, no API key, nothing to connect. One of them writes your posts off 21 hook formulas. One comments on other people's posts. One handles the replies under yours.
Post-mortem on what the user has already published - which posts actually worked, why, and…
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the…
Write comments on other people's LinkedIn posts that read as a person with an opinion, not a…
Write connection notes and DM follow-ups that get replies - the 200-character invite, the…
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers…
Build the week on LinkedIn - what to post, when to post it, and who to engage with. Use when…