本文へ移動
cccskills
無料GitHub で公開

stop-slop

Prose final-pass editor for GitHub issue bodies, pull request bodies, release notes, README/docs changes, public comments, and user-facing explanations. Use when Codex drafts or revises substantial prose that will be published or committed, especially when the user asks to polish, de-slop, make it less AI-written, improve a PR/issue body, or prepare docs text; do not use for ordinary code implementation, debugging transcripts, logs, quoted text, command output, API names, or Chinese conversational replies unless explicitly requested.

インストール方法を見る

含まれるファイル(6)

  • SKILL.md2.0 KB
  • agents/openai.yaml248 B
  • LICENSE1.0 KB
  • references/examples.md1.6 KB
  • references/phrases.md2.8 KB
  • references/structures.md5.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Stop Slop

Use this skill as a final prose pass, after technical facts are correct.

Workflow

  1. Preserve facts, scope, and intent.
  2. Leave code blocks, commands, logs, stack traces, quoted source text, identifiers, API names, filenames, branch names, commit messages, and test names unchanged unless the user explicitly asks to rewrite them.
  3. For English prose, remove formulaic AI phrasing, throat-clearing, empty emphasis, stock transitions, fake symmetry, inflated claims, and punchline endings.
  4. Prefer concrete nouns, direct verbs, and specific consequences over vague summaries.
  5. Keep useful technical caution. Do not remove uncertainty, caveats, or passive voice when they make the engineering claim more accurate.
  6. Keep the output in the user's requested language and tone. For Chinese output, use the reference files only as a smell list, not as English style rules.
  7. If a reference detail is needed, read only the relevant file:
    • references/phrases.md for filler phrases and stock wording.
    • references/structures.md for formulaic paragraph and sentence shapes.
    • references/examples.md for before/after patterns.

Output Rules

  • Return the revised text, not a scoring report, unless asked.
  • Mention material factual changes separately if any were unavoidable.
  • Keep Markdown structure valid and preserve links.
  • Do not make the prose more combative or marketing-like.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

adhx

無料

Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.

日本語の概要は準備中です。原文の説明を表示しています。

bioinformatist/codex-base82026年10月10日 更新

Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.

日本語の概要は準備中です。原文の説明を表示しています。

bioinformatist/codex-base82026年10月10日 更新

Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.

日本語の概要は準備中です。原文の説明を表示しています。

bioinformatist/codex-base82026年10月10日 更新

Route requests for current library, framework, SDK, API, CLI, or cloud-service documentation through available documentation tools and primary sources.

日本語の概要は準備中です。原文の説明を表示しています。

bioinformatist/codex-base82026年10月10日 更新

Build and sharpen a project's domain model. Use only when actively changing glossary or ubiquitous-language terms, or recording a durable architectural decision; merely reading a glossary is not a trigger.

日本語の概要は準備中です。原文の説明を表示しています。

bioinformatist/codex-base82026年10月10日 更新

grilling

無料

Explicit-only interview loop for stress-testing a plan, decision, or idea. Use only when the user asks to grill, interrogate, interview, or stress-test their thinking before action.

日本語の概要は準備中です。原文の説明を表示しています。

bioinformatist/codex-base82026年10月10日 更新

bioinformatist のスキルをすべて見る

このスキルの問題を報告する