Skip to content
Skills Library
Marketing & content · Learning & explanation

linkedin-rules-explainer

/linkedin-rules-explainer

Explain why each AI-tell rule exists and whether to trust it. Tier-classified rule reference for the linkedin-humanizer package. Separates forensic signals (real AI leakage), strict bans (corporate-speak the user wants out), and aesthetic overreach (stylistic patterns wrongly tagged as AI). Each rule comes with a famous human writer who uses it, a defense strength, and a citation. Use to defend a stylistic choice, audit detector output, or argue against blanket rules. Keywords: rule explainer, AI detector defense, em dash defense, rule of three, passive voice, false positive, OriginalityAI, GP

Licence
MIT
Last repository change
18.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Explain why each AI-tell rule exists and whether to trust it. Tier-classified rule reference for the linkedin-humanizer package. Separates forensic signals (real AI leakage), strict bans (corporate-speak the user wants out), and aesthetic overreach (stylistic patterns wrongly tagged as AI). Each rule comes with a famous human writer who uses it, a defense strength, and a citation. Use to defend a stylistic choice, audit detector output, or argue against blanket rules. Keywords: rule explainer, AI detector defense, em dash defense, rule of three, passive voice, false positive, OriginalityAI, GP

Original author description

Explain why each AI-tell rule exists and whether to trust it. Tier-classified rule reference for the linkedin-humanizer package. Separates forensic signals (real AI leakage), strict bans (corporate-speak the user wants out), and aesthetic overreach (stylistic patterns wrongly tagged as AI). Each rule comes with a famous human writer who uses it, a defense strength, and a citation. Use to defend a stylistic choice, audit detector output, or argue against blanket rules. Keywords: rule explainer, AI detector defense, em dash defense, rule of three, passive voice, false positive, OriginalityAI, GP

How it works

  1. When to use
  2. Input
  3. Output
  4. The three tiers
  5. Non-negotiable rules
  6. Example
  7. Files
  8. Related skills
Original SKILL.md headings · 87 lines, 812 words
SKILL.md preview
---
name: linkedin-rules-explainer
description: Explain why each AI-tell rule exists and whether to trust it. Tier-classified rule reference for the linkedin-humanizer package. Separates forensic signals (real AI leakage), strict bans (corporate-speak the user wants out), and aesthetic overreach (stylistic patterns wrongly tagged as AI). Each rule comes with a famous human writer who uses it, a defense strength, and a citation. Use to defend a stylistic choice, audit detector output, or argue against blanket rules. Keywords: rule explainer, AI detector defense, em dash defense, rule of three, passive voice, false positive, OriginalityAI, GPTZero, stylometry.
---

# LinkedIn Rules Explainer

The educational backbone for the humanizer package. Every rule in `linkedin-humanizer` came from somewhere — Wikipedia's "Signs of AI writing" taxonomy, OriginalityAI's heuristics, GPTZero's stylometry, or 2026 LinkedIn-specific patterns. Some are real forensics (a `[oaicite:0]` marker is undefendable). Some are corporate-speak bans the user wants out for taste reasons. Some are aesthetic overreach — patterns Lincoln, Dickinson, and Didion built careers on, now flagged because GPT-4 happens to use them too.

This skill answers a simple question: **for any given rule, is the AI-tell verdict forensic, strict, or aesthetic — and how strong is the defense?**

## When to use

- Defending a stylistic choice that a detector flagged ("but Emily Dickinson uses em dashes")
- Arguing the controversial post about AI-rule overreach
- Auditing humanizer output before applying a rewrite
- Teaching a team which rules are real signals vs which are taste calls
- Reviewing a false positive from OriginalityAI / GPTZero / Pangram

## Input

Either:
- A specific rule name ("em dashes", "rule of three", "robust")
- A flagged passage from a detector
- A request to walk the full taxonomy

## Output

For each rule:
- **The rule** (what gets flagged)
- **Tier** (forensic / strict / aesthetic)
- **One-line summary** (why it's flagged)
- **Famous human writer** who uses this pattern (with example)
- **Defense strength** (low / medium / high)
- **Citation** (when available)

## The three tiers

### Forensic — real AI signals, undefendable

These are leakage from the model itself or the prompt template. No human writer ever produces them by accident. If the humanizer flags one, accept the rewrite.

Examples: `oaicite` markers, `contentReference` tokens, `turn0search0` artifacts, knowledge-cutoff disclaimers ("As of my last update January 2022..."), Mad-Libs blanks, phrasal templates with literal `[Your Name]` placeholders.

**Defense strength: zero.** Citation: Wikipedia "Signs of AI writing".

### Strict — corporate-speak, easy to ban for taste

These are real human patterns, but they're patterns the user explicitly wants out. The rule isn't "this proves AI wrote it" — it's "I find this voice cheap and want it gone." Defending these is possible but pointless inside a brand voice that has already rejected them.

Examples: leverage / utilize / harness / delve / foster / cultivate, filler adverbs (fundamentally, essentially, ultimately), filler openers ("In today's fast-paced world"), cliché closers ("What do you think?"), negative parallelism ("X isn't Y, it's Z").

**Defense strength: medium** (someone could defend "leverage" as 1980s management vocabulary). **Brand-voice strength: zero** — the user banned them.

### Aesthetic — overreach, defendable

These are patterns flagged because LLMs happen to use them, not because they signal AI. Famous human writers built careers on them. Detectors over-fire on these and produce false positives — see Stanford HAI / Liang et al. (2023) showing detectors are biased against non-native English writers, and the Adelphi University lawsuit over an AI false-positive accusation.

Examples: a single em dash (Emily Dickinson, Cormac McCarthy), the rule of three (Lincoln, Caesar, Churchill), passive voice (Watson & Crick, Joan Didion, all scientific writing), the word "robust" (a century of epidemiology and engineering papers), curly quotes (automatic in Word/Pages, New Yorker house style since 1925).

**Defense strength: high.** These are the rules Author's controversial post is built on.

## Non-negotiable rules

- Don't conflate tiers. A `[oaicite]` marker and a single em dash are not the same kind of evidence.
- When defending, name the writer and give the example. "Lincoln" is weaker than "Lincoln, Gettysburg Address, 1863: 'of the people, by the people, for the people'."
- Cite when available. Stanford HAI and the OpenAI classifier shutdown are the strongest external receipts.
- Don't defend a rule the user has personally banned (em dashes in his own voice, even though Dickinson used them). Brand voice overrides aesthetic defense.

## Example

> **Input:** "OriginalityAI flagged my post for using 'robust' — should I rewrite?"
>
> **Output:**
> Tier: aesthetic. The word "robust" has been used by epidemiologists, engineers, and statisticians for over a century — it has a precise meaning ("insensitive to assumption violations") that no synonym carries. OriginalityAI flags it because GPT-4 over-uses it, not because it signals AI. Defense strength: high.
>
> Recommendation: keep "robust" if you're describing a statistical model, a system architecture, or an immune response. Rewrite to "solid" only if you're using it as generic praise — that's the corporate-speak overuse the humanizer is actually targeting.
>
> Citation: Wikipedia "Signs of AI writing" lists "robust" under AI vocabulary; Stanford HAI shows detectors over-fire on technical English.

## Files

- `SKILL.md` — this file
- `references/rules.md` — full table of all 15 rules organized by tier, with famous-writer examples and citations

## Related skills

- `linkedin-humanizer` — applies the rules (this skill explains them)
- `linkedin-post-audit` — flags rules in a draft
- `linkedin-detector-tester` — runs OriginalityAI / GPTZero / Pangram against drafts
Files in this package (2)
  • SKILL.md 6 KB
  • references/rules.md 14 KB

Versions

The database has no other skills named linkedin-rules-explainer.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 3695f629af6c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90humanizer-linkedin
    Turn a source (a news story, a link, notes, a transcript, or a draft) into a LinkedIn post in the user's saved Humanizer voice. Use for /humanizer-linkedin, \"turn this into a LinkedIn post\", \"write a LinkedIn post about this\", or \"humanize this for LinkedIn\".
  • 100linkedin-humanizer
    Audits and rewrites LinkedIn drafts to remove machine-sounding patterns: tiered tell catalogue, emoji-pattern scoring, rule explanations, and a voice fingerprint built from the author's own posts. Use when a draft reads generated, before publishing, or when an edit flattened someone's voice.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.