stop-slop

Writing Community

Repo stars 7,725
Author repo stop-slop

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells. Eliminat…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Core Rules”, “Quick Checks”, “Scoring”, “Examples”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name stop-slop directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Core Rules / Quick Checks / Scoring” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Stop Slop

Eliminate predictable AI writing patterns from prose.

Core Rules

Cut filler phrases. Remove throat-clearing openers, emphasis crutches, and all adverbs. See references/phrases.md.
Break formulaic structures. Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See references/structures.md.
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").
Be specific. No vague declaratives ("The reasons are structural"). Name the specific thing. No lazy extremes ("every," "always," "never") doing vague work.
Put the reader in the room. No narrator-from-a-distance voice. "You" beats "People." Specifics beat abstractions.
Vary rhythm. Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes.
Trust readers. State facts directly. Skip softening, justification, hand-holding.
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:

Dimension	Question
Directness	Statements or announcements?
Rhythm	Varied or metronomic?
Trust	Respects reader intelligence?
Authenticity	Sounds human?
Density	Anything cuttable?

Below 35/50: revise.

Examples

See references/examples.md for before/after transformations.

License

MIT

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Writing
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @hardikpandya · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview stop-slop.preview

The current SKILL.md does not define a fixed output example.

SKILL.md 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 [references/phrases.md](references/phrases.md).

2. **Break formulaic structures.** Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See [references/structures.md](references/structures.md).

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.

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Core Rules → Quick Checks → Scoring → Examples → License
terms    -> Cut filler phrases. · Break formulaic structures. · Use active voice. · Be specific. · Put the reader in the room. · Vary rhythm. · Trust readers. · Cut quotables.
files/cmd -> references/phrases.md · references/structures.md · what/this/that · 35/50 · references/examples.md · before/after
body sha256 -> cb5dfe60e266