Menú
Write or rewrite copy that sounds human. Kills generic AI filler, asks for specifics before writing, and pushes back on vague prompts. Use when writing marketing copy, landing pages, blog posts, event descriptions, or any user-facing text.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
enforce the iron laws on all written output. activate when writing, editing, or reviewing any text including copy, emails, taglines, descriptions, blog posts, social media, proposals, bios, documentation, README files, commit messages, code comments, UI strings, error messages, PR descriptions, changelogs, or any content task. also activate when the user asks for feedback on existing writing.
enforce the iron laws on all written output. activate when writing, editing, or reviewing any text including copy, emails, taglines, descriptions, blog posts, social media, proposals, bios, documentation, or any content task. also activate when the user asks for feedback on existing writing. these rules override default chatgpt writing style.
Ten rules that stop AI from writing like AI. Activate on any writing, editing, or copy review task. Overrides default writing style with specific, human-sounding output.
Structured 4-phase workflow for non-trivial tasks. Enforces Understand, Plan, Execute, Verify phases with quality gates.
Run a multi-angle code review using three specialist agents in parallel. Use when the user types /review or when finishing a code task.
| name | noslop |
| description | Write or rewrite copy that sounds human. Kills generic AI filler, asks for specifics before writing, and pushes back on vague prompts. Use when writing marketing copy, landing pages, blog posts, event descriptions, or any user-facing text. |
| argument-hint | ["what to write or rewrite"] |
Write or rewrite copy with zero AI slop. This skill forces you to ask the right questions before writing and reject generic filler.
Type /noslop write hero copy for my deployment platform to write from scratch. Or /noslop rewrite this: [paste existing copy] to fix something that already exists.
These rules are active for the duration of this task. Follow all of them.
Never use emojis in any output. Plain text only.
Never use em dashes. Use commas, periods, or restructure the sentence. Em dashes are the single most reliable tell that text was AI-generated. Exception: box-drawing characters (├── └── │) are not em dashes. Leave them alone.
All copy must sound like a human wrote it. Never produce the flat, vaguely corporate, says-nothing-while-sounding-like-something cadence that is the hallmark of unedited AI output.
Kill on sight:
If you don't have enough detail to write something that could only describe THIS specific thing, ask before writing. Do not produce generic copy and offer to refine later. Get the details, then write.
Challenge vague prompts. If the request would produce copy that could describe any product in any industry, say so and ask for specifics. Don't be agreeable at the expense of quality.
When offering options, rank them by recommendation. Explain why your top pick is your top pick. No open-ended lists without guidance.
Read $ARGUMENTS. Determine if this is:
Before writing anything, check if you have enough to write something specific. You need at minimum:
If any of these are missing, ask. Keep questions short and direct. Don't ask more than 4-5 questions at once.
If this is a rewrite, diagnose what's wrong with the current copy first. Name the specific problems (generic filler, hollow verbs, no differentiator, etc.) before rewriting.
Write the copy. Keep it specific. Every sentence should say something that couldn't be said about a competitor.
If appropriate, offer 2-3 options with different angles (e.g., direct, problem-first, punchy). Rank them and explain your pick.
Before presenting the final copy, apply this test: swap the product/company name with a competitor's name. Does the copy still work? If yes, it's too generic. Rewrite until swapping names would break it.
If the copy needs a call to action, ask what the CTA should be rather than defaulting to "Learn More" or "Get Started." The CTA depends on the business model (free trial, waitlist, demo, purchase).
