Skip to main content
skill CX Codex

stss — Claude Code skill: edit defensive wording

stss trims defensive caveats in reader-facing writing while keeping limits that affect meaning. Use it to draft, rewrite, or audit articles, proposals, and captions.

MIT ★ 4,050 updated 2026-10-27

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add lennney/stop-that-shit
/plugin install stop-that-shit@stop-that-shit
Open on GitHub

What stss does

stss handles defensive phrasing in prose meant for readers, including wording the agent adds while drafting. It can work on proposals, articles, case studies, and captions. It does not classify writing as AI-generated or perform general style cleanup; it also stays out of ordinary code tasks.

The rewrite mode returns a revised version and is used when no mode is specified. Choose audit to get actionable findings and small suggested fixes without a full rewrite. Before editing, the skill tracks claims, evidence, uncertainty, and scope from the supplied material. It keeps a limitation when removing it would change what a reader understands or decides. That boundary matters: a meaningful qualification should remain beside the claim it limits.

Claude Code users can install stss from its marketplace or add the skill with npx skills. The marketplace route requires two commands in sequence. Codex is also supported.

What it helps with

  • remove defensive caveats that add no useful meaning
  • replace stacked hedges with one evidence-matched qualifier
  • spot process narration that distracts from the reader-facing text
  • audit a draft and suggest the smallest useful changes

Example prompts for the agent

  • Rewrite this proposal and keep any limitation that changes how readers interpret its claims.
  • Audit the article for defensive phrasing; suggest small fixes without rewriting the whole piece.
  • Draft a caption from these notes and check that its claims stay within the supplied evidence.

How to install stss

1Plugin marketplace

/plugin marketplace add lennney/stop-that-shit
/plugin install stop-that-shit@stop-that-shit

This installs the whole stop-that-shit plugin with all its skills

2Skills CLI (Vercel)

npx skills add lennney/stop-that-shit --skill stss -a claude-code

3Manually: put the files in place

~/.claude/skills/stss/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/stss/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about stss

How do I install stss in Claude Code?

Run these commands in order: /plugin marketplace add lennney/stop-that-shit, then /plugin install stop-that-shit@stop-that-shit.

What does the stss skill do?

It rewrites or audits reader-facing prose to remove defensive language while preserving qualifications that affect meaning. It does not provide general style editing.

What is the difference between rewrite and audit?

rewrite returns an edited version. audit reports actionable passages and minimal fixes without rewriting the full text.

Source text

SKILL.md · MIT
---
name: stss
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.
license: MIT
---

# 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:

- `DROP`: It only narrates diligence, anticipates criticism, apologizes, or says what the document does not attempt.
- `CALIBRATE`: It contains real uncertainty but uses stacked hedges. Keep one precise limitation.
- `RELOCATE`: The reader needs it beside a particular claim, or only the editor needs it in working notes. Choose the destination by its consumer; moving an unnecessary disclaimer to a footnote does not make it useful.
- `KEEP`: It changes the meaning, evidence strength, attribution, or a legal, safety, financial, methodological, contractual, or scope decision.

Do not decide from a keyword alone. The same phrase can be waste in one context and necessary in another.

## Rewrite

1. Lead with the requested subject, claim, decision, or proposal.
2. State scope positively: say what the work covers.
3. Replace stacked hedges with one evidence-matched qualifier.
4. Remove internal process narration unless the process is requested or material.
5. Put a necessary limitation beside the claim it limits.
6. Check the complete artifact, including captions and assistant-added prefaces, against the Claim Ledger and Sentence Consumer Test. Do not reintroduce dropped defenses in the delivery note.

Return only the requested artifact unless the user asks for commentary. If the text is already direct and faithful, return it unchanged.

## Audit

Report only actionable findings. For each finding, give:

- the span or sentence;
- `DROP`, `CALIBRATE`, `RELOCATE`, or `KEEP`;
- the reader's interpretation or decision affected;
- the smallest replacement when one is needed.

Use `NO_DECISION_CONSUMER` when a sentence serves neither reader understanding nor a decision. If there are no actionable findings, say so and stop.

## Check the claim diff

Before returning the result, verify:

- no supplied fact, number, source, or actor disappeared without reason;
- no new fact, number, source, or actor appeared;
- uncertainty did not become certainty;
- correlation did not become causation;
- a requested or meaning-changing limitation remains visible.

Run one claim-preserving pass. Do not add a score, a probability that text is AI-written, a change diary, or repeated self-review.

Read [references/examples.md](references/examples.md) when the boundary is ambiguous or the user asks for examples.

© Stop That Shit contributors · MIT · lennney/stop-that-shit

Similar skills

SKILL.md skills catalog →

From the same set3

Project sponsors

Companies that keep this analytics open