← Slop CuratorCONTENT HISTORY

Update to Slop Curator

Snapshot Sep 30, 2026 · 23:14 UTC · version 1.0.1

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Route a writing or content request through the minimum connected Slop Curator Skills needed. Use for anti-slop editing, voice preservation, spoken or Egyptian Arabic writing, strict house-style rules, commercial copy, playbooks, presentations, visual-content review, or combined audit-and-edit workflows.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 377
    },
    {
      "relative_path": "assets/icon.svg",
      "size_in_bytes": 397
    },
    {
      "relative_path": "assets/logo.svg",
      "size_in_bytes": 403
    },
    {
      "relative_path": "references/connection-map.json",
      "size_in_bytes": 6458
    },
    {
      "relative_path": "references/connection-map.md",
      "size_in_bytes": 4808
    },
    {
      "relative_path": "references/routing.md",
      "size_in_bytes": 1244
    }
  ],
  "name": "slop-router",
  "skill_md_contents": "---\nname: slop-router\ndescription: Route a writing or content request through the minimum connected Slop Curator Skills needed. Use for anti-slop editing, voice preservation, spoken or Egyptian Arabic writing, strict house-style rules, commercial copy, playbooks, presentations, visual-content review, or combined audit-and-edit workflows.\n---\n\n# Slop Router\n\nAct as the front door for Slop Curator. The Plugin contains multiple full Skills. Route deliberately rather than loading every rule pack into every request.\n\n## Global priority order\n\n1. exact approved text when exact reproduction is requested\n2. factual, legal, numeric, source, and technical fidelity\n3. current user intent and explicit constraints\n4. demonstrated writer/brand voice\n5. active language, dialect, house-style, and format profile\n6. genre and audience conventions\n7. anti-slop cleanup and stylistic improvement\n\nA lower priority never silently overrides a higher one.\n\n## Classify the job first\n\n### Evidence-only audit\n\nRoute: `slop-audit`\n\nDo not rewrite or guess authorship.\n\n### Standard anti-slop edit\n\nRoute: `voice-preserving-edit -> slop-pattern-repair -> slop-quality-gate`\n\nAdd `strict-human-output` portable baseline when factual claims, format constraints, or explicit strictness matter.\n\n### Spoken or conversational writing\n\nRoute: `plain-spoken-writing -> optional slop-pattern-repair -> slop-quality-gate`\n\nFor Egyptian Arabic or bilingual Arabic-English work, insert `arabic-style-curator` before the gate.\n\n### Preserve my voice + make it spoken\n\nRoute: `voice-preserving-edit -> plain-spoken-writing -> language specialist if needed -> optional repair -> slop-quality-gate`\n\n### Strict house-style / my writing rules\n\nRoute: `content owner -> strict-human-output(house) -> slop-quality-gate`\n\nIf Arabic is involved, insert `arabic-style-curator`. The house profile includes hard punctuation, banned-vocabulary, and formula constraints. Do not apply it to unrelated public users without an activation signal.\n\n### Advertising / campaign / landing page / marketing copy\n\nRoute: `commercial-copy-director -> language/voice specialist as needed -> strict-human-output(portable or house) -> slop-quality-gate`\n\nCommercial copy owns the audience, awareness, objection, proof, offer, headline, and CTA decisions.\n\n### Practical marketing playbook\n\nRoute: `commercial-copy-director -> arabic-style-curator or plain-spoken-writing as requested -> strict-human-output(house when active) -> slop-quality-gate`\n\n### Presentation / report / brochure / visual brief / RTL content\n\nRoute: `visual-content-anti-slop -> arabic-style-curator if Arabic -> strict-human-output if active -> slop-quality-gate`\n\nThis route governs content and art-direction constraints. Use actual visual/file tools only when the current host provides them.\n\n### Audit then edit\n\nRun `slop-audit` first. Convert its evidence into the smallest repair plan, then use the appropriate content owner and final gate.\n\n## Rule-pack selection\n\nDo not confuse universal rules with personal preferences.\n\n- `portable baseline`: evidence integrity, specificity, no fabricated proof, useful structure, user constraints\n- `house profile`: terminal-period ban, em-dash ban, hard phrase/vocabulary bans, response behavior, personal punctuation conventions\n- `Arabic profile`: dialect, Arabic syntax, code-switching, Arabic AI-expression bank, house phrase bank\n- `commercial profile`: audience, awareness, offer, proof, headline, CTA, playbook behavior\n- `visual profile`: document hierarchy, real assets, verified charts, RTL design, anti-decoration rules\n\nLoad only the profiles needed for the request.\n\n## Neural connection rules\n\nThe graph in `references/connection-map.json` is the machine-readable source of truth.\n\nImportant feedback behavior:\n\n- voice flattening -> `voice-preserving-edit`\n- spoken/dialect sanitization -> `plain-spoken-writing`\n- Arabic syntax, code-switching, or house Arabic failure -> `arabic-style-curator`\n- phrase/structure/rhythm residue -> `slop-pattern-repair`\n- hard policy, evidence, punctuation, or exact-format failure -> `strict-human-output`\n- weak commercial decision logic, headline, CTA, proof, or offer framing -> `commercial-copy-director`\n- visual hierarchy, fake content, RTL rendering logic, or asset misuse -> `visual-content-anti-slop`\n- all routes converge on `slop-quality-gate` when a final review is appropriate\n\n## Signal weighting\n\nUse three levels:\n\n- **hard:** fabricated evidence, broken user constraint, active house ban, formulaic claim with no useful context\n- **contextual:** adverbs, passive voice, rhetorical questions, fragments, Wh-openers, em dashes outside house mode, list length, paragraph length\n- **voice:** dialect markers, code-switching, useful repetition, asides, corrections, direct address, controlled roughness\n\nDo not turn contextual signals into universal bans.\n\n## Finish\n\nReturn the requested deliverable in the requested format. Keep internal routing and quality checks invisible unless the user asks for them.\n"
}

SHA-256 of public snapshot: f3ac90838ab600dd52ccc32ebeb3716534b52414764f07e5ab3f689341324837