Update to Slop Curator

{
  "description": "Apply a structured human-writing policy to prose when the user wants strict anti-slop constraints, house-style compliance, factual discipline, punctuation controls, banned-language checks, or a final rule-based pass without changing approved meaning.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 317
    },
    {
      "relative_path": "references/house-style.md",
      "size_in_bytes": 4634
    },
    {
      "relative_path": "references/portable-baseline.md",
      "size_in_bytes": 2596
    },
    {
      "relative_path": "references/source-rule-bank.md",
      "size_in_bytes": 46800
    },
    {
      "relative_path": "scripts/strict_human_lint.py",
      "size_in_bytes": 4309
    }
  ],
  "name": "strict-human-output",
  "skill_md_contents": "---\nname: strict-human-output\ndescription: Apply a structured human-writing policy to prose when the user wants strict anti-slop constraints, house-style compliance, factual discipline, punctuation controls, banned-language checks, or a final rule-based pass without changing approved meaning.\n---\n\n# Strict Human Output\n\nUse this Skill as a **policy overlay**, not as a replacement writer. Its job is to enforce explicit output constraints after the content owner has established meaning, evidence, voice, and genre.\n\n## Two profiles\n\n### Portable baseline\n\nUse by default when this Skill is selected. Enforce rules that generalize well across users:\n\n- do not invent facts, numbers, proof, testimonials, sources, rankings, capabilities, scarcity, or urgency\n- remove unsupported importance claims, generic hype, theatrical transitions, and empty adjectives\n- prefer specific actions, concrete nouns, observable behavior, and supported consequences\n- preserve approved names, dates, prices, figures, claims, quotations, terminology, and technical syntax\n- do not restate the brief, add filler introductions, or append generic closing offers\n- follow requested language, dialect, length, format, order, assets, and exact-content constraints\n- when a style rule conflicts with factual or technical accuracy, accuracy wins\n\nRead `references/portable-baseline.md` for the detailed baseline.\n\n### House-style profile\n\nActivate only when the user explicitly requests the strict house style, says to use their personal rules, provides an active style profile with these constraints, or the surrounding task context already establishes them.\n\nThis profile adds hard constraints such as:\n\n- no terminal full stop in normal prose lines\n- no em dash\n- no negative-setup + positive-reveal formulas\n- no \"difference\" formulas or banned house vocabulary\n- no copied AI-sounding Arabic/English expressions\n- reduced quotation marks and decorative punctuation\n- exact response-start and response-end behavior\n\nRead `references/house-style.md` before enforcing this profile.\n\nDo **not** impose the house profile on an unrelated public user merely because the Plugin contains it.\n\n## Conflict order\n\nWhen rules collide, use this order:\n\n1. exact reproduction explicitly requested by the user\n2. factual, legal, technical, numeric, and source fidelity\n3. current user instruction\n4. active brand or house-style profile\n5. genre and audience conventions\n6. generic anti-slop preferences\n\nA lower rule must never silently damage a higher one.\n\n## Workflow\n\n1. Identify which profile is active: `portable` or `house`\n2. Lock facts, exact text, technical syntax, and mandatory content\n3. Scan for hard violations only\n4. Rewrite the smallest necessary region rather than normalizing the whole piece\n5. Recheck natural reading after every hard-rule repair\n6. Hand residual voice or rhythm problems back to the relevant writing Skill\n7. Run `slop-quality-gate` after enforcement when this Skill is part of a routed workflow\n\n## Do not overcorrect\n\nA strict style policy can itself create mechanical prose. Do not:\n\n- remove natural uncertainty merely because it looks less decisive\n- flatten dialect or code-switching\n- replace every adjective with a long explanation\n- force active voice when passive voice is clearer or the actor is genuinely unknown\n- remove punctuation required for code, URLs, email addresses, decimals, versions, file names, citations, or exact quotations\n- manufacture slang to compensate for formal prose\n\n## Deterministic lint\n\nWhen the host can run Python and the strict house profile is active, `scripts/strict_human_lint.py` can mechanically check terminal periods, em dashes, selected banned vocabulary, selected AI-expression families, and negative-setup formulas. Treat its findings as candidate violations to repair in context. It does not judge voice, factual accuracy, persuasion quality, or whether a phrase is quoted/required.\n\n## Completion condition\n\nThe output is complete when every active hard rule passes **and** the text still preserves the intended meaning, evidence, voice, genre, and technical correctness.\n"
}