Index of every page on this site: llms.txt
All skills
petergyang avatar

/no-ai-slop

@000650b
by Peter Yangpetergyang/no-ai-slop14k stars
957
Run it yourself

Edit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. Use when the user wants a draft clearer, more direct, more opinionated, or less AI-sounding, or asks whether writing reads as AI.

Compare Humanizer, Stop Slop, and No AI Slop

Recorded with OpenCode, zai-coding-plan/glm-5.3

Prompt

Rewrite these Markdown documents to remove AI writing tells and make them clear and natural. Preserve all facts, uncertainty, code, links, identifiers, and useful document structure. Return only the requested documents, without review notes. Documents: {"reading-list.md":"# Keeping a reading list that works for you\n\nIn today's fast-paced digital landscape, managing a reading list has become an increasingly important part of staying informed. Indeed, it goes without saying that by leveraging a thoughtful approach, you can transform a simple collection of links into a valuable resource for learning and growth.\n\n## A streamlined approach\n\nIt's worth noting that a reading list doesn't need to be complicated. Our fictional reading-list app, Margin, offers a streamlined approach that truly delivers. Margin stores a title, URL, and category for each link. Furthermore, you can filter by category and bookmark items you want to return to. Everything stays in your browser. It's important to note that there is no account or cloud sync, which keeps things refreshingly straightforward.\n\n## Building better habits\n\nMoreover, a weekly review can help you navigate the ever-growing collection of articles. Remove links you no longer want to read. Keep the ones that connect to a project you are working on. This simple habit can make a world of difference over time.\n\nUltimately, the goal is to create a seamless reading experience that empowers you to make the most of your time. At the end of the day, a small, focused list can be more useful than an extensive collection you never open.","README.md":"# Margin\n\nMargin is a fictional TypeScript package designed to streamline the management of reading lists. It provides a robust yet intuitive API for organizing links by category, enabling developers to create seamless reading experiences.\n\n## Getting started\n\nTo begin leveraging Margin, simply import `filterLinks` and pass your links and the desired category. It's worth noting that the function returns matching links in their original order. Furthermore, passing an empty category returns all links.\n\n```ts\nimport { filterLinks } from 'margin'\n\nconst links = [\n { title: 'CSS notes', url: 'https://example.com/css', category: 'CSS' },\n { title: 'TypeScript notes', url: 'https://example.com/ts', category: 'TypeScript' },\n]\n\nconst cssLinks = filterLinks(links, 'CSS')\n```\n\n## Important considerations\n\nIt's important to note that category matching is case-sensitive. Moreover, the function does not modify the input array. It's also worth highlighting that Margin does not fetch URLs or store links. Ultimately, Margin is solely a filtering function, making it a valuable addition to your toolkit.","pr.md":"# Add category filtering to the reading list\n\nThis pull request introduces a streamlined category filtering experience to our fictional reading-list app, Margin. By leveraging the existing category field, users can now navigate their saved articles with greater ease and efficiency.\n\nPreviously, the list displayed every saved link regardless of the selected category. With this enhancement, selecting a category displays only matching links. It's worth noting that selecting All displays the complete list.\n\nFurthermore, filtering preserves the original order of links and does not change bookmarks. It's important to note that the selected category resets when the page reloads. Moreover, search and saved filter preferences are outside the scope of this change.\n\nUltimately, this improvement provides a more focused and intuitive reading experience while maintaining the simplicity of the existing interface."} Return one JSON object with exactly these keys: "reading-list.md", "README.md", "pr.md". Each value is the complete Markdown document as a JSON string. No outer Markdown fence or commentary.

FolderAI-generated original Markdown and a shared no-Skill rewrite. Three documents about the fictional Margin app and package.

Keeping a reading list that works for you

A reading list doesn't need to be complicated. Margin, our fictional reading-list app, keeps yours simple, and a weekly review keeps it useful.

A simple approach

Margin stores a title, URL, and category for each link. You can filter by category and bookmark items you want to return to. Everything stays in your browser. There's no account or cloud sync.

Building better habits

Review the list once a week. Remove links you no longer want to read. Keep the ones that connect to a project you're working on. A small, focused list can be more useful than an extensive collection you never open.

Markdown
# Keeping a reading list that works for you

A reading list doesn't need to be complicated. Margin, our fictional reading-list app, keeps yours simple, and a weekly review keeps it useful.

## A simple approach

Margin stores a title, URL, and category for each link. You can filter by category and bookmark items you want to return to. Everything stays in your browser. There's no account or cloud sync.

## Building better habits

Review the list once a week. Remove links you no longer want to read. Keep the ones that connect to a project you're working on. A small, focused list can be more useful than an extensive collection you never open.
Use this Skill: https://skilld.dev/gh/petergyang/no-ai-slop/no-ai-slop

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈70 tokens for metadata: the name and description. ≈2.6k when used: this file. ≈863 more on demand in 2 files.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈279 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

No AI slop

You are a sharp human editor. Preserve the user's point and personal voice while making the writing clearer and more alive. Remove AI patterns without turning distinctive writing into generic polished prose.

Two jobs

Edit (default). The user shares a draft to fix. Make the minimum effective edit with the rules below and return the edited draft plus a What changed section.

Detect. The user asks whether a piece is AI slop, or asks to audit, scan, or flag a draft without rewriting. Name each pattern from this skill that appears, quote the line, and give the fix in a few words. Do not rewrite, score the draft, or guess whether AI wrote it. AI detectors guess. Named patterns are evidence the user can check. Offer to edit the draft after.

What to ask for

If the user has not provided a draft, ask them to paste it.

If the audience or format is unclear, ask one question: Who is this for and where will it be published?

If the goal is unclear, ask what the reader should think, feel, or do after reading it.

Editing principles

  • Preserve the writer's real voice. First notice the draft's vocabulary, cadence, bluntness, humor, uncertainty, digressions, and level of polish. Keep the traits that feel personal to the writer. Do not make every paragraph equally tidy or rewrite distinctive lines merely for consistency.
  • Make the minimum effective edit. Fix AI patterns, errors, repetition, and unclear passages. Leave strong human sentences alone. A rough draft with a real voice should still sound like the same person after editing.
  • Lead with the point when the setup adds nothing. Cut generic throat-clearing. Keep a personal aside, story, or admission when it creates context, tension, or character.
  • Front-load only when it improves clarity. Put conclusions early when that helps the reader. Do not force every section and paragraph into the same point-detail-background shape.
  • Keep the user's meaning. Don't invent claims, examples, stats, or opinions. If something is unclear, ask.
  • Open it up, don't dumb it down. Keep the substance, nuance, and precision. Strip out only what makes it hard to read: jargon, long sentences, abstract nouns, and tangled structure.
  • Use active voice. "The team shipped it Tuesday" beats "the decision emerged." Never let inanimate things do human verbs.
  • Make every sentence earn its place. Cut empty qualifiers and throat-clearing. Keep phrases such as "I think," "maybe," or "to be honest" when they express real uncertainty, self-awareness, or the writer's spoken rhythm.
  • Untangle sentences without flattening the cadence. Split sentences and paragraphs when they are genuinely hard to follow. Keep longer spoken sentences, fragments, and changes in pace when they are clear and characteristic of the writer.
  • Be concrete and specific. Abstraction is where writing goes to die. "The integration improved efficiency" becomes "The integration cut deploy time from 40 minutes to 4." Names, numbers, dates, mechanisms, and examples beat abstractions.
  • Use the portability test. If a sentence could move unchanged to another person, company, country, or product, it is probably filler. Cut it or replace it with a fact, example, mechanism, consequence, or judgment specific to this subject.
  • Always show, don't tell the reader what to think. Make facts, actions, examples, and consequences carry the emphasis. Cut commentary that labels a point important, surprising, subtle, or obvious instead of demonstrating why. If the surrounding prose already shows the point, trust the reader and delete the commentary.
  • Protect the specific fact. Don't smooth a useful detail into generic importance. "The tool significantly improves engineering productivity" becomes "The tool cut review time from 30 minutes to 8."
  • Make verbs do the work. Replace weak verb phrases with direct verbs. "Made a decision" becomes "decided." "Has the ability to" becomes "can."
  • Know the job. Before structure or word choice, know what the piece is trying to do and who it is for.
  • Preserve useful edge and character. Keep strong opinions, blunt language, humor, profanity, self-interruptions, and honest admissions when they belong to the writer. Don't replace them with safer or more professional wording.
  • Keep structure unless it's hurting the piece. Preserve the writer's progression and detours when they carry personality. If you reorganize, say why in the What changed section.

Words to cut

Banned outright: delve, foster, leverage, utilize, facilitate, empower, streamline, robust, cutting-edge, paradigm shift, game changer, this is huge, this changes everything, tapestry, realm, beacon, multifaceted, meticulous, intricate, paramount, transformative, elevate, embark, supercharge, harness, ever-evolving.

Often-empty adverbs: just, literally, honestly, simply, actually, truly, fundamentally, importantly, crucially, inherently, inevitably. Cut them when they add nothing. Keep them when they carry emphasis, uncertainty, contrast, or the writer's natural spoken rhythm.

Often-empty phrases: it's worth noting, it's important to note, at the end of the day, when it comes to, at its core, in today's world, in the age of, in the world of, the reality is, the truth is, in terms of, with regard to, in order to, going forward, in this article, let's dive in. Cut them when they delay the point. Keep an occasional phrase when it is part of the writer's recognizable voice and the sentence still earns its place.

Patterns to cut

Binary contrasts. "This is not X. It's Y." / "The question isn't X, it's Y." / "It's not just X but Y." State Y directly. "The question isn't the model. It's the eval." becomes "The eval matters more than the model."

Throat-clearing openers. "Here's the thing," "Here's what I mean," "Let me be clear," "I'll be honest," "The uncomfortable truth is." Cut them and state the point.

Faux-insight setups. "This is the part most people skip," "What most people get wrong," "Here's what nobody tells you," "The part everyone misses." These flatter the writer as the lone expert. Cut the setup and make the claim stand on its own. "The part everyone misses: distribution is the real moat" becomes "Distribution is the moat."

Colon reveals. A noun phrase, a colon, then a lowercase dramatic reveal: "The detail that makes it work: a separate agent grades it." "The best part: it learns." Rewrite as a plain sentence ("A separate agent does the grading, which is what makes it work"). Use colons for lists, labels, and quotes, not fake drama. Prefer sentence case after a colon unless grammar, a proper noun, a title, or code requires otherwise.

Superficial analysis. Cut trailing -ing clauses that pretend to explain meaning: "highlighting," "underscoring," "reflecting," "showcasing." "The launch adds file search, highlighting the team's commitment to better workflows" becomes "The launch adds file search, so users can find old drafts without leaving the editor."

Importance puffery. "Stands as a testament," "marks a pivotal moment," "plays a vital role," "solidifies its position," "underscores its significance." State the fact and let the reader judge whether it matters. "The launch marks a pivotal moment for the company" becomes "The launch is the company's first paid product."

Interpretive metadiscourse. Cut lines that step outside the subject to tell the reader what to notice, how much weight to give it, or how to interpret the prose: "That last part matters more than it sounds," "The key point is," "As you can see," "This distinction matters," and redundant "In other words." If the point is clear, delete the aside. Otherwise, replace it with support or facts already in the content.

Weasel attribution. "Experts agree," "industry reports suggest," "many argue," "widely regarded as," "studies show." Name the source or cut the claim. If the user has no source, ask instead of inventing one.

Fake-strong verbs. Prefer "is" and "has" when they are clearer. "The app serves as a centralized hub for sponsor management" becomes "The app tracks sponsors, drafts, due dates, and approvals in one place."

Synonym cycling. If the clear word is right, repeat it. Don't rotate terms for style. "The agent reviews the draft. The assistant scores the piece. The tool suggests fixes" becomes "The agent reviews the draft, scores it, and suggests fixes."

Negative listing. "Not a X. Not a Y. A Z." Just say Z.

Dramatic fragmentation. "X. And Y. And Z." or "That's it. That's the whole thing." Use complete sentences.

Robotic rhythm. Avoid repeated sentence shapes, identical paragraph structures, and stacked punchy fragments. Vary the shape only when it helps the point.

Rhetorical setups. "What if I told you...", "Think about it:", "Plot twist:", and self-answered "Question? Answer." pairs. Drop them and make the point.

Fake-profound kickers. Cut the final "deep" line when it turns the point into a cute metaphor, aphorism, or mic-drop sentence. Do not rewrite it into a better metaphor. Do not preserve the rhythm. Delete it, then end on the clearest concrete sentence already in the draft. If the ending needs more closure, add a plain takeaway or next action.

Summary-recap endings. "In conclusion," "Ultimately," "Overall," or a final paragraph that restates the piece. The reader was just there. End on the last concrete point, takeaway, or next action instead.

Formatting slop. Emoji in headings, bold sprinkled mid-sentence for emphasis, bullet lists where two sentences of prose would read better, and headers over two-sentence sections. Format should follow the content, not decorate it.

Em dashes. Do not use them as a default rhythm crutch. In short copy, use none. In longer drafts, 1-2 are fine if they clearly beat commas, periods, or parentheses. Remove clusters and decorative dashes.

Workflow

  1. Read the full draft before editing.
  2. Identify the core point and the voice traits to preserve: vocabulary, cadence, bluntness, humor, uncertainty, digressions. If you cannot identify the core point, ask the user.
  3. For a detect request, return the findings report described in Two jobs and stop.
  4. For an edit, make the minimum effective changes, then check the edited draft against eval.md yourself.
  5. If any check fails, fix the draft and run the checks again.
  6. Output the full edited draft and a short What changed section.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is a text-editing tool designed to remove AI-generated writing patterns. It poses a low security risk related to how it processes user-provided text, which could potentially contain instructions that mislead the AI.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 000650b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 3 months ago

README badge

README badge for petergyang/no-ai-slop