agentleFS
whit3rabbitwhit3rabbit/rabbit-writes/skills/rabbit-rewrites/SKILL.md

rabbit-rewrites

Skill0 starsChanged 2 months agoMITView on GitHub

Rewrite engine-flagged prose using a small local model over an OpenAI-compatible endpoint rather than spending frontier tokens. Use when de-slopping drafts offline, running on llama.cpp, Ollama, or LM Studio, or benchmarking local models against the rewrite gate.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always look for existing settings before prompting or reconfiguring.

    line 29
  2. Very specific:

    Fact preservation: Every candidate must pass verify.py validation (numbers, dates, paths, code spans, quotes, and links must match exactly).

    line 125
  3. Distinctive:

    Will not touch code, tables, headings, or lists: Only prose blocks are processed.

    line 162

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Model-backed rewriting

Detection in this plugin needs no model. scan.py is pure Python and runs on a Pi today. Rewriting is the part that needs one, and this is the path that uses a small local model for it rather than a frontier model.

Paths. ${CLAUDE_PLUGIN_ROOT}/skills/ means the directory holding this skill and its siblings (rabbit-writes, voice-setup, rabbit-readme-improver, rabbit-reads, rabbit-rewrites, rabbit-agents-md). Claude Code expands the variable. On a host that doesn't, such as Codex, resolve it that way by hand.

The design rests on three core principles: targeted chunking, persistent settings reuse, and gated execution.

1. Targeted chunking and context

Rather than sending entire documents (which exceed small model context windows and cause hallucinated edits), the engine chunks flagged prose into focused, contextual units:

  • Sentence units with local context: A tell sitting in a sentence is chunked alongside its preceding sentence context. The model receives the target sentence, the specific problem to remove, and surrounding context to resolve pronoun referents, antecedents, and narrative tone without being asked to rewrite the context itself.
  • Passage and block units: Structural and density tells (uniformity, tier2-cluster, tier3-density) are chunked at the full paragraph level, sized against the endpoint's input budget.
  • Unit merging: Multiple findings landing within the same sentence are merged into a single rewrite unit, preventing colliding edits from invalidating the comparison baseline.

A 10,000-word draft with 40 findings becomes 40 focused 150- to 350-token requests, keeping token budgets tight while giving the model enough context to preserve flow.

2. Settings: Looked at and saved first

Always look for existing settings before prompting or reconfiguring. The engine checks configuration sources in this order:

  1. .rabbit-model in the directory beside the document or the current working directory.
  2. .rabbit-model at the repository root.
  3. Environment variables: $RABBIT_MODEL_BASE_URL, $RABBIT_MODEL_NAME, $RABBIT_MODEL_API_KEY.

Save user configuration to .rabbit-model so settings persist and are automatically reused on every run:

{
  "base_url": "http://127.0.0.1:8080/v1",
  "model": "qwen2.5-3b-instruct",
  "context_tokens": 4096,
  "max_output_tokens": 640,
  "temperature": 0.2,
  "disable_thinking": true
}

For hosted endpoints (e.g. OpenRouter), specify the environment variable holding the key (api_key_env) rather than committing raw keys:

{
  "base_url": "https://openrouter.ai/api/v1",
  "model": "qwen/qwen3-4b-instruct",
  "api_key_env": "OPENROUTER_API_KEY"
}

Shipped presets for the recommended models live in references/presets/. Copy one to the project root as .rabbit-model:

cp skills/rabbit-rewrites/references/presets/deslop-qwen3-4b.json .rabbit-model

A preset may also set system_prompt to override the engine's default prompt. That is useful for narrowly-tuned models whose weights already exclude slop and do not need a long instruction. See references/models.md for the catalog, the caveat boxes, and the download commands.

3. Recommended models and download locations

Small local models (1.5B to 8B parameters) perform reliably when guided by strict prompts and the verification gate. Detailed download sources, commands, and quantization notes live in references/models.md.

Model FamilyRecommended SizesPrimary Download SourceOllama Tag
Qwen 2.5 / 31.5B, 3B, 7BHugging Face (Qwen/Qwen2.5-3B-Instruct-GGUF)qwen2.5:1.5b, qwen2.5:3b, qwen2.5:7b
Gemma 2 / 42B, 9B, 26B (MLX)Hugging Face (google/gemma-2-2b-it-GGUF)gemma2:2b, gemma2:9b, gemma4:26b-mlx
Llama 3.2 / 3.13B, 8BHugging Face (meta-llama/Llama-3.2-3B-Instruct-GGUF)llama3.2:3b, llama3.1:8b

Suggested storage paths

  • Local project directory: ./models/
  • User model cache: ~/.cache/llama.cpp/ or ~/.local/share/models/
  • LM Studio / Ollama cache: ~/.cache/lm-studio/models/ or ~/.ollama/models/

Serving an endpoint

# llama-server
llama-server -m ./models/qwen2.5-3b-instruct-q4_k_m.gguf --port 8080 -c 4096 --flash-attn

# Ollama (endpoint at http://127.0.0.1:11434/v1)
ollama serve

4. System prompt and editing rules

The rewriting system prompt blends plain-language simplification with targeted de-slopping:

You are a copy editor. You rewrite one short passage at a time into clear, natural, and plain language.

Remove these machine-writing characteristics:
- Weird subject and verb combinations, and roundabout pseudo-epiphanies.
- Objects performing action verbs (keep actions for humans, groups, or agents, and avoid phrases like "this file carries..." or "the module names...").
- Self-praise, AI hedges, and conversational padding.
- Distracting beats and unnecessary complexity.

Absolute rules:
- Keep every number, date, name, file path, URL, and quoted phrase exactly as written.
- Keep all markdown unchanged: code spans, links, list markers, headings, and emphasis.
- Leave fenced code blocks completely unchanged.
- Never use an em dash (—).
- Do not add facts, opinions, examples, or a closing summary sentence.
- Do not change the meaning. Say the same thing in plainer, everyday words.
- Reply ONLY with the rewritten passage and nothing else: no preamble, no commentary, no labels, no surrounding quotes, no code fence.

Style presets

  • Default (Plain Language): Everyday vocabulary, active verbs, concise sentences.
  • TLDR: Short summary retaining every key fact, cutting length by half.
  • 5-Year-Old (5y): Maximum simplicity, short conversational phrasing.

Thinking / reasoning tokens: Disabled by default ("disable_thinking": true, sending reasoning_effort: "none" and enable_thinking: false). Reasoning blocks consume the output token budget before the model emits the rewrite.

5. The gating mechanism

A small model is never trusted blindly:

  1. Fact preservation: Every candidate must pass verify.py validation (numbers, dates, paths, code spans, quotes, and links must match exactly).
  2. Rescan validation: A rescan verifies that the flagged tell is gone and no new tells were introduced.
  3. Retry loop: Rejected completions are retried with the rejection reason appended. If all attempts fail, the original text is preserved untouched.

Run it

Deterministic fixes first:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/rabbit-writes/scripts/scan.py draft.md --apply-safe --write

Dry run / plan what would be sent:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/rabbit-writes/scripts/scan.py draft.md --apply-model --model-plan

Apply model rewrites:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/rabbit-writes/scripts/scan.py draft.md --apply-model
python3 ${CLAUDE_PLUGIN_ROOT}/skills/rabbit-writes/scripts/scan.py draft.md --apply-model --write
python3 ${CLAUDE_PLUGIN_ROOT}/skills/rabbit-writes/scripts/scan.py draft.md --apply-model --stdout | diff draft.md -

--model-limit N stops after N passages. --model-attempts N controls retry attempts per passage.

Benchmarking models

Measure actual pass rates using the fixed 12-passage test battery:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/rabbit-rewrites/scripts/bench.py --model-endpoint http://127.0.0.1:8080/v1 --model-name qwen2.5-3b
python3 ${CLAUDE_PLUGIN_ROOT}/skills/rabbit-rewrites/scripts/bench.py --repeat 3 --json > qwen2.5-3b.json

What this will not do

  • Will not match a voice profile: Matching a personal voice fingerprint requires broader context and a capable frontier model. Use rabbit-writes for voice conversion.
  • Will not touch code, tables, headings, or lists: Only prose blocks are processed.
  • Will not alter safety band findings: Any concealed instructions or prompt injections are rejected prior to sending.

Where things live

PathWhat it holds
${CLAUDE_PLUGIN_ROOT}/skills/rabbit-writes/scripts/rwlib/endpoint.pyendpoint configuration, resolution, and security checks
${CLAUDE_PLUGIN_ROOT}/skills/rabbit-writes/scripts/rwlib/rewrite.pyunit planning, prompt templates, gate validation, retry loop
${CLAUDE_PLUGIN_ROOT}/skills/rabbit-rewrites/references/models.mdrecommended models, download sources, and endpoint setup
${CLAUDE_PLUGIN_ROOT}/skills/rabbit-rewrites/scripts/bench.pythe model benchmarking runner
${CLAUDE_PLUGIN_ROOT}/skills/rabbit-rewrites/scripts/battery.jsonthe twelve passages scored in the benchmark

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.