Write Like Your Business Has a Human Behind It

This loads the rules into the conversation. It does not permanently install a slash command. If the assistant cannot open GitHub or read attachments, paste the file contents yourself. A URL alone is not proof it read the instructions.

Install No AI Slop in your AI agent

No AI Slop is an editing skill, not a standalone app. Choose one installation method below. You need an agent that supports installing skills, such as a compatible Claude Code or Codex setup. Ordinary chat access does not automatically include permission to install files.

Before installing: Open the repository at the bottom of this guide and review its README, SKILL.md and eval.md. Global installation makes the skill available beyond one project for supported agents under your user account. On a managed work computer, get approval before adding third-party instructions or packages.

Option A: ask your agent to install it. Open your agent and paste the repository’s installation prompt below. This is an instruction for the agent, not a terminal command.

Install the /no-ai-slop skill globally from https://github.com/petergyang/no-ai-slop

Review any installation or file-access request before approving. Ask the agent to show the installed file path and confirm it can read the skill and evaluation rules. If it cannot install skills in that environment, use the paste-instructions method above instead. A message saying “installed” without a file or host confirmation is not enough.

Option B: install from your computer’s terminal. This route needs Node.js and npm, which provides npx. Open Terminal on macOS/Linux or PowerShell on Windows and check:

node --version
npm --version
npx --version

If a command is missing, install a supported Node.js LTS release from the official Node.js website or through your organization’s approved software manager, then reopen the terminal. Do not enter these commands into an ordinary chat window.

The repository documents this installation command:

npx skills add petergyang/no-ai-slop --skill no-ai-slop --global --yes

This downloads and runs the skills installer and installs the named skill globally for supported agents. The --yes flag accepts installer prompts automatically, so review the command and source before running it. Read the installation result to confirm which agent locations were updated. Do not assume every AI app on your computer now has the skill.

Verify before using business copy. Start a fresh agent session if the skill is not immediately visible. Ask it to load no-ai-slop and identify its installed location, then run this fictional test:

/no-ai-slop is this slop? In today's fast-paced world, our platform marks a pivotal moment in business innovation.

Check that the response quotes the supplied wording, names relevant patterns such as an empty opening or inflated importance, and suggests short fixes without rewriting the whole draft or assigning an AI-authorship score. Then ask it to edit the same sentence. It should not invent product features or statistics to replace the vague claim. If the command is unrecognized, check the target agent in the installer output or use the manual route.

Cost and privacy: The repository is free and MIT-licensed. Your AI service may charge for use. Copy submitted for review goes through your chosen AI host and its data policies; installing the skill does not make that processing local or private.

After a supported installation, the documented commands are:

/no-ai-slop is this slop? [paste your draft]

/no-ai-slop [paste your draft]

The first is detect mode; the second edits and lists changes. Replace the bracketed text with your actual copy. If your app treats the command as ordinary text, use the manual route above rather than repeatedly claiming it is installed.

The skill files are free under the repository’s MIT license. A paid assistant subscription, usage charges or organizational restrictions may still apply. Do not upload private copy to an unfamiliar third-party “humanizer.”

Create your Voice and Facts file

Copy this template into a document. Fill it before asking for an edit. If a field is unknown, write “unknown” and ask the model to flag it rather than fill it in.

ASSET: Homepage / product page / automated email
AUDIENCE:
READER QUESTION:
DESIRED ACTION:
VERIFIED FACTS: Features, materials, dimensions, prices, eligibility, delivery, returns.
CLAIM SOURCES: Fact ID | exact fact | source or approved policy | date checked.
NON-NEGOTIABLES: Legal text, warnings, exclusions, guarantees and exact numbers.
VOICE SAMPLES: Two short pieces I wrote and want to sound like.
VOICE TRAITS: For example, plain, mildly funny, direct, no fake urgency.
WORDS OR LINES TO KEEP:
THINGS WE DO NOT CLAIM:
ORIGINAL COPY:
[Paste the complete asset, including buttons and footnotes.]

Never invent a stronger number to make copy feel concrete. “Faster” cannot become “saves five hours” without evidence. Keep limitations that affect a purchase decision even when they interrupt a neat sentence.

Audit first, edit second

Prompt A: exact-line audit

Paste this after the instructions and your Voice and Facts file. Save the response as Copy Audit.

Use the No AI Slop instructions in detect mode. Do not rewrite the asset yet and do not assign an AI-authorship percentage or detector score.
Read the full original. First list the sections you received so I can check coverage.
For each real issue, return:
1. Location or heading.
2. Exact quote copied from my draft.
3. Named pattern or factual problem.
4. Why it hurts clarity, specificity or the reader’s decision.
5. Smallest suggested fix.
6. Facts or clarification needed before editing.
Prioritize unsupported claims, then missing or confusing information, then style.
Do not flag a line just because it contains a dash, a list or a common word.
Keep strong lines and briefly identify what should remain untouched.
Stop after the audit and wait for my approval.

Check before continuing: every quote must exist in the original. Reject invented quotes and subjective complaints that do not explain a reader problem. For long pages, work section by section and maintain a list of completed sections.

Prompt B: minimum-change edit

Mark each proposed change KEEP, EDIT, DELETE or NEEDS FACT. Then paste this prompt with those decisions.

Edit only the changes I marked EDIT or DELETE. Preserve my meaning, voice samples, structure and strong lines.
Use only facts in my approved fact file. Preserve numbers, prices, dates, units, guarantees, exclusions, product names and CTA destinations exactly unless I explicitly approve a change.
Do not invent examples, testimonials, urgency, sources or opinions.
If a fix needs a missing fact, flag it under Open questions and leave that claim unpublished rather than guessing.
Return:
A. The full revised draft.
B. A change log: original quote | replacement | reason.
C. Open questions and unresolved claims.
D. A brief check against eval.md, including any failed checks.
Do not publish or overwrite the original.

Prompt C: factual and voice review

Compare the original, approved fact file and revised draft.
List any changed or added number, policy, promise, qualification, feature, quote or source. Check each against the supplied evidence. Mark absent evidence as unverified.
Check whether my distinctive words, humor, uncertainty and useful details survived.
Flag new generic phrases, invented confidence and passages rewritten without a clear reason.
Confirm every original section was reviewed, including buttons, footnotes and email subject lines.
Return discrepancies and the exact passage to fix. Do not declare the draft accurate based only on your own earlier output.

Then do the source check yourself. Another AI pass can help find discrepancies, but it is not independent evidence. Read the revision aloud and compare it side by side with the original.

Three business-copy examples

All examples here are fictional. Each rewrite uses only the facts stated alongside it.

Homepage: replace praise with the actual job

Approved fact: The product puts enquiries from website forms and email in one inbox. No time-saving study exists.

Before: “In today’s fast-paced business landscape, our innovative platform empowers teams to unlock seamless communication.”

After: “See enquiries from your website forms and email in one inbox.”

Why: The rewrite names the inputs and output. It does not invent a revenue lift or time saving. A suitable button might be “See how the inbox works” if that destination exists.

Product page: retain personality and useful specs

Approved facts: A 750 ml bottle, dishwasher-safe body, lid washed by hand. Owner’s preferred line: “For people who forget where they left their water.”

Before: “For people who forget where they left their water. More than a bottle, it’s a testament to sustainable living. Its robust design elevates every sip.”

After: “For people who forget where they left their water. Holds 750 ml. Put the body in the dishwasher and wash the lid by hand.”

Why: Keep the writer’s joke. Replace generic claims with specifications and care instructions. Do not add an environmental claim without supporting evidence.

Automated email: get to the next action

Approved facts: The customer requested a demo. The booking link is valid. No deadline or scarce-slot claim is approved.

Before: “We’re thrilled to embark on this transformative journey with you. Take the next step toward unlocking your full potential.”

After: “Thanks for requesting a demo. Choose a time using the booking link below. Reply with the workflow you want us to show.”

Why: The email states why it arrived and what to do next. Keep required consent, unsubscribe and legal text unchanged.

Prevent the same problems in the next draft

Use this brief before generating new copy. Attach the completed Voice and Facts file.

Draft this asset using the attached Voice and Facts file.
Answer the reader’s main question early. Use specific approved facts and my voice samples. Keep meaningful limitations beside the claims they qualify.
Avoid generic openings, inflated importance, unsupported authority, forced contrasts and repeated dramatic fragments.
Do not replace missing evidence with confident language. Put missing information in a separate questions list.
Keep the CTA specific to the real next step. Do not invent scarcity or testimonials.
After drafting, audit for named patterns and make only changes that improve clarity. Return the draft and a short list of factual checks still needed.

Before approving a page, try the portability test: could the sentence appear unchanged on a competitor’s site? If yes, replace it with a supported detail or delete it. Do not delete useful navigation or standard legal wording merely because it is common.

Keep three reusable outputs

Review new or substantially changed copy before publishing. Recheck prices and policies whenever the underlying business terms change. Preserve the old version so you can restore it.

Troubleshooting

Final publishing check

1. The reader can identify what is offered, who it is for and what to do next.
2. Every number, testimonial and consequential claim has a checked source.
3. Prices, guarantees, exclusions, care instructions and legal text are preserved.
4. The writer’s useful voice remains. No fake personal experience was added.
5. Buttons and links lead to the right places. The copy works on mobile.
6. No placeholders, model commentary or broken citations remain.
7. A human approved the text and saved the original before publication.

Track the business outcome separately from the style audit. If you test two versions, define one relevant outcome such as completed enquiries or purchases and keep other changes controlled where possible. A before-and-after change alone does not prove the copy caused a conversion difference.

What this changes

Your team can approve edits by checking the quoted sentence, the supporting facts and the proposed change. Keep that record with each published asset so the next round starts from approved copy instead of another generic rewrite.

Further reading: Wikipedia: Signs of AI writing. This guide adapts its observations for business copy; it is not Wikipedia policy or an authorship detector.

Original skill: No AI Slop by Peter Yang. Review the current README, skills/no-ai-slop/SKILL.md, eval.md and MIT license before use. The practical templates and fictional business examples in this guide are adaptations, not official examples from the repository.

Get the repository: https://github.com/petergyang/no-ai-slop