de-slopify

Name: de-slopify
Author: Dicklesworthstone

69stars13forks

How to install de-slopify?

dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/de-slopify

$npx -y skills add Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations --skill de-slopify

Installs into the current project.

Summary

Remove telltale signs of AI-generated 'slop' writing from README files and documentation. Make your docs sound authentically human.

Files · 1

View on GitHub

SKILL.md

1	# De-Slopify — Remove AI Writing Artifacts
2
3	> Purpose: Make your documentation sound like it was written by a human, not an LLM.
4	>
5	> Key Insight: You can't do this with regex or a script—it requires manual, systematic review of each line.
6
7	---
8
9	## What is "AI Slop"?
10
11	AI slop refers to writing patterns that LLMs produce disproportionately more commonly than human writers. These patterns make text sound inauthentic and "cringe."
12
13	### Common Tells
14
15	\| Pattern \| Problem \|
16	\|---------\|---------\|
17	\| Emdash overuse \| LLMs love emdashes—they use them constantly—even when other punctuation works better \|
18	\| "It's not X, it's Y" \| Formulaic contrast structure \|
19	\| "Here's why" \| Clickbait-style lead-in \|
20	\| "Here's why it matters:" \| Same energy \|
21	\| "Let's dive in" \| Forced enthusiasm \|
22	\| "In this guide, we'll..." \| Overly formal setup \|
23	\| "It's worth noting that..." \| Unnecessary hedge \|
24	\| "At its core..." \| Pseudo-profound opener \|
25
26	---
27
28	## THE EXACT PROMPT — De-Slopify Documentation
29
30	```
31	I want you to read through the complete text carefully and look for any telltale signs of "AI slop" style writing; one big tell is the use of emdash. You should try to replace this with a semicolon, a comma, or just recast the sentence accordingly so it sounds good while avoiding emdash.
32
33	Also, you want to avoid certain telltale writing tropes, like sentences of the form "It's not [just] XYZ, it's ABC" or "Here's why" or "Here's why it matters:". Basically, anything that sounds like the kind of thing an LLM would write disproportionately more commonly that a human writer and which sounds inauthentic/cringe.
34
35	And you can't do this sort of thing using regex or a script, you MUST manually read each line of the text and revise it manually in a systematic, methodical, diligent way. Use ultrathink.
36	```
37
38	---
39
40	## Why Manual Review is Required
41
42	The prompt explicitly states:
43
44	> "And you can't do this sort of thing using regex or a script, you MUST manually read each line of the text and revise it manually in a systematic, methodical, diligent way."
45
46	Reasons:
47	1. Context matters — Sometimes an emdash is actually the right choice
48	2. Recasting sentences — Often the fix isn't substitution but rewriting
49	3. Tone consistency — Need to maintain voice throughout
50	4. Judgment calls — Some patterns are fine in moderation
51
52	---
53
54	## Emdash Alternatives
55
56	When you encounter an emdash (—), consider:
57
58	\| Original \| Alternative \|
59	\|----------\|-------------\|
60	\| `X—Y—Z` \| `X; Y; Z` or `X, Y, Z` \|
61	\| `The tool—which is powerful—works well` \| `The tool, which is powerful, works well` \|
62	\| `We built this—and it works` \| `We built this, and it works` \|
63	\| `Here's the thing—it matters` \| `Here's the thing: it matters` or recast entirely \|
64
65	Sometimes the best fix is to split into two sentences or restructure entirely.
66
67	---
68
69	## Phrases to Eliminate or Rewrite
70
71	### "Here's why" family
72	- "Here's why" → Just explain why directly
73	- "Here's why it matters" → Explain the importance inline
74	- "Here's the thing" → Usually can be deleted entirely
75
76	### Contrast formulas
77	- "It's not X, it's Y" → "This is Y" or explain the distinction differently
78	- "It's not just X, it's also Y" → "This does X and Y" or similar
79
80	### Forced enthusiasm
81	- "Let's dive in!" → Just start
82	- "Let's get started!" → Just start
83	- "Excited to share..." → Just share it
84
85	### Pseudo-profound openers
86	- "At its core..." → Usually can be deleted
87	- "Fundamentally..." → Often unnecessary
88	- "In essence..." → Just say the essence
89
90	### Unnecessary hedges
91	- "It's worth noting that..." → Just note it
92	- "It's important to remember..." → Just state the fact
93	- "Keep in mind that..." → Often deletable
94
95	---
96
97	## Before and After Examples
98
99	### Example 1: Emdash Overuse
100
101	Before (sloppy):
102	```
103	This tool—which we built from scratch—handles everything automatically—from parsing to output.
104	```
105
106	After (clean):
107	```
108	This tool handles everything automatically, from parsing to output. We built it from scratch.
109	```
110
111	### Example 2: "Here's why" Pattern
112
113	Before (sloppy):
114	```
115	We chose Rust for this component. Here's why: performance matters, and Rust delivers.
116	```
117
118	After (clean):
119	```
120	We chose Rust for this component because performance matters.
121	```
122
123	### Example 3: Contrast Formula
124
125	Before (sloppy):
126	```
127	It's not just a linter—it's a complete code quality system.
128	```
129
130	After (clean):
131	```
132	This is a complete code quality system, not just a linter.
133	```
134
135	Or even better:
136	```
137	This complete code quality system goes beyond basic linting.
138	```
139
140	### Example 4: Forced Enthusiasm
141
142	Before (sloppy):
143	```
144	# Getting Started
145
146	Let's dive in! We're excited to help you get up and running with our amazing tool.
147	```
148
149	After (clean):
150	```
151	# Getting Started
152
153	Install the tool and run your first command in under a minute.
154	```
155
156	---

People who liked this also viewed

6 picks

Type

de-slopify

69stars13forks

View on GitHub

How to install de-slopify?

dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/de-slopify

$npx -y skills add Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations --skill de-slopify

Installs into the current project.

Summary

Remove telltale signs of AI-generated 'slop' writing from README files and documentation. Make your docs sound authentically human.

Files · 1

View on GitHub

SKILL.md

1	# De-Slopify — Remove AI Writing Artifacts
2
3	> Purpose: Make your documentation sound like it was written by a human, not an LLM.
4	>
5	> Key Insight: You can't do this with regex or a script—it requires manual, systematic review of each line.
6
7	---
8
9	## What is "AI Slop"?
10
11	AI slop refers to writing patterns that LLMs produce disproportionately more commonly than human writers. These patterns make text sound inauthentic and "cringe."
12
13	### Common Tells
14
15	\| Pattern \| Problem \|
16	\|---------\|---------\|
17	\| Emdash overuse \| LLMs love emdashes—they use them constantly—even when other punctuation works better \|
18	\| "It's not X, it's Y" \| Formulaic contrast structure \|
19	\| "Here's why" \| Clickbait-style lead-in \|
20	\| "Here's why it matters:" \| Same energy \|
21	\| "Let's dive in" \| Forced enthusiasm \|
22	\| "In this guide, we'll..." \| Overly formal setup \|
23	\| "It's worth noting that..." \| Unnecessary hedge \|
24	\| "At its core..." \| Pseudo-profound opener \|
25
26	---
27
28	## THE EXACT PROMPT — De-Slopify Documentation
29
30	```
31	I want you to read through the complete text carefully and look for any telltale signs of "AI slop" style writing; one big tell is the use of emdash. You should try to replace this with a semicolon, a comma, or just recast the sentence accordingly so it sounds good while avoiding emdash.
32
33	Also, you want to avoid certain telltale writing tropes, like sentences of the form "It's not [just] XYZ, it's ABC" or "Here's why" or "Here's why it matters:". Basically, anything that sounds like the kind of thing an LLM would write disproportionately more commonly that a human writer and which sounds inauthentic/cringe.
34
35	And you can't do this sort of thing using regex or a script, you MUST manually read each line of the text and revise it manually in a systematic, methodical, diligent way. Use ultrathink.
36	```
37
38	---
39
40	## Why Manual Review is Required
41
42	The prompt explicitly states:
43
44	> "And you can't do this sort of thing using regex or a script, you MUST manually read each line of the text and revise it manually in a systematic, methodical, diligent way."
45
46	Reasons:
47	1. Context matters — Sometimes an emdash is actually the right choice
48	2. Recasting sentences — Often the fix isn't substitution but rewriting
49	3. Tone consistency — Need to maintain voice throughout
50	4. Judgment calls — Some patterns are fine in moderation
51
52	---
53
54	## Emdash Alternatives
55
56	When you encounter an emdash (—), consider:
57
58	\| Original \| Alternative \|
59	\|----------\|-------------\|
60	\| `X—Y—Z` \| `X; Y; Z` or `X, Y, Z` \|
61	\| `The tool—which is powerful—works well` \| `The tool, which is powerful, works well` \|
62	\| `We built this—and it works` \| `We built this, and it works` \|
63	\| `Here's the thing—it matters` \| `Here's the thing: it matters` or recast entirely \|
64
65	Sometimes the best fix is to split into two sentences or restructure entirely.
66
67	---
68
69	## Phrases to Eliminate or Rewrite
70
71	### "Here's why" family
72	- "Here's why" → Just explain why directly
73	- "Here's why it matters" → Explain the importance inline
74	- "Here's the thing" → Usually can be deleted entirely
75
76	### Contrast formulas
77	- "It's not X, it's Y" → "This is Y" or explain the distinction differently
78	- "It's not just X, it's also Y" → "This does X and Y" or similar
79
80	### Forced enthusiasm
81	- "Let's dive in!" → Just start
82	- "Let's get started!" → Just start
83	- "Excited to share..." → Just share it
84
85	### Pseudo-profound openers
86	- "At its core..." → Usually can be deleted
87	- "Fundamentally..." → Often unnecessary
88	- "In essence..." → Just say the essence
89
90	### Unnecessary hedges
91	- "It's worth noting that..." → Just note it
92	- "It's important to remember..." → Just state the fact
93	- "Keep in mind that..." → Often deletable
94
95	---
96
97	## Before and After Examples
98
99	### Example 1: Emdash Overuse
100
101	Before (sloppy):
102	```
103	This tool—which we built from scratch—handles everything automatically—from parsing to output.
104	```
105
106	After (clean):
107	```
108	This tool handles everything automatically, from parsing to output. We built it from scratch.
109	```
110
111	### Example 2: "Here's why" Pattern
112
113	Before (sloppy):
114	```
115	We chose Rust for this component. Here's why: performance matters, and Rust delivers.
116	```
117
118	After (clean):
119	```
120	We chose Rust for this component because performance matters.
121	```
122
123	### Example 3: Contrast Formula
124
125	Before (sloppy):
126	```
127	It's not just a linter—it's a complete code quality system.
128	```
129
130	After (clean):
131	```
132	This is a complete code quality system, not just a linter.
133	```
134
135	Or even better:
136	```
137	This complete code quality system goes beyond basic linting.
138	```
139
140	### Example 4: Forced Enthusiasm
141
142	Before (sloppy):
143	```
144	# Getting Started
145
146	Let's dive in! We're excited to help you get up and running with our amazing tool.
147	```
148
149	After (clean):
150	```
151	# Getting Started
152
153	Install the tool and run your first command in under a minute.
154	```
155
156	---

People who liked this also viewed

6 picks

Type