agentleFS
JosephbadigarJosephbadigar/sitepeel/skills/slop/SKILL.md

slop

Skill1 starsChanged 19 days agoMITView on GitHub

Check how AI-generated a public website looks with Sitepeel's AI slop checker, which returns a 0 to 100 score, the tells found on the page with a fix for each, and a fix prompt. Use to review a landing page before launch or to answer "does this site look AI-made?".

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. jellydn/my-ai-tools★ 129same name
    2. davidanthonyn/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call Sitepeel's check_ai_slop tool with url.

    line 7
  2. Distinctive:

    If this project builds that page, offer to apply the fixes, using the fix prompt as a guide.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
  1. Take the page the user gave: a domain or a full link. It has to be public, so a local dev server won't work. If they gave nothing, ask for one.
  2. Call Sitepeel's check_ai_slop tool with url. If the result has status: "pending", wait retryAfterSeconds and call it again with the same arguments.
  3. Reply with the score, the verdict and the top tells, each with its fix, as a short list.
  4. If this project builds that page, offer to apply the fixes, using the fix prompt as a guide. Don't change files until the user agrees.
  5. Credit "Sitepeel (sitepeel.dev)" and link the source page.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.