ワンクリックでManusで任意のスキルを実行

始める

stop-slop

スター7

フォーク0

更新日2026年5月29日 17:02

Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

ozzaii

ozzaii/vibemix

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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

このリポジトリの他の Skills

同じリポジトリ

frontend-enforcement

ozzaii/vibemix

Project-local enforcement of vibemix frontend design standards. Loaded automatically by agents that touch frontend code or UI design — Forged Obsidian Chrome (tozpembe) discipline, 20/80 rule, One-Rose, gold quarantine, no AI slop.

2026-06-107

vibemix-grounding-review

ozzaii/vibemix

Reviews any change to what the vibemix co-host SAYS or WHEN it speaks against the 5 cardinal anti-slop invariants. Trigger BEFORE shipping edits to src/vibemix/state/coach.py, src/vibemix/agent/dj_cohost.py, anything under src/vibemix/prompts/ (matrix.py, filter.py, negative_dict.py), src/vibemix/state/event_detector.py, state/refresh.py, state/evidence_registry.py, coach/citation_linter.py, or any reaction/persona/lens/learn-tutor wiring. Also trigger when a PR/plan touches the reaction loop, the citation grammar, EVIDENCE_SOURCES, the slop filter, or the ws bus, OR when Kaan asks "is this grounded / will this slop / does this break an invariant / can we ship this reaction change". Reactions that are scripted, late, hallucinated, or generic are the release blocker — this is the gate.

2026-06-027

drive-vibemix

ozzaii/vibemix

Launch vibemix in dev-source mode and DRIVE the running app to prove a change works LIVE — the perception loop (fire a control, read the logs it produced, confirm the co-host's reaction is grounded, not slop). Trigger when verifying any backend/runtime change actually works in the app (not just green tests), when Kaan asks "does this actually work / show me it working / run it / verify live", when a control or panel looks dead/unresponsive (button does nothing, panel blank, no reaction), when confirming a co-host reaction is grounded vs hallucinated, or when you edited anything under src/vibemix/ (state, agent, runtime/ws_bus, prompts, coach) and need to observe it on the real ws bus. Use BEFORE claiming a runtime fix is done — green unit tests do NOT prove the live app works (frozen sidecar + Tauri runtime hide real failures).

2026-05-317

ipc-wiring-checker

ozzaii/vibemix

Verifies BOTH ends of a vibemix IPC message type are wired — sender on one side, handler/consumer on the other — so a one-ended "dead" type never ships as a silent dead feature. Trigger BEFORE shipping any edit to tauri/ui/src/ipc/messages.schema.json, when adding/removing/renaming an ipc.* message type, when wiring a new control end-to-end (button → emitIpc → register_handler → response), or when hunting a control/panel that looks dead or unresponsive ("button does nothing", "panel stays blank", "no reaction on the wire"). Also trigger when a PR or plan touches the ws_bus, register_handler, emitIpc/sendIpcRequest/subscribeIpc, or the codegen:ipc pipeline.

2026-05-317

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

name	stop-slop
description	Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
metadata	{"trigger":"Writing prose, editing drafts, reviewing content for AI patterns","author":"Hardik Pandya (https://hvpandya.com)"}

name	stop-slop
description	Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
metadata	{"trigger":"Writing prose, editing drafts, reviewing content for AI patterns","author":"Hardik Pandya (https://hvpandya.com)"}