lennney/stop-that-shit / codex-plugin/skills/stss
stss
VerifiedReduce 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.6 KB |
| agents/openai.yaml | config | 311 B |
| references/examples.md | markdown | 7.4 KB |
references/examples.md
View on GitHub# STSS examples
These synthetic pairs show the boundary between defensive padding and context that changes the reader's understanding or decision. They are examples, not a banned-word list.
## 1. Proposal disclaimer — DROP unless requested
### Bad Case
**Request:** Rewrite this pilot result for a proposal.
**Before:** We should note that this was only a limited first-round pilot and is not intended to prove that the approach works in every setting. In 120 tickets, 24-hour completion rose from 68% to 76% after automatic triage was introduced.
**Rewrite:** In the first 120-ticket pilot, 24-hour completion rose from 68% to 76% after automatic triage was introduced.
**Why:** The sample and observed result already bound the claim. The unrequested universal disclaimer has no decision consumer.
### Nearest Good Case
**Changed condition:** The approving manager requires the proposal to state that the internal pilot does not represent general deployment.
**Rewrite:** In the internal 120-ticket pilot, 24-hour completion rose from 68% to 76% after automatic triage was introduced. This internal pilot does not represent general deployment.
**Boundary:** Keep a requested limitation that affects approval.
**Claim Diff:** Both versions preserve the sample, metric, and observed change. Neither adds causation.
## 2. Hedge stack — CALIBRATE to one uncertainty
### Bad Case
**Request:** Tighten the schedule statement.
**Before:** We may perhaps potentially be able to finish the migration in roughly six to eight weeks, depending on access approval.
**Rewrite:** We estimate six to eight weeks, subject to access approval.
**Why:** The range and dependency are real. Four layers of uncertainty are not.
### Nearest Good Case
**Changed condition:** Six to eight weeks is the current estimate, and work cannot begin before access approval.
**Rewrite:** The estimated migration time is six to eight weeks after access approval.
**Boundary:** Keep the range and prerequisite. Remove only duplicated uncertainty.
## 3. Negative scope — DROP unless it changes ownership
### Bad Case
**Request:** Rewrite the scope paragraph.
**Before:** This proposal is not a comprehensive redesign and does not try to address every support workflow. It covers intake, routing, and escalation.
**Rewrite:** This proposal covers intake, routing, and escalation.
**Why:** Positive scope is enough when no excluded area changes ownership or acceptance.
### Nearest Good Case
**Changed condition:** The contract assigns billing to another team and requires the exclusion to be explicit.
**Rewrite:** This proposal covers intake, routing, and escalation; billing remains out of scope.
**Boundary:** Keep an exclusion that prevents an ownership mistake.
## 4. Diligence narration — DROP unless the method was requested
### Bad Case
**Request:** Make the recommendation direct.
**Before:** We reviewed the available documents and tried to be appropriately cautious. Although we could not verify every possible edge case, we believe the team should start with the two highest-volume queues.
**Rewrite:** Start with the two highest-volume queues.
**Why:** The recommendation is the deliverable. The diligence monologue does not change it.
### Nearest Good Case
**Changed condition:** The reader explicitly asks how to identify the two highest-volume queues.
**Rewrite:** Start with the two highest-volume queues. Rank them by ticket counts from the previous 30 days.
**Boundary:** Keep a requested method because it makes the recommendation executable.
## 5. Hollow claim — audit; do not invent
### Bad Case
**Request:** Audit this sentence: “Our innovative framework creates significant value through a robust, user-centric approach.”
**Audit:** CALIBRATE — The claim supplies no mechanism or measured outcome. Replace it with the actual mechanism and evidence, or remove it.
**Why:** Direct writing cannot repair missing evidence by fabricating specificity.
### Nearest Good Case
**Changed condition:** The source provides both a mechanism and a measured pilot result.
**Rewrite:** Matching request IDs reduced duplicate tickets by 14% in the pilot.
**Boundary:** Use supplied evidence. Do not invent a number or mechanism to make prose sound concrete.
## 6. Causal boundary — KEEP the evidence boundary
### Bad Case
**Request:** Rewrite an observational pilot result without overstating causation.
**Before:** The pilot clearly proves that automatic triage caused completion to improve from 68% to 76%.
**Rewrite:** During the observational pilot, 24-hour completion rose from 68% to 76% after automatic triage was introduced.
**Why:** Removing hedging is not permission to strengthen the evidence.
### Nearest Good Case
**Changed condition:** Requests were randomly assigned, the control group completed 68%, and the automatic-triage group completed 76% under the prespecified analysis.
**Rewrite:** In the randomized comparison, automatic triage increased completion from 68% in the control group to 76%.
**Boundary:** A randomized comparison can support the causal wording that an observational sequence cannot.
## 7. Chinese caption — KEEP the stage, DROP the assurance
### Bad Case
**Request:** Draft a caption for a design-evolution article. Help the reader see the composition and preserve the design stage.
**Material:** An early homepage study has a leaf on the left and an arc on the right. It has not launched. The editor's notes record where the image was found and checked.
**Draft:** 早期首页试样:左侧叶片,右侧圆弧。
**Why:** “早期首页试样” supplies the stage. A separate assurance about image verification or deployment would not help the reader see the composition.
### Nearest Good Case
**Changed condition:** The reader also asks whether the pictured page is live and available to use.
**Draft:** 尚未上线的首页试样:左侧叶片,右侧圆弧。
**Boundary:** Deployment status now answers the reader's question. Keep it beside the subject instead of treating all negative wording as padding.
## 8. Fresh drafting — separate the subject from editorial checks
### Bad Case
**Request:** Turn notes into a short paragraph about column widths and a caption for the type comparison.
**Material:** The contents column is 480px; the reading column is 720px. Chinese and English type are shown together. An editor-only note records that screenshots came from the design archive and were verified there.
**Draft:**
The contents use a 480px column; long-form reading uses 720px.
Chinese and English type set together for comparison.
**Why:** Verification belongs in the editor's working notes here. Do not add a process preface to a new draft and then wait for the reader to ask for its removal.
### Nearest Good Case
**Changed condition:** The same drafting request also asks for the image source in the caption.
**Draft:**
The contents use a 480px column; long-form reading uses 720px.
Chinese and English type set together for comparison. Screenshots are from the design archive.
**Boundary:** Requested attribution stays. The verification monologue still does not help the reader.
**Claim Diff:** Both drafts preserve the two widths and the type comparison. Neither invents a design rationale, a personal reaction, or a published version.
## Already direct
**Before:** The migration will take six to eight weeks after access approval.
**After:** The migration will take six to eight weeks after access approval.
Stop when there is nothing useful to remove.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |