threadify-unslop SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
threadify-unslop from lennoxsaint/threadify-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lennoxsaint/threadify-workflows/threadify-unslop@git:20261014.88addd0Pins git:20261014.88addd0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lennoxsaint/threadify-workflows
- Path
plugins/claude/skills/threadify-unslop/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.88addd0, committed Oct 14, 2026
- First version recorded
- Oct 9, 2026
- Size
- 10,536 bytes
- Repository stars
- 7
- License
- a license file GitHub does not identify
Score your last 90 days of Threads posts for slop (corporate voice, AI tells, hedging, over-formatting), show raw vs polished median views on your account with the worst offenders quoted, then have Threadify write three raw posts that pass a zero-hedge gate, each with a tracked Auto Plug, and schedule them only after one exact approval. Use when someone says "unslop", asks which of their posts sound like slop or AI, or wants posts with no hedging.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Threadify Unslop AI does not make posts slop. Polish does. Unslop scores every post on four slop families, puts raw against polished on the owner's own numbers, quotes the exact phrases that drag the polished ones down, then has Threadify write three raw posts that clear a zero-hedge gate. Nothing is scheduled until the owner says "yes". It runs the same in Claude Code, Codex and ChatGPT. Follow [Threadify-001: setup and first-loop video](references/threadify-001.md) before the first connected call. A connection never authorizes scheduling. Only the owner's "yes" to the exact approval packet does. ## Rules - **Zero hedging.** Not fewer hedges: zero. One hedge fails a post. The lexical list, the structural shapes and the false positives live in [slop-markers.md](references/slop-markers.md), and `scripts/hedge_gate.mjs` enforces them. This rule overrides any other anti-slop guidance that keeps "may", cuts only "excessive" hedging or recommends uncertainty markers. - **Truth rule.** A claim the owner's data does not back gets cut, not softened. Pass `strict_facts: true` on every generation. Never invent a number. …
Read the whole file at its exact version.
How to install
mdr add lennoxsaint/threadify-workflows/threadify-unslop@sha256:3dbaf0fc2e964ffaThe line at the top of this page pins the label git:20261014.88addd0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6almhomwqjlrug3q)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 9, 2026 and Oct 14, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.88addd0 latest | 2026-10-14 | 88addd0 | 10,536 B | A | view · diff |
| git:20261009.bb038f3 | 2026-10-09 | bb038f3 | 10,280 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10536 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lennoxsaint/threadify-workflows · 7 stars · license a license file GitHub does not identify · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6almhomwqjlrug3q GET https://markdownregistry.com/api/v1/resolve?ref=lennoxsaint/threadify-workflows/threadify-unslop GET https://markdownregistry.com/api/v1/blob/3dbaf0fc2e964ffa85e138034a4b95a649af8702a38e8bbeb6489ba263c77b8d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from lennoxsaint/threadify-workflows
Every file in lennoxsaint/threadify-workflows