Slopgent

Slopkit

Two anti-slop skills for coding agents, installed by the same means.

• slopbeth cleans the writing you ship. It rewrites and reviews an artifact, cutting AI tells without changing what the draft can honestly claim.
• slopgent cleans the conversation. It shapes the agent's own replies so they stay honest about what actually ran, action-first, and plain.

They are separate skills. Install both (the default), or remove either one and keep the other. The split is deliberate: point slopgent at a document and you get the clipped formula prose slopbeth exists to remove; ask slopbeth to narrate a build and it has nothing to preserve.

	slopbeth	slopgent
Governs	the text you hand over to edit or publish	the agent's own status reports, explanations, and "done" claims
Optimizes for	sourced, dense, unsummarizable prose in your voice	honesty first, then structure, then plain language
Runtime	Node + Python, with a PowerShell 7 twin	Python (Node for the memory helper)
Full docs	skills/slopbeth/README.md	skills/slopgent/README.md

[!TIP] Not sure which you need? slopbeth edits a document you hand over. slopgent shapes what the agent tells you while it works. Most people want both. The default install adds them as siblings, and deleting either directory leaves the other working.

why

An agent produces two kinds of text, and both drift toward slop in their own way.

• The artifacts it writes for you (the README, the postmortem, the release note) fill with unsupported claims, brand-lesson closers, and sentences that read clean but say nothing. slopbeth cuts that without dropping a single sourced fact.
• The things it says to you ("Fixed the auth bug," "everything should work now") overstate what actually ran and bury the one command you need. slopgent keeps the agent honest about what it verified and leads with the action.

Neither is a "be concise" directive. Concise-only rules cut the filler and the load-bearing caveat with equal enthusiasm. Both skills cut the filler and keep the caveat.

install

Install both skills into supported agent skill directories:

npx github:ehmo/slopkit install

That installs slopbeth and slopgent for whichever of Codex, Claude Code, Hermes, OpenClaw, OpenCode, and Pi already exist under your home. Agents you do not use are skipped. Add --all (or the installnpx alias) to install into every supported agent whether or not its directory exists yet:

npx github:ehmo/slopkit install --all
npx github:ehmo/slopkit installnpx

Both skills land as sibling subdirectories, skills/slopbeth and skills/slopgent, under each agent's skills/ directory.

as Claude Code and Codex plugins

npx github:ehmo/slopkit install-plugin          # both skills, both agents
npx github:ehmo/slopkit install-plugin claude   # Claude only
npx github:ehmo/slopkit install-plugin codex    # Codex only

The Claude plugins install as skills-directory plugins. The Codex plugins install under ~/.codex/plugins/<skill> and register in ~/.agents/plugins/marketplace.json, one marketplace entry per skill.

Marketplace install:

# Claude Code
/plugin marketplace add ehmo/slopkit
/plugin install slopbeth@slopkit
/plugin install slopgent@slopkit

# Codex CLI
codex plugin marketplace add ehmo/slopkit
# then open /plugins and install Slopbeth + Slopgent from the Slopkit marketplace

other paths

Install into a specific directory (both skills land under it):

npx github:ehmo/slopkit install /path/to/skills

Via the external Skills CLI, request all agents explicitly (without --all it may install only for the detected current agent):

npx skills@latest add ehmo/slopkit --all --copy

From a clone:

git clone [email protected]:ehmo/slopkit.git
cd slopkit
node bin/slopkit.js install

PowerShell edition (no Node or Python required for slopbeth)