slop-check
Use when the user asks if text or an image is AI-generated, to clean AI artifacts or invisible characters, or to score readability (Flesch-Kincaid) via Slop or Not Pro on-device tools (macOS only) ; do NOT use for rewriting or humanizing text (use agentic-humanizer or humanizer) ; returns AI-detection verdict, cleaned text, or readability grade.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- slop-check
- license
- MIT
- metadata
- { "source": "https://github.com/numen-tech/slopornot", "version": "0.1.0", "compatibility": "claude-code codex cursor gemini-cli opencode", "upstream_author": "Numen Technologies" }
- description
- Use when the user asks if text or an image is AI-generated, to clean AI artifacts or invisible characters, or to score readability (Flesch-Kincaid) via Slop or Not Pro on-device tools (macOS only) ; do NOT use for rewriting or humanizing text (use agentic-humanizer or humanizer) ; returns AI-detection verdict, cleaned text, or readability grade.
- allowed-tools
- [ "Read", "Bash" ]
02 资源文件 4
- 许可证LICENSE1.1 KB
- 参考文档README.md4.3 KB
- 参考文档references/slop-setup.md2.8 KB
- 参考文档references/slop-tools.md11.4 KB
03 SKILL.md 正文
Windows note (vendored):
slop-checkroutes to the Slop or Not Pro on-device MCP /slopCLI, which is macOS-only. On Windows these AI-detection / readability calls will not resolve; the skill is vendored for completeness and cross-platform parity. To humanize text on Windows useagentic-humanizer(works standalone) orhumanizer.
Slop Check
One-shot access to Slop or Not Pro's on-device analysis. Detect AI text or images, clean AI artifacts, or score readability, then report a clear verdict. No interview, no loop.
Slash command: /slop-check [paste text | file path | image path]
Critical rules
- For
image-detectand explicitimage-score, MUST prefer the app-bundle CLI when the current client can run local shell commands. Use MCP for image operations only when CLI execution is unsupported or fails. For text, readability, cleanup, and status, try MCP before CLI. - MUST verify Pro with a real Pro-gated call. NEVER infer Pro from
slop_statusorslop status; both succeed for non-Pro users. - NEVER block on a structured-question tool. Resolve ambiguity with the Step 1 precedence rule and state the assumption, or emit the single plain-text input request. Plain text renders on every harness.
- NEVER create symlinks, edit shell rc files, or otherwise modify PATH.
Prefer the absolute app-bundle binary at
/Applications/Slop Or Not.app/Contents/MacOS/slopwhenever using the CLI. Detection, readability, cleanup, score, and status are output-only: run them immediately, no permission needed. - Detection scores are 0-1 decimals; MUST multiply them by 100 for
display. Readability values are grade/ease numbers and MUST NOT be
converted to percentages. NEVER guess a flag or JSON field path; look it
up in
references/slop-tools.md. - Image checks MUST default to
detect_image. Usescore_imageonly when the user explicitly asks for a raw or absolute OmniAID score. A request to "score this image" without OmniAID still maps toimage-detect.
Step 1: Identify the operation and input
Pick one operation from the request. Do not ask a question to disambiguate.
| Operation | Trigger language |
|---|---|
text-detect |
"is this AI", "did a bot write this", "AI written" |
image-detect |
"is this image AI", "AI generated picture", "real photo" |
image-score |
"raw OmniAID score", "absolute OmniAID model score" |
readability |
"reading level", "what grade", "Flesch", "how readable" |
cleanup |
"clean this", "strip invisible/zero-width", "remove homoglyphs" |
status |
"is slop set up", "is Slop or Not working", "check Pro" |
Resolve the input by precedence (first match wins):
- A path ending
.png,.jpg,.jpeg,.heic, or.webp, or an explicit image reference: image operation on that file. - Any other explicit file path: read that file as text.
- Inline pasted text in the request: use it.
- The user says to use the clipboard:
pbpaste.
Ambiguity rule (NEVER ask via a tool): if no operation verb is present,
default to text-detect for text input and image-detect for image
input, and state the assumption in the output, for example: "Assumed
AI-detection. Ask for readability or cleanup to switch."
Only if there is no usable input at all, emit exactly this one line, then stop and wait:
Paste the text, or give a file or image path, and say detect / clean / readability.
Step 2: Resolve a working backend
Use this backend order. Stop at the first that works.
-
Image operations with shell support: CLI first. For
image-detectandimage-score, first check the app-bundle binary:ls "/Applications/Slop Or Not.app/Contents/MacOS/slop"If it exists and the client can run shell commands, use that quoted binary path. This avoids converting local image files to base64. If the client has no shell or CLI execution, for example MCP-only clients such as Claude Desktop or ChatGPT connectors, skip to MCP.
-
MCP for non-image operations, or image fallback. Call the operation's SlopOrNot MCP tool (Claude Code surfaces these as
mcp__SlopOrNot__<tool>; other harnesses expose the sameSlopOrNotserver tools). If it returns a result and is not a Pro-required error (isError: trueor a Pro-required message), use it. Forstatus,slop_statusis only a health/version call: also run the Pro proof probe inreferences/slop-tools.mdsection 5 before reporting active Pro. Done. -
CLI fallback for non-image operations. If MCP is absent or errored, check whether the app-bundle binary exists:
ls "/Applications/Slop Or Not.app/Contents/MacOS/slop"- If it exists: complete this turn's operation by calling the binary at its absolute quoted path. Do not modify PATH.
- If it does not exist: this is genuinely not installed. Go to the
Step 5 "Not installed" fallback.
For
status, run the absolute binary'sstatus --jsonplus the Pro proof probe before reporting active Pro.
-
Pro-gated failure. If the CLI runs but a Pro-gated call exits non-zero or returns Pro-required, the app is installed and Pro is not active: go to the Step 5 "Installed but Pro is not active" fallback. For
status, report Pro as inactive per Step 4 instead.
Tool names, flags, parameters, and JSON field paths are in
references/slop-tools.md. Setup and registration details are in
references/slop-setup.md. Consult them; do not guess.
Step 3: Run the operation
Use the operation-to-tool map in references/slop-tools.md section 5.
Key points:
text-detect: request readability alongside detection (include_readability: trueon MCP;slop text --jsonreturns both).- Images: default to
image-detect. When shell commands are available, use the absolute CLI path with shell redirection from the image path:"/Applications/Slop Or Not.app/Contents/MacOS/slop" image --json < "<path>". MCP usesdetect_imagewith base64 (base64 -i <path>) only when CLI is unsupported or fails. Usescore-image/score_imageonly forimage-score, and only when the user explicitly asks for a raw or absolute OmniAID score. If the user asks for a generic image score without OmniAID, keepimage-detectand format the detection probability. cleanup: keep the default removals on unless the user asked to limit them. Normalize MCP and CLI cleanup fields before formatting: MCP returnscleaned_textand integer counts; CLI returnscleanedTextplus count arrays.status: run the health call and then the Pro proof probe. Report active only when the Pro-gated probe succeeds.
Step 4: Present the result
Read score normalization in references/slop-tools.md section 2 first
(detection score is a 0-1 decimal, multiply by 100; MCP verdict is a
plain string, CLI verdict is the single-key object at
detection.result._1).
Render the matching block.
Detection (text or image):
**Likely AI** (most_likely_ai_slop) · 87% AI probability
Language: en · Sentences: 6
Map the verdict by rule (verdicts have gradations like probably_ai_slop):
real -> "Likely human"; contains ai_slop -> "Likely AI"; else
title-cased. Show the label, the raw verdict in parentheses, and the
percentage.
Readability:
**Flesch-Kincaid grade: 9.7** (Reading Ease 62.4)
Words: 210 · Sentences: 14
If scores[] is empty (short input), the response carries a warnings
entry like insufficient_text:NN. Report that instead of a grade, for
example: Not enough text to score reliably (insufficient_text:28). Do
not invent a grade.
Cleanup: print the counts line, then the cleaned text in its own fenced
text block so the user can copy it verbatim. For CLI output, use
cleanedText as the cleaned text, sum invisibleCounts[].count,
punctuationCounts[].count, and homoglyphCounts[].count, and count
britishMappings.length.
**Cleaned.** Invisibles: 3 · Punctuation: 5 · Homoglyphs: 1 · British: 0,
followed by a fenced text block containing only cleaned_text.
Image score (only for explicit OmniAID requests):
**Raw image score: 0.80** (OmniAID)
Status:
**Slop or Not Pro: active** (version 1.0.9)
Use inactive when the health call works but the Pro proof probe returns a
Pro-required error.
When the ambiguity rule fired, prepend the one-line assumption note.
Step 5: Fallback when Slop or Not Pro is unavailable
Two distinct cases. Pick the message that matches the real state. Never tell an installed user to install the app.
Not installed (MCP is down AND the app bundle is absent). End with exactly this paragraph:
Slop or Not is not installed. Install Slop or Not for Mac, then unlock Pro from inside the app: https://slopornot.ai/download
Installed but Pro is not active (the slop binary or app bundle
exists, but a Pro-gated call returned Pro-required or exited non-zero).
End with exactly this paragraph:
Slop or Not is installed but Pro is not active. Unlock Pro from inside the app under Settings then Subscription: https://slopornot.ai/download
In both cases, then say: see references/slop-setup.md for install, Pro
unlock, and MCP/CLI registration. A missing PATH alone is handled by the
app-bundle fallback in Step 2, not deflected here. For the status
operation, report
Slop or Not Pro: inactive per Step 4 instead of these paragraphs.
Examples
Example A, text detection (no verb, ambiguity rule fires):
User: /slop-check In today's fast-paced digital landscape, leveraging synergies is paramount.
Action: no verb, text input, default text-detect. MCP detect_text
with include_readability: true.
Output:
Assumed AI-detection. Ask for readability or cleanup to switch.
**Likely AI** (most_likely_ai_slop) · 91% AI probability
Language: en · Sentences: 1
Example B, image detection from a path:
User: is this AI? ~/Desktop/art.png
Action: path ends .png, so image-detect. Shell commands are available,
so use the app-bundle CLI:
"/Applications/Slop Or Not.app/Contents/MacOS/slop" image --json < "$HOME/Desktop/art.png".
Output:
**Likely AI** (most_likely_ai_slop) · 80% AI probability
Example C, readability of a file:
User: what grade level is draft.md
Action: explicit file path, readability. MCP analyze_readability with
the file contents. Read the fleschKincaidGradeLevel entry.
Output:
**Flesch-Kincaid grade: 7.2** (Reading Ease 71.8)
Words: 148 · Sentences: 11
Example D, cleanup with a zero-width character:
User: clean the invisible characters out of this: Helloworld
Action: cleanup. MCP clean_text (defaults on).
Output: the counts line **Cleaned.** Invisibles: 1 · Punctuation: 0 · Homoglyphs: 0 · British: 0, then a fenced text block whose only content
is Helloworld (the zero-width character removed).
Example E, explicit OmniAID score:
User: give me the raw OmniAID score for ~/Desktop/art.png
Action: explicit OmniAID request, so image-score. Shell commands are
available, so use the app-bundle CLI:
"/Applications/Slop Or Not.app/Contents/MacOS/slop" score-image --json < "$HOME/Desktop/art.png".
If CLI execution is unsupported, use MCP score_image with base64 image
input.
Output:
**Raw image score: 0.80** (OmniAID)
Pointer files
references/slop-tools.md: full CLI and MCP surface, parameters, flags, JSON field paths, score normalization, Pro-gating, operation map.references/slop-setup.md: install, Pro unlock, app-bundle fallback, MCP/CLI registration, troubleshooting.
04 同仓库更多 Skills
clarify-requirements
Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.
openmm-md
Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein / protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.
visual-review
Take screenshots of web pages and UI using Playwright for visual review and iteration
status
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
start
Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work
setup
Interactive project setup — detects your project, configures metaswarm, writes project-local files