Unslop
Cut AI tells from any writing. Must always apply. Observe required inputs first; HOLD when they are missing rather than guessing.
Install
npx skills add jeremybrasher/grokbot-skills --skill unslopgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/pstack/skills/unslop ~/.claude/skills/unslopPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Unslop ## When to use Cut AI tells from any writing. Must always apply to prose surfaces you produce or edit when this skill is in play. **Do not use when:** - Object is source code, config, or generated data - User asked for authorship/cheating verdicts from tells - There is no text to edit ## Intake — before you proceed You need all of the following. If any is missing, stop. 1. The prose text (pasted or a named file) 2. Whether to rewrite or only flag 3. Authority to edit if a file is involved If any is missing, stop. Say what is missing and what you need. Do not invent inputs to keep moving. ## HOLD — stop and return this, not a polished guess When you cannot proceed, return the gap. | Condition | What is missing | What it needs | Return instead | |---|---|---|---| | No text | The passage | Pasted prose or a file path | I need the text. I will not invent a sample. | | Structured non-prose file | A prose surface | Different file or detect-only on comments | Prose rewrites corrupt structured content. Holding. | | Authorship verdict requested | A decision this skill cannot make | Human judgment beyond pattern flags | Signals, not proof. No verdict. | | No edit authority | Explicit rewrite/edit ask | Detect-only or the question | Flags only. No rewrite. | A HOLD is a return value, not a delay before you guess. ## Defaults: cut first This operation defaults to less, not more. - Subtract tells; do not add personality or facts - Leave clean passages untouched
Details
- Skill name
unslop- Repository
- jeremybrasher/grokbot-skills
- Path
collections/pstack/skills/unslop/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Unslop skill do?
Cut AI tells from any writing. Must always apply. Observe required inputs first; HOLD when they are missing rather than guessing.
How do I install the Unslop skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill unslop. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Unslop popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Vertical Creator
38jeremybrasher/grokbot-skills
Domain-knowledge primer for the marketing & creator vertical (creators, newsletter writers, podcasters, course sellers) so architect/pm don't spec naively against incumbents (Substack ~10%, Patreon 8–12%, Kajabi $149+, beehiiv, Buffer/Hootsuite/Later). Supplies the vocabulary, the non-obvious take-rate/red-ocean rules, the entities a real scheduler/analytics/monetization/sponsorship product must model, and the per-product wedge — with sponsorship-crm flagged as the white-space wedge. Applied by architect/pm during spec authoring for any of the four products in this vertical — content-scheduler
Technical Writing
38jeremybrasher/grokbot-skills
Layered technical-writing standard: Di\u00e1taxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages. Observe required inputs first; HOLD when they are missing rather than guessing.
Vertical Logistics
38jeremybrasher/grokbot-skills
Domain knowledge for the logistics & supply-chain vertical (SMB shipping & inventory) so architect and pm don't spec naively. Covers the vocabulary (TMS vs WMS, multi-carrier rate shopping, dimensional weight, BOL/ASN, lot/batch, reorder point), the non-obvious rules incumbents get right, what a naive build gets wrong, and the entities each of the four products (shipment-tracking, warehouse-lite, route-optimization, po-mgmt) must model. Applied by architect when writing ARCH-{slug}.md and by pm when writing PLAN-{slug}.md for any logistics product.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.