Skip to content
Back to search

ai-slop-detector

120 patterns that make writing read like AI slop, with an agent skill for Claude Code and Codex.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/feedhive--ai-slop-detector/badge.svg)](/listings/feedhive--ai-slop-detector)

HTML

<a href="/listings/feedhive--ai-slop-detector"><img src="/api/listings/feedhive--ai-slop-detector/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 1,163 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # AI Slop Detector
  2. 120 patterns that make writing read like AI slop, in 9 categories. Each pattern has a short explanation, a bad example and a plain rewrite.
  3. Give the list to your AI before it writes, or check a draft against it afterwards. To check a draft in your browser, paste it into the free [AI Slop Detector](https://www.feedhive.com/tools/ai-slop-detector).
  4. The list doesn't try to tell whether a person or an AI wrote a text. People write these patterns too, and a model can be told to avoid them. A single pattern is normal in human writing; several in one paragraph is what makes a text read as slop.
  5. ## Use it with your AI
  6. **Claude Code, Codex and other agents.** Give the agent this repository and ask it to install the skill:
  7. ```text
  8. Install the AI Slop Detector skill from https://github.com/FeedHive/ai-slop-detector
  9. ```
  10. Or install it yourself for Claude Code:
  11. ```sh
  12. git clone https://github.com/FeedHive/ai-slop-detector.git
  13. cp -r ai-slop-detector/skills/ai-slop-detector ~/.claude/skills/
  14. ```
  15. **ChatGPT, Claude and other chat apps.** Paste this README into the chat and ask it to avoid every pattern in what it writes next. To check a draft, paste the README and the draft and ask for every pattern it finds, with the line it found it in.
  16. **Your own tools.** [`patterns.json`](patterns.json) has the full list as structured data. Edit it and run `node scripts/build.mjs` to regenerate this README and the skill.
  17. ## Categories
  18. | Category | Patterns |
  19. |---|---|
  20. | [Vocabulary](#vocabulary) | 20 |
  21. | [Stock phrases](#stock-phrases) | 15 |
  22. | [Sentence patterns](#sentence-patterns) | 22 |
  23. | [Structure and rhythm](#structure-and-rhythm) | 12 |
  24. | [Imagery and metaphor](#imagery-and-metaphor) | 6 |
  25. | [Substance](#substance) | 12 |
  26. | [Formatting and punctuation](#formatting-and-punctuation) | 10 |
  27. | [Chatbot residue](#chatbot-residue) | 8 |
  28. | [Social media and LinkedIn](#social-media-and-linkedin) | 15 |
  29. <a id="vocabulary"></a>
  30. ## Vocabulary
  31. Words that show up far more often in AI output than in human writing. One is a coincidence; three in a paragraph is a pattern.
  32. <a id="v-01-delve-and-friends"></a>
  33. ### V-01 Delve and friends
  34. delve, dive into, deep dive, unpack, explore (for "discuss").
  35. Bad: "Let's delve into the data."
  36. Better: "Here is what the data shows."
  37. <a id="v-02-tapestry-words"></a>
  38. ### V-02 Tapestry words
  39. tapestry, landscape, realm, sphere, ecosystem, fabric (used abstractly).
  40. Bad: "the ever-evolving landscape of marketing."
  41. Better: "marketing in 2026" or name the actual change.
  42. <a id="v-03-testament-and-beacon"></a>
  43. ### V-03 Testament and beacon
  44. testament to, beacon of, embodiment of, hallmark of.
  45. Bad: "The launch is a testament to the team's dedication."
  46. Better: "The team shipped it in six weeks."
  47. <a id="v-04-pivotal-and-crucial"></a>
  48. ### V-04 Pivotal and crucial
  49. pivotal, crucial, vital, paramount, critical (as decoration).
  50. Bad: "plays a pivotal role in growth."
  51. Better: "drives 40% of signups."
  52. <a id="v-05-showcase-verbs"></a>
  53. ### V-05 Showcase verbs
  54. showcase, highlight, underscore, emphasize, spotlight (as commentary verbs).
  55. Bad: "The results underscore the importance of testing."
  56. Better: "Testing caught three bugs before launch."
  57. <a id="v-06-foster-and-cultivate"></a>
  58. ### V-06 Foster and cultivate
  59. foster, cultivate, nurture (applied to abstract things).
  60. Bad: "fostering a culture of innovation."
  61. Better: Say what the team actually does.
  62. <a id="v-07-leverage-and-utilize"></a>
  63. ### V-07 Leverage and utilize
  64. leverage, utilize, harness, capitalize on.
  65. Bad: "Leverage AI to streamline your workflow."
  66. Better: "Use AI to draft the weekly report."
  67. <a id="v-08-elevate-and-enhance"></a>
  68. ### V-08 Elevate and enhance
  69. elevate, enhance, empower, supercharge, unlock, amplify.
  70. Bad: "Elevate your content strategy."
  71. Better: Name the result: "Post three times a week without writing on weekends."
  72. <a id="v-09-seamless-and-robust"></a>
  73. ### V-09 Seamless and robust
  74. seamless, robust, cutting-edge, state-of-the-art, best-in-class, world-class.
  75. Bad: "a seamless, robust solution."
  76. Better: "it syncs in under a second and hasn't gone down this year."
  77. <a id="v-10-intricate-and-multifaceted"></a>
  78. ### V-10 Intricate and multifaceted
  79. intricate, multifaceted, nuanced, complex (as filler).
  80. Bad: "the intricate interplay of factors."
  81. Better: Name two of the factors.
  82. <a id="v-11-meticulous"></a>
  83. ### V-11 Meticulous
  84. meticulous, meticulously, painstakingly, carefully crafted.
  85. Bad: "meticulously crafted templates."
  86. Better: "templates tested on 200 posts."
  87. <a id="v-12-vibrant-and-rich"></a>
  88. ### V-12 Vibrant and rich
  89. vibrant, rich, bustling, thriving, dynamic.
  90. Bad: "a vibrant community of creators."
  91. Better: "4,000 creators who post weekly."
  92. <a id="v-13-journey-and-embark"></a>
  93. ### V-13 Journey and embark
  94. journey, embark, navigate, voyage, path (for ordinary processes).
  95. Bad: "embark on your SEO journey."
  96. Better: "start with your top ten pages."
  97. <a id="v-14-game-changer"></a>
  98. ### V-14 Game changer
  99. game changer, revolutionary, groundbreaking, transformative, paradigm shift.
  100. Bad: "This feature is a game changer."
  101. Better: Say what changes and for whom.
  102. <a id="v-15-transition-adverbs"></a>
  103. ### V-15 Transition adverbs
  104. Additionally, Furthermore, Moreover, Notably, Importantly (opening sentences).
  105. Bad: "Additionally, the tool supports exports."
  106. Better: "It also exports to CSV."
  107. <a id="v-16-empty-intensifiers"></a>
  108. ### V-16 Empty intensifiers
  109. truly, incredibly, deeply, profoundly, remarkably, fundamentally.
  110. Bad: "a truly remarkable result."
  111. Better: Give the number that makes it remarkable.
  112. <a id="v-17-quietly"></a>
  113. ### V-17 Quietly
  114. quietly, silently, subtly (adding drama to plain events).
  115. Bad: "Costs quietly crept up."
  116. Better: "Costs rose 12% in March."
  117. <a id="v-18-align-and-resonate"></a>
  118. ### V-18 Align and resonate
  119. align with, resonate with, speak to, in line with.
  120. Bad: "content that resonates with your audience."
  121. Better: "posts your audience replies to."
  122. <a id="v-19-key-as-an-adjective"></a>
  123. ### V-19 Key as an adjective
  124. key insight, key takeaway, key factor, key role.
  125. Bad: "The key takeaway is consistency."
  126. Better: "Post on the same days every week."
  127. <a id="v-20-era-words"></a>
  128. ### V-20 Era words
  129. in today's fast-paced world, in the digital age, in an era of, now more than ever.
  130. Bad: "In today's fast-paced digital world, content is king."
  131. Better: Cut it and start with the point.
  132. <a id="stock-phrases"></a>
  133. ## Stock phrases
  134. Ready-made phrases that fill space without adding meaning.
  135. <a id="p-01-worth-noting"></a>
  136. ### P-01 Worth noting
  137. it's worth noting, it's important to note, it should be noted.
  138. Bad: "It's worth noting that the API is rate limited."
  139. Better: "The API allows 100 calls a minute."
  140. <a id="p-02-at-its-core"></a>
  141. ### P-02 At its core
  142. at its core, at the end of the day, when all is said and done, ultimately.
  143. Bad: "At its core, marketing is about people."
  144. Better: Delete, or say something specific about people.
  145. <a id="p-03-when-it-comes-to"></a>
  146. ### P-03 When it comes to
  147. when it comes to, in terms of, with regard to, in the world of.
  148. Bad: "When it comes to scheduling, timing matters."
  149. Better: "Posts at 9am get more reach than posts at 3pm."
  150. <a id="p-04-let-s-dive-in"></a>
  151. ### P-04 Let's dive in
  152. let's dive in, let's get started, buckle up, without further ado.
  153. Bad: "Ready? Let's dive in!"
  154. Better: Start with the first point.
  155. <a id="p-05-plays-a-role"></a>
  156. ### P-05 Plays a role
  157. plays a role in, contributes to, is a factor in.
  158. Bad: "Hashtags play a role in reach."
  159. Better: "Posts with 3 to 5 hashtags reached more people in our test."
  160. <a id="p-06-stands-as"></a>
  161. ### P-06 Stands as
  162. stands as, serves as, functions as, acts as (instead of "is").
  163. Bad: "The dashboard serves as a central hub."
  164. Better: "The dashboard shows every scheduled post."
  165. <a id="p-07-navigate-the-complexities"></a>
  166. ### P-07 Navigate the complexities
  167. navigate the complexities of, the ins and outs of, the nuances of.
  168. Bad: "helping you navigate the complexities of SEO."
  169. Better: "explains how Google picks which page to rank."
  170. <a id="p-08-whether-you-re-x-or-y"></a>
  171. ### P-08 Whether you're X or Y
  172. Whether you're a beginner or a pro, from startups to enterprises.
  173. Bad: "Whether you're a solo creator or a global brand, ..."
  174. Better: Say who it is actually for.
  175. <a id="p-09-look-no-further"></a>
  176. ### P-09 Look no further
  177. look no further, you've come to the right place, this is your ultimate guide.
  178. Bad: "Looking for a scheduler? Look no further."
  179. Better: "FeedHive schedules posts to 10 platforms."
  180. <a id="p-10-unlock-the-power"></a>
  181. ### P-10 Unlock the power
  182. unlock the power of, harness the potential of, take it to the next level.
  183. Bad: "Unlock the full potential of your content."
  184. Better: Say the specific gain.
  185. <a id="p-11-here-s-the-thing"></a>
  186. ### P-11 Here's the thing
  187. here's the thing, here's the deal, let me be clear, I'll be honest, I'll be straight with you.
  188. Bad: "Here's the thing: most people quit."
  189. Better: "Most people quit in month two."
  190. <a id="p-12-the-truth-is"></a>
  191. ### P-12 The truth is
  192. the truth is, the reality is, the uncomfortable truth, the hard truth.
  193. Bad: "The hard truth is that SEO takes time."
  194. Better: "SEO takes about six months to show results."
  195. <a id="p-13-sign-off-clich-s"></a>
  196. ### P-13 Sign-off clichés
  197. I hope this helps, happy writing, feel free to reach out, let me know if you have any questions.
  198. Bad: A post or article ending with "Hope this helps!"
  199. Better: End on the last useful point.
  200. <a id="p-14-summary-openers"></a>
  201. ### P-14 Summary openers
  202. In conclusion, In summary, To sum up, Overall, All in all.
  203. Bad: "In conclusion, consistency is key."
  204. Better: End on the last concrete point; the reader was just there.
  205. <a id="p-15-vague-future"></a>
  206. ### P-15 Vague future
  207. the future is bright, the possibilities are endless, only time will tell, the sky's the limit.
  208. Bad: "With AI, the possibilities are endless."
  209. Better: Name one thing that is now possible.
  210. <a id="sentence-patterns"></a>
  211. ## Sentence patterns
  212. Constructions that AI reaches for again and again.
  213. <a id="s-01-not-x-but-y"></a>
  214. ### S-01 Not X, but Y
  215. "It's not X. It's Y." / "This isn't about X, it's about Y."
  216. Bad: "It's not a tool. It's a teammate."
  217. Better: Say what it does: "It drafts replies for you to approve."
  218. <a id="s-02-not-just-x-but-also-y"></a>
  219. ### S-02 Not just X, but also Y
  220. "It's not just fast, it's also accurate."
  221. Bad: "Not just a scheduler, but a full content engine."
  222. Better: List what it does.
  223. <a id="s-03-the-question-isn-t-x"></a>
  224. ### S-03 The question isn't X
  225. "The question isn't whether, it's when." / "The problem isn't X. The problem is Y."
  226. Bad: "The question isn't if you should use AI. It's how."
  227. Better: "Here is how we use AI for first drafts."
  228. <a id="s-04-negative-listing"></a>
  229. ### S-04 Negative listing
  230. "Not a X. Not a Y. A Z."
  231. Bad: "Not a plan. Not a hope. A system."
  232. Better: "A system: three posts a week, written on Mondays."
  233. <a id="s-05-rhetorical-q-and-a"></a>
  234. ### S-05 Rhetorical Q and A
  235. A question the writer immediately answers.
  236. Bad: "Why does this matter? Because reach is everything."
  237. Better: "Reach decides how many people see the post."
  238. <a id="s-06-the-obvious-question"></a>
  239. ### S-06 The obvious question
  240. "The obvious question is...", "You might be wondering..."
  241. Bad: "You might be wondering how this works."
  242. Better: Explain how it works.
  243. <a id="s-07-colon-reveal"></a>
  244. ### S-07 Colon reveal
  245. A short setup, a colon, then a dramatic reveal.
  246. Bad: "The best part: it's free."
  247. Better: "It's free."
  248. <a id="s-08-faux-insight"></a>
  249. ### S-08 Faux insight
  250. "What nobody tells you", "the part most people miss", "here's what most get wrong".
  251. Bad: "What nobody tells you about growth: distribution beats product."
  252. Better: "Distribution brought us more users than any feature."
  253. <a id="s-09-this-is-where-it-gets-interesting"></a>
  254. ### S-09 This is where it gets interesting
  255. this is where it gets interesting, this changes everything, and that's where things get wild.
  256. Bad: "And this is where it gets interesting."
  257. Better: State the interesting thing.
  258. <a id="s-10-the-useful-part-is"></a>
  259. ### S-10 The useful part is
  260. the useful part, the part where, the best part, the exciting part, the part that stuck with me.
  261. Bad: "The useful part is that it connects to your inbox."
  262. Better: "It connects to your inbox."
  263. <a id="s-11-x-is-just-y"></a>
  264. ### S-11 X is just Y
  265. Calling something "just" a vivid unrelated thing to make a point.
  266. Bad: "Posting without a plan is just gambling with your time."
  267. Better: "Without a plan you post less and repeat topics."
  268. <a id="s-12-trailing-ing-analysis"></a>
  269. ### S-12 Trailing -ing analysis
  270. A sentence ends with an -ing clause that tells you what it means.
  271. Bad: "Sales rose 20%, highlighting the strength of the brand."
  272. Better: "Sales rose 20%."
  273. <a id="s-13-rule-of-three"></a>
  274. ### S-13 Rule of three
  275. Lists of exactly three adjectives or phrases, by reflex.
  276. Bad: "fast, simple, and powerful."
  277. Better: Keep the one that is true and provable.
  278. <a id="s-14-synonym-cycling"></a>
  279. ### S-14 Synonym cycling
  280. Rotating names for the same thing to avoid repetition.
  281. Bad: "The agent drafts. The assistant reviews. The tool publishes."
  282. Better: "The agent drafts, reviews and publishes."
  283. <a id="s-15-arbitrary-one"></a>
  284. ### S-15 Arbitrary "one"
  285. Putting "one" before a noun to sound focused when the number means nothing.
  286. Bad: "Start with one workflow."
  287. Better: "Start with your weekly newsletter."
  288. <a id="s-16-fake-strong-verbs"></a>
  289. ### S-16 Fake-strong verbs
  290. boasts, features, offers, maintains (instead of "has").
  291. Bad: "The app boasts an intuitive interface."
  292. Better: "The app has a drag-and-drop calendar."
  293. <a id="s-17-imagine-a-world"></a>
  294. ### S-17 Imagine a world
  295. imagine a world where, picture this, what if I told you.
  296. Bad: "Imagine a world where your posts write themselves."
  297. Better: Describe what the product does today.
  298. <a id="s-18-hedge-stacking"></a>
  299. ### S-18 Hedge stacking
  300. may potentially, could possibly, might help to, can sometimes.
  301. Bad: "This may potentially help improve results."
  302. Better: "This improved reply rate by 8% in our test." Or cut it.
  303. <a id="s-19-both-sides-filler"></a>
  304. ### S-19 Both-sides filler
  305. "While X has benefits, it also has drawbacks."
  306. Bad: "While automation saves time, it's important to stay authentic."
  307. Better: Take a position and support it.
  308. <a id="s-20-from-x-to-y-range"></a>
  309. ### S-20 From X to Y range
  310. "From startups to enterprises", "from strategy to execution".
  311. Bad: "From ideation to publication, we've got you covered."
  312. Better: Name the two steps you actually handle.
  313. <a id="s-21-interpretive-asides"></a>
  314. ### S-21 Interpretive asides
  315. Telling the reader how to read the text.
  316. Bad: "That last point matters more than it sounds."
  317. Better: Show why it matters, or delete the aside.
  318. <a id="s-22-rhetorical-self-correction"></a>
  319. ### S-22 Rhetorical self-correction
  320. "Actually, let me rephrase that", "Or rather..."
  321. Bad: "It's fast. Or rather, it's instant."
  322. Better: "It's instant."
  323. <a id="structure-and-rhythm"></a>
  324. ## Structure and rhythm
  325. Slop is often in the shape of the text, not the words.
  326. <a id="r-01-one-line-paragraph-stacks"></a>
  327. ### R-01 One-line paragraph stacks
  328. Many short lines in a row, each a slogan.
  329. Bad: "I quit my job. / I built a product. / Nobody came. / Then I learned this."
  330. Better: Write it as one paragraph.
  331. <a id="r-02-fragment-drumbeat"></a>
  332. ### R-02 Fragment drumbeat
  333. Strings of fragments for rhythm.
  334. Bad: "Code. Content. Customers. Every day."
  335. Better: One full sentence that says what you do every day.
  336. <a id="r-03-repeated-starters"></a>
  337. ### R-03 Repeated starters
  338. Several lines that start with the same word or phrase.
  339. Bad: "It saves time. It saves money. It saves your sanity."
  340. Better: "It saves about four hours a week."
  341. <a id="r-04-identical-sentence-shapes"></a>
  342. ### R-04 Identical sentence shapes
  343. Every sentence the same length and structure.
  344. Bad: A paragraph of 12-word sentences, each "Subject verb object, comma, clause."
  345. Better: Vary length when it helps the point.
  346. <a id="r-05-list-dumps"></a>
  347. ### R-05 List dumps
  348. Long inventories of nouns in one breath.
  349. Bad: "sales, marketing, support, ops, finance, hiring, legal and product."
  350. Better: Pick the two that matter here.
  351. <a id="r-06-bullets-for-everything"></a>
  352. ### R-06 Bullets for everything
  353. Bullet points where two sentences of prose would read better.
  354. Bad: Three bullets of four words each.
  355. Better: One sentence.
  356. <a id="r-07-headings-on-tiny-sections"></a>
  357. ### R-07 Headings on tiny sections
  358. Headers over one or two sentences.
  359. Bad: "## Why it matters" followed by one line.
  360. Better: Fold it into the paragraph above.
  361. <a id="r-08-recap-ending"></a>
  362. ### R-08 Recap ending
  363. A final paragraph that repeats the whole piece.
  364. Bad: "To recap, we covered A, B and C."
  365. Better: End on the last point or the next action.
  366. <a id="r-09-mic-drop-ending"></a>
  367. ### R-09 Mic-drop ending
  368. A final "deep" one-liner.
  369. Bad: "The future isn't coming. It's already here."
  370. Better: End on the clearest concrete sentence.
  371. <a id="r-10-challenges-and-future-outlook"></a>
  372. ### R-10 Challenges and future outlook
  373. A formulaic "Despite challenges, the future looks promising" closer.
  374. Bad: "Despite these challenges, the outlook remains positive."
  375. Better: Name the challenge and what is being done.
  376. <a id="r-11-fake-unscripted-scaffolding"></a>
  377. ### R-11 Fake-unscripted scaffolding
  378. "And honestly...", "And look...", "So yeah..." used as filler.
  379. Bad: "And honestly? That's when it clicked."
  380. Better: Say what clicked.
  381. <a id="r-12-over-structured-short-answers"></a>
  382. ### R-12 Over-structured short answers
  383. A short reply split into sections with headers and bold labels.
  384. Bad: A three-sentence answer with "Overview", "Key Points" and "Conclusion".
  385. Better: Three sentences.
  386. <a id="imagery-and-metaphor"></a>
  387. ## Imagery and metaphor
  388. AI likes making things vivid when they should be clear.
  389. <a id="m-01-cute-metaphors"></a>
  390. ### M-01 Cute metaphors
  391. Abstract things doing human or physical actions.
  392. Bad: "Your data is whispering insights."
  393. Better: "Your data shows Tuesday posts get more replies."
  394. <a id="m-02-things-that-live-or-sit"></a>
  395. ### M-02 Things that "live" or "sit"
  396. Data, products or agents that live or sit somewhere.
  397. Bad: "where your customer data lives."
  398. Better: "where your customer data is stored."
  399. <a id="m-03-honest-dashboards"></a>
  400. ### M-03 Honest dashboards
  401. Systems that "get honest", "tell the truth", "hide" or "reveal".
  402. Bad: "Analytics finally get honest."
  403. Better: "Analytics now count only real views."
  404. <a id="m-04-mixed-and-stacked-metaphors"></a>
  405. ### M-04 Mixed and stacked metaphors
  406. Two or three images in one sentence.
  407. Bad: "a north star that fuels the engine of growth."
  408. Better: Drop both images and say what drives growth.
  409. <a id="m-05-fuel-and-engine"></a>
  410. ### M-05 Fuel and engine
  411. fuel, engine, rocket, catalyst, springboard, flywheel (as decoration).
  412. Bad: "content that fuels your growth engine."
  413. Better: "posts that bring in signups."
  414. <a id="m-06-secret-sauce"></a>
  415. ### M-06 Secret sauce
  416. secret sauce, magic, silver bullet, holy grail.
  417. Bad: "Consistency is the secret sauce."
  418. Better: "Accounts that posted weekly grew twice as fast."
  419. <a id="substance"></a>
  420. ## Substance
  421. The deepest kind of slop: text that sounds informative and says nothing.
  422. <a id="c-01-importance-puffery"></a>
  423. ### C-01 Importance puffery
  424. Inflating significance: "marks a pivotal moment", "a significant shift".
  425. Bad: "This marks a pivotal moment for the industry."
  426. Better: State the fact and let the reader judge.
  427. <a id="c-02-vague-attribution"></a>
  428. ### C-02 Vague attribution
  429. experts agree, studies show, many believe, it is widely regarded.
  430. Bad: "Studies show posting daily works."
  431. Better: Name the study, or cut the claim.
  432. <a id="c-03-generic-claims-without-receipts"></a>
  433. ### C-03 Generic claims without receipts
  434. Claims any company could make.
  435. Bad: "AI can transform your business."
  436. Better: "Our AI drafts a week of posts from a 3-line brief."
  437. <a id="c-04-the-portability-test"></a>
  438. ### C-04 The portability test
  439. A sentence that could move unchanged to another company or topic.
  440. Bad: "We're committed to delivering value to our customers."
  441. Better: A sentence only you could write.
  442. <a id="c-05-fake-profound-wisdom"></a>
  443. ### C-05 Fake-profound wisdom
  444. Lines that sound deep and mean nothing concrete.
  445. Bad: "Growth is a mindset, not a metric."
  446. Better: Say what you measure and why.
  447. <a id="c-06-smoothing-the-specific"></a>
  448. ### C-06 Smoothing the specific
  449. Replacing a sharp fact with a generic description.
  450. Bad: "a leading expert in the field."
  451. Better: "who wrote the Kubernetes scheduler."
  452. <a id="c-07-made-up-specifics"></a>
  453. ### C-07 Made-up specifics
  454. Invented numbers, names or examples presented as real.
  455. Bad: "Sarah, a marketing manager, saved 10 hours a week." (no Sarah exists)
  456. Better: A real example, or none.
  457. <a id="c-08-telling-instead-of-showing"></a>
  458. ### C-08 Telling instead of showing
  459. Labeling something surprising, important or interesting.
  460. Bad: "Surprisingly, the simple version won."
  461. Better: "The simple version got twice the clicks."
  462. <a id="c-09-canned-notability"></a>
  463. ### C-09 Canned notability
  464. "featured in top outlets", "widely recognized", "has an active social media presence".
  465. Bad: "She has been featured in numerous leading publications."
  466. Better: Name one, with a link.
  467. <a id="c-10-superficial-balance"></a>
  468. ### C-10 Superficial balance
  469. Every point gets a "however" so the text never commits.
  470. Bad: "AI is powerful. However, it has limitations."
  471. Better: Say which limitation matters for this reader.
  472. <a id="c-11-advice-with-no-steps"></a>
  473. ### C-11 Advice with no steps
  474. Telling the reader to "optimize", "be strategic" or "stay consistent" without saying how.
  475. Bad: "Optimize your posting schedule."
  476. Better: "Post Tuesday to Thursday between 8 and 10am."
  477. <a id="c-12-hollow-promises"></a>
  478. ### C-12 Hollow promises
  479. "Everything you need to know", "the ultimate guide", "master X in minutes".
  480. Bad: "The ultimate guide to LinkedIn."
  481. Better: "How to write a LinkedIn post that gets replies."
  482. <a id="formatting-and-punctuation"></a>
  483. ## Formatting and punctuation
  484. <a id="f-01-em-dash-habit"></a>
  485. ### F-01 Em dash habit
  486. Em dashes used everywhere for rhythm.
  487. Bad: "It's fast — really fast — and free."
  488. Better: "It's fast and free." Use commas, periods or parentheses.
  489. <a id="f-02-bold-sprinkled-mid-sentence"></a>
  490. ### F-02 Bold sprinkled mid-sentence
  491. Random words in bold for emphasis.
  492. Bad: "This is **really important** for **growth**."
  493. Better: No bold; let the sentence carry it.
  494. <a id="f-03-emoji-as-bullets"></a>
  495. ### F-03 Emoji as bullets
  496. ✅ 🚀 💡 👉 used as list markers or decoration.
  497. Bad: "✅ Faster ✅ Cheaper ✅ Better"
  498. Better: A plain sentence.
  499. <a id="f-04-title-case-headings"></a>
  500. ### F-04 Title Case Headings
  501. Every Word Capitalized In Headings.
  502. Bad: "How To Grow Your Audience On LinkedIn"
  503. Better: "How to grow your audience on LinkedIn"
  504. <a id="f-05-colon-label-lines"></a>
  505. ### F-05 Colon-label lines
  506. Every line starts with a bold label and a colon.
  507. Bad: "**Speed:** fast. **Price:** low. **Support:** great."
  508. Better: A sentence about the one that matters.
  509. <a id="f-06-markdown-in-the-wrong-place"></a>
  510. ### F-06 Markdown in the wrong place
  511. Asterisks, hashtags or headers pasted into emails, posts or forms.
  512. Bad: "**Subject:** ..." inside a LinkedIn post.
  513. Better: Plain text.
  514. <a id="f-07-curly-quote-and-character-mix"></a>
  515. ### F-07 Curly-quote and character mix
  516. Curly quotes, special dashes and non-breaking spaces mixed with plain text.
  517. Bad: “quotes” next to "quotes" in one paragraph.
  518. Better: Pick one style.
  519. <a id="f-08-exclamation-inflation"></a>
  520. ### F-08 Exclamation inflation
  521. Exclamation marks on ordinary sentences.
  522. Bad: "We updated the settings page!"
  523. Better: "We updated the settings page."
  524. <a id="f-09-unicode-bold-and-fancy-fonts-in-long-posts"></a>
  525. ### F-09 Unicode bold and fancy fonts in long posts
  526. 𝗕𝗼𝗹𝗱 or 𝓈𝒸𝓇𝒾𝓅𝓉 letters across whole lines.
  527. Bad: An entire LinkedIn post in Unicode bold.
  528. Better: Plain text, one bold phrase at most (screen readers can't read these).
  529. <a id="f-10-tables-for-two-facts"></a>
  530. ### F-10 Tables for two facts
  531. A table where a sentence would do.
  532. Bad: A 2x2 table comparing price and speed.
  533. Better: "A is cheaper; B is faster."
  534. <a id="chatbot-residue"></a>
  535. ## Chatbot residue
  536. Text that was clearly copied out of a chat window.
  537. <a id="b-01-assistant-openers"></a>
  538. ### B-01 Assistant openers
  539. Certainly!, Absolutely!, Great question!, Of course!
  540. Bad: "Certainly! Here's a LinkedIn post about..."
  541. Better: Delete it.
  542. <a id="b-02-sycophancy"></a>
  543. ### B-02 Sycophancy
  544. You're absolutely right, what a great idea, I love this.
  545. Bad: An email reply starting "Great point, you're absolutely right!"
  546. Better: Answer the point.
  547. <a id="b-03-offer-to-do-more"></a>
  548. ### B-03 Offer to do more
  549. Would you like me to..., Let me know if you'd like a shorter version.
  550. Bad: A published post ending "Would you like me to adjust the tone?"
  551. Better: Delete it.
  552. <a id="b-04-here-is-a"></a>
  553. ### B-04 Here is a...
  554. Lead-ins like "Here is a polished version of your post:" left in the final text.
  555. Better: Delete the line.
  556. <a id="b-05-placeholder-text"></a>
  557. ### B-05 Placeholder text
  558. [Your Name], [Company], [insert statistic], XX%.
  559. Better: Fill it in or cut the sentence.
  560. <a id="b-06-ai-disclaimers"></a>
  561. ### B-06 AI disclaimers
  562. As an AI, I don't have personal opinions; my knowledge is limited to...
  563. Better: Delete it.
  564. <a id="b-07-source-hedging"></a>
  565. ### B-07 Source hedging
  566. "Based on available information", "specific details are limited".
  567. Bad: "While specific figures are not widely available, ..."
  568. Better: Find the figure or don't mention it.
  569. <a id="b-08-citation-debris"></a>
  570. ### B-08 Citation debris
  571. Leftover markers like [1], contentReference, oaicite, turn0search0.
  572. Better: Remove them, and check the claim they were attached to.
  573. <a id="social-media-and-linkedin"></a>
  574. ## Social media and LinkedIn
  575. Patterns that turn a post into "LinkedIn slop".
  576. <a id="l-01-broetry"></a>
  577. ### L-01 Broetry
  578. One sentence per line, top to bottom.
  579. Bad: A 20-line post where every line is a new sentence.
  580. Better: Short paragraphs.
  581. <a id="l-02-hook-formulas"></a>
  582. ### L-02 Hook formulas
  583. "I was fired. Best thing that ever happened.", "Unpopular opinion:", "Stop doing X."
  584. Better: Open with the specific thing that happened or the specific claim.
  585. <a id="l-03-thrilled-to-announce"></a>
  586. ### L-03 Thrilled to announce
  587. I'm thrilled/excited/humbled to announce, I'm proud to share.
  588. Bad: "I'm thrilled to announce I've joined Acme!"
  589. Better: "I joined Acme to lead the growth team."
  590. <a id="l-04-read-that-again"></a>
  591. ### L-04 Read that again
  592. Read that again., Let that sink in., I'll say it louder.
  593. Better: Delete it. If the line needs a second read, rewrite it.
  594. <a id="l-05-agree-thoughts"></a>
  595. ### L-05 Agree? / Thoughts?
  596. Engagement-bait closers.
  597. Bad: "Agree? 👇"
  598. Better: Ask a real question, or don't.
  599. <a id="l-06-the-lesson-list"></a>
  600. ### L-06 The lesson list
  601. "Here are 7 lessons I learned from..." with generic lessons.
  602. Better: One lesson with the story behind it.
  603. <a id="l-07-humblebrag-setup"></a>
  604. ### L-07 Humblebrag setup
  605. "I don't usually post this, but...", "This might be controversial, but..."
  606. Better: Post it without the preamble.
  607. <a id="l-08-thread-markers"></a>
  608. ### L-08 Thread markers
  609. 🧵, 1/, "A thread" on content that isn't a thread.
  610. Better: Write the post.
  611. <a id="l-09-hashtag-walls"></a>
  612. ### L-09 Hashtag walls
  613. Ten or more hashtags at the end.
  614. Better: Three relevant ones, or none.
  615. <a id="l-10-that-s-it-that-s-the-post"></a>
  616. ### L-10 That's it. That's the post
  617. Self-aware closers that announce the ending.
  618. Bad: "That's it. That's the tweet."
  619. Better: Just stop.
  620. <a id="l-11-p-s-engagement"></a>
  621. ### L-11 P.S. engagement
  622. "P.S. Repost ♻️ if this helped." on every post.
  623. Better: Drop it, or use it rarely.
  624. <a id="l-12-no-fluff-just-value"></a>
  625. ### L-12 No fluff, just value
  626. Announcing quality instead of delivering it: no fluff, just value; straight to the point; real talk.
  627. Better: Delete the announcement.
  628. <a id="l-13-comment-slop"></a>
  629. ### L-13 Comment slop
  630. Generic replies: "Great insights!", "So true!", "Thanks for sharing, this is gold."
  631. Better: Reply to something specific in the post, or don't reply.
  632. <a id="l-14-fake-vulnerability-arc"></a>
  633. ### L-14 Fake vulnerability arc
  634. "I failed. I was broke. Then I discovered X." built to sell.
  635. Better: Tell what happened, with dates and numbers.
  636. <a id="l-15-contrarian-template"></a>
  637. ### L-15 Contrarian template
  638. "Everyone says X. They're wrong."
  639. Better: Make your claim and back it up; skip the strawman.
  640. ## License
  641. MIT. Use it, change it and ship it in your own tools.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.