Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

stop-slop停止斜坡

Agent Skill

stop-slop 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

541

周安装

23

GitHub Stars

10

下载量

190
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:stop-slop(停止斜坡)
来源仓库:https://github.com/boraoztunc/skills
仓库路径:skills/stop-slop
安装命令:
npx skills add https://github.com/boraoztunc/skills --skill stop-slop
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/boraoztunc/skills --skill stop-slop

简介

stop-slop 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景快速定位候选结果。
  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • stop-slop 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Stop Slop

Eliminate predictable AI writing patterns from prose.

Core Rules

  1. Cut filler phrases. Remove throat-clearing openers, emphasis crutches, and all adverbs. See Phrases to Remove below.
  2. Break formulaic structures. Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See Structures to Avoid below.
  3. Use active voice. Every sentence needs a human subject doing something. No passive constructions. No inanimate objects performing human actions ("the complaint becomes a fix").
  4. Be specific. No vague declaratives ("The reasons are structural"). Name the specific thing. No lazy extremes ("every," "always," "never") doing vague work.
  5. Put the reader in the room. No narrator-from-a-distance voice. "You" beats "People." Specifics beat abstractions.
  6. Vary rhythm. Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes.
  7. Trust readers. State facts directly. Skip softening, justification, hand-holding.
  8. Cut quotables. If it sounds like a pull-quote, rewrite it.

Quick Checks

Before delivering prose:

  • Any adverbs? Kill them.
  • Any passive voice? Find the actor, make them the subject.
  • Inanimate thing doing a human verb ("the decision emerges")? Name the person.
  • Sentence starts with a Wh- word? Restructure it.
  • Any "here's what/this/that" throat-clearing? Cut to the point.
  • Any "not X, it's Y" contrasts? State Y directly.
  • Three consecutive sentences match length? Break one.
  • Paragraph ends with punchy one-liner? Vary it.
  • Em-dash anywhere? Remove it.
  • Vague declarative ("The implications are significant")? Name the specific implication.
  • Narrator-from-a-distance ("Nobody designed this")? Put the reader in the scene.
  • Meta-joiners ("The rest of this essay...")? Delete. Let the essay move.

Scoring

Rate 1-10 on each dimension:

DimensionQuestion
DirectnessStatements or announcements?
RhythmVaried or metronomic?
TrustRespects reader intelligence?
AuthenticitySounds human?
DensityAnything cuttable?

Below 35/50: revise.


Phrases to Remove

Throat-Clearing Openers

Remove these announcement phrases. State the content directly.

  • "Here's the thing:"
  • "Here's what [X]"
  • "Here's this [X]"
  • "Here's that [X]"
  • "Here's why [X]"
  • "The uncomfortable truth is"
  • "It turns out"
  • "The real [X] is"
  • "Let me be clear"
  • "The truth is,"
  • "I'll say it again:"
  • "I'm going to be honest"
  • "Can we talk about"
  • "Here's what I find interesting"
  • "Here's the problem though"

Any "here's what/this/that" construction is throat-clearing before the point. Cut it and state the point.

Emphasis Crutches

These add no meaning. Delete them.

  • "Full stop." / "Period."
  • "Let that sink in."
  • "This matters because"
  • "Make no mistake"
  • "Here's why that matters"

Business Jargon

Replace with plain language.

AvoidUse instead
Navigate (challenges)Handle, address
Unpack (analysis)Explain, examine
Lean intoAccept, embrace
Landscape (context)Situation, field
Game-changerSignificant, important
Double downCommit, increase
Deep diveAnalysis, examination
Take a step backReconsider
Moving forwardNext, from now
Circle backReturn to, revisit
On the same pageAligned, agreed

Adverbs

Kill all adverbs. No -ly words. No softeners, no intensifiers, no hedges.

Specific offenders:

  • "really"
  • "just"
  • "literally"
  • "genuinely"
  • "honestly"
  • "simply"
  • "actually"
  • "deeply"
  • "truly"
  • "fundamentally"
  • "inherently"
  • "inevitably"
  • "interestingly"
  • "importantly"
  • "crucially"

Also cut these filler phrases:

  • "At its core"
  • "In today's [X]"
  • "It's worth noting"
  • "At the end of the day"
  • "When it comes to"
  • "In a world where"
  • "The reality is"

Meta-Commentary

Remove self-referential asides. The essay should move, not announce its own structure.

  • "Hint:"
  • "Plot twist:" / "Spoiler:"
  • "You already know this, but"
  • "But that's another post"
  • "X is a feature, not a bug"
  • "Dressed up as"
  • "The rest of this essay explains..."
  • "Let me walk you through..."
  • "In this section, we'll..."
  • "As we'll see..."
  • "I want to explore..."

Performative Emphasis

False intimacy or manufactured sincerity:

  • "creeps in"
  • "I promise"
  • "They exist, I promise"

Telling Instead of Showing

Announcing difficulty or significance rather than demonstrating it:

  • "This is genuinely hard"
  • "This is what leadership actually looks like"
  • "This is what X actually looks like"
  • "actually matters"

Vague Declaratives

Sentences that announce importance without naming the specific thing. Kill these.

  • "The reasons are structural"
  • "The implications are significant"
  • "This is the deepest problem"
  • "The stakes are high"
  • "The consequences are real"

If a sentence says something is important/deep/structural without showing the specific thing, cut it or replace it with the specific thing.


Structures to Avoid

Binary Contrasts

These create false drama. State the point directly.

PatternProblem
"Not because X. Because Y." / "Not because X, but because Y."Telegraphed reversal
"[X] isn't the problem. [Y] is."Formulaic reframe
"The answer isn't X. It's Y."Predictable pivot
"It feels like X. It's actually Y."Setup/reveal cliche
"The question isn't X. It's Y."Rhetorical misdirection
"Not X. But Y." / "not X, it's Y" / "isn't X, it's Y"Mechanical contrast
"It's not this. It's that."Same formula, different words
"stops being X and starts being Y"False transformation arc
"doesn't mean X, but actually Y"Negation-then-assertion crutch
"is about X but not Y"False distinction
"not just X but also Y"Additive hedge

Instead: State Y directly. "The problem is Y." "Y matters here." Drop the negation entirely.

Negative Listing

Listing what something is *not* before revealing what it *is*. A rhetorical striptease.

PatternProblem
"Not a X... Not a Y... A Z."Dramatic buildup through negation
"It wasn't X. It wasn't Y. It was Z."Same structure, past tense

Instead: State Z. The reader doesn't need the runway.

Dramatic Fragmentation

Sentence fragments for emphasis read as manufactured profundity.

PatternProblem
"[Noun]. That's it. That's the [thing]."Performative simplicity
"X. And Y. And Z."Staccato drama
"This unlocks something. [Word]."Artificial revelation

Instead: Complete sentences. Trust content over presentation.

Rhetorical Setups

These announce insight rather than deliver it.

PatternProblem
"What if [reframe]?"Socratic posturing
"Here's what I mean:"Redundant preview
"Think about it:"Condescending prompt
"And that's okay."Unnecessary permission

Instead: Make the point. Let readers draw conclusions.

Formulaic Constructions

PatternProblem
"By the time X, I was Y."Narrative template
"X that isn't Y"Indirect. Say "X is broken"

False Agency

Giving inanimate things human verbs. Complaints don't "become" fixes. Bets don't "live or die." Decisions don't "emerge." A person does something to make those things happen. AI loves this because it avoids naming the actor.

PatternProblem
"a complaint becomes a fix"The complaint did nothing. Someone fixed it.
"a bet lives or dies in days"Bets don't have lifespans. Someone kills the project or ships it.
"the decision emerges"Decisions don't emerge. Someone decides.
"the culture shifts"Cultures don't shift on their own. People change behavior.
"the conversation moves toward"Conversations don't move. Someone steers.
"the data tells us"Data sits there. Someone reads it and draws a conclusion.
"the market rewards"Markets don't reward. Buyers pay for things.

Instead: Name the human. "The team fixed it that week" beats "the complaint becomes a fix." If no specific person fits, use "you" to put the reader in the seat.

Narrator-from-a-Distance

Floating above the scene instead of putting the reader in it.

PatternProblem
"Nobody designed this."Disembodied observation
"This happens because..."Lecturer voice
"This is why..."Same
"People tend to..."Armchair sociologist

Instead: Put the reader in the room. "You don't sit down one day and decide to..." beats "Nobody designed this."

Passive Voice

Every sentence needs a subject doing something. Passive voice hides the actor and drains energy.

PatternFix
"X was created"Name who created it
"It is believed that"Name who believes it
"Mistakes were made"Name who made them
"The decision was reached"Name who decided

Instead: Find the actor. Put them at the front of the sentence.

Sentence Starters to Avoid

PatternFix
Sentences starting with What, When, Where, Which, Who, Why, HowRestructure. Lead with the subject or the verb.
Paragraphs starting with "So"Start with content
Sentences starting with "Look,"Remove

Wh- openers become a crutch. "What makes this hard is..." becomes "The constraint is..." or better, name the specific constraint.

Rhythm Patterns

PatternFix
Three-item listsUse two items or one
Questions answered immediatelyLet questions breathe or cut them
Every paragraph ends punchilyVary endings
Em-dashesRemove. Use commas or periods. No em dashes at all.
Staccato fragmentationDon't stack short punchy sentences
"Not always. Not perfectly."Hedging disguised as reassurance

Word Patterns

PatternProblem
Lazy extremes (every, always, never, everyone, everybody, nobody)False authority. Use specifics instead of sweeping claims.
All adverbs (-ly words, "really," "just," "literally," "genuinely," "honestly," "simply," "actually")Empty emphasis. See Adverbs section above.

Examples

Example 1: Throat-Clearing + Binary Contrast

Before:

"Here's the thing: building products is hard. Not because the technology is complex. Because people are complex. Let that sink in."

After:

"Building products is hard. Technology is manageable. People aren't."

Changes: Removed opener, binary contrast structure, and emphasis crutch. Direct statements.


Example 2: Filler + Unnecessary Reassurance

Before:

"It turns out that most teams struggle with alignment. The uncomfortable truth is that nobody wants to admit they're confused. And that's okay."

After:

"Teams struggle with alignment. Nobody admits confusion."

Changes: Cut hedging ("most"), removed throat-clearing phrases, deleted permission-granting ending.


Example 3: Business Jargon Stack

Before:

"In today's fast-paced landscape, we need to lean into discomfort and navigate uncertainty with clarity. This matters because your competition isn't waiting."

After:

"Move faster. Your competition is."

Changes: Eliminated jargon entirely. Core message in six words.


Example 4: Dramatic Fragmentation

Before:

"Speed. Quality. Cost. You can only pick two. That's it. That's the tradeoff."

After:

"Speed, quality, cost—pick two."

Changes: Single sentence. No performative emphasis.


Example 5: Rhetorical Setup

Before:

"What if I told you that the best teams don't optimize for productivity? Here's what I mean: they optimize for learning. Think about it."

After:

"The best teams optimize for learning, not productivity."

Changes: Direct claim. No rhetorical scaffolding.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.42%
按下载量换算73

Claude

28.08%
按下载量换算53

Cursor

18.29%
按下载量换算35

Gemini CLI

10.34%
按下载量换算20

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills