# Stss

Reduce defensive disclaimers, stacked hedging, and self-protective narration when...

- Repository: https://github.com/lennney/stop-that-shit (3457 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add lennney/stop-that-shit --skill stss -g -a claude-code -y`
Codex: `npx skills add lennney/stop-that-shit --skill stss -g -a codex -y`
Cursor: `npx skills add lennney/stop-that-shit --skill stss -g -a cursor -y`
Gemini CLI: `npx skills add lennney/stop-that-shit --skill stss -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add lennney/stop-that-shit`

## Description

Reduce defensive disclaimers, stacked hedging, and self-protective narration when drafting, rewriting, or auditing proposals, articles, case studies, captions, and other reader-facing prose. Use when defensive wording is requested for review or appears in a draft, including wording the assistant adds. Preserve meaningful limits; do not perform general style cleanup or ordinary code work.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Stop That Shit Slop

别再废话。

Make the point without writing for an imaginary critic. Preserve limitations that change what the reader understands or decides.

## Stay in scope

Reduce defensive wording in reader-facing prose, including captions and introductions. Do not classify text as AI-written, promise to remove an "AI voice," humanize unrelated prose, or perform a general style cleanup.

Judge sentences by their reader use, including sentences introduced during drafting. A request to describe a project's evolution calls for that history; it does not by itself call for an account of how the article's sources were checked.

## Select the mode

- `rewrite`: Return a tighter version. This is the default when the user provides text without a mode.
- `audit`: Identify defensive writing and propose the smallest useful fix. Do not rewrite the full text.

Follow an explicit mode. Infer the mode from the request only when none is given.

For a drafting request, create the requested artifact from the supplied material and apply the rewrite checks before returning it.

## Record the claims

Before editing, build a private Claim Ledger from the supplied material:

- facts and numbers;
- named actors and sources;
- evidence strength;
- stated uncertainty and scope;
- what the reader needs to understand or do.

Do not print the ledger unless the user asks for it. Do not add facts, sources, numbers, certainty, or causality.

Keeping facts accurate does not require printing every editorial note. Keep verification logs and source-checking process in working notes unless the reader needs them. Preserve useful attribution, actual methods, and conditions that affect a claim.

## Test each defensive sentence

Apply the Sentence Consumer Test:

1. Who will use this sentence?
2. What understanding or decision does it change for this reader?
3. What becomes false or misleading if it is removed?

Choose one action:

The rest: https://github.com/lennney/stop-that-shit/blob/HEAD/codex-plugin/skills/stss/SKILL.md