← Slop CuratorCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Slop Curator
Snapshot Sep 30, 2026 · 23:14 UTC · version 1.0.1
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Edit a draft while protecting the writer's meaning, facts, cadence, vocabulary, humor, bluntness, uncertainty, and useful imperfections. Use when preserving personal voice matters more than making every sentence uniformly polished.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 309
},
{
"relative_path": "references/voice-veto.md",
"size_in_bytes": 652
}
],
"name": "voice-preserving-edit",
"skill_md_contents": "---\nname: voice-preserving-edit\ndescription: Edit a draft while protecting the writer's meaning, facts, cadence, vocabulary, humor, bluntness, uncertainty, and useful imperfections. Use when preserving personal voice matters more than making every sentence uniformly polished.\n---\n\n# Voice-Preserving Edit\n\nOwn meaning and voice. Anti-slop cleanup is subordinate to these two responsibilities.\n\n## Before editing\n\nBuild a private `voice fingerprint` from the draft:\n\n- vocabulary level and favorite kinds of words\n- sentence length range and cadence\n- directness versus digression\n- humor, bluntness, warmth, skepticism, or formality\n- use of fragments, asides, repetition, slang, profanity, or uncertainty\n\nAlso lock anything the edit must not silently change:\n\n- names\n- numbers and dates\n- quotes\n- claims and evidence\n- product or technical terminology\n- instructions, legal wording, or operational constraints\n\n## Editing contract\n\n1. Make the minimum effective change for the user's requested intensity.\n2. Leave strong human sentences alone even if another version could sound cleaner.\n3. Cut filler when it adds no context, character, or meaning.\n4. Make vague claims more concrete only from information already present. Never manufacture specificity.\n5. Prefer direct verbs and named actors when that improves clarity, but do not force every sentence into actor-first syntax.\n6. Preserve useful roughness. A draft does not need uniform paragraph length, identical polish, or perfect symmetry.\n7. Keep uncertainty when the writer is genuinely uncertain.\n8. Keep genre-appropriate rhetorical devices when they have a job.\n9. Reorganize only when the current order hides the point or makes the piece hard to follow.\n10. If a proposed cleanup erases a voice marker, either keep the original or find a smaller fix.\n\n## Handoff to Plain-Spoken Writing\n\nWhen the user explicitly wants the result to sound spoken, conversational, Egyptian Arabic, or like something they would say aloud, keep ownership of factual locks and the voice fingerprint, then hand those anchors to `plain-spoken-writing`. Do not independently formalize or compress the draft before that handoff.\n\n## Intensity\n\n### Light\nCorrect obvious slop, repetition, and confusion. Preserve structure and most wording.\n\n### Standard\nRewrite weak sentences, remove recurring formulas, and improve structure where needed while keeping the recognizable writer.\n\n### Strong\nAllow paragraph and section reconstruction. Keep factual locks and reintroduce the writer's vocabulary, pace, and edge before finishing.\n\n## Output\n\nReturn the full edited draft. Unless the user requests copy only, add a short `What changed` section focused on substantive decisions, not a line-by-line change log.\n"
}SHA-256 of public snapshot: d63312ec9c973731d9950c692c9bc57dedfeba0448e469dea6f9b49de723570c