What problem does it solve? Agent-drafted prose often carries AI slop, fabricated specifics, vague claims, and formulaic structure. This Skill provides a shared quality layer for any human-facing text — docs, PR descriptions, issues, specs, release notes, announcements — by routing each draft to the correct scenario writing skill and enforcing non-negotiable rules before delivery. ## Core Features & Use Cases - Scenario routing: Maps the artifact type to exactly one scenario skill (github-writing, writing-docs, writing-spec, writing-community, writing-marketing) with explicit edge-case rules. - Mandatory quality gate: Runs scripts/writingcheck.py on every draft, combining Vale lexical rules (Slop, Google, Marketing styles) with structural checks for single-bullet lists, closing summaries, thin sections, and unattributed statistics. - Composition pipeline: Sequences base drafting, optional persuasion pass, and author-voice overlay as distinct edits with defined precedence rules. - Use Case: When asked to write a README or PR description, the agent routes to the matching scenario skill, drafts with BLUF structure, runs the revision pass from references/, and gates the result through writingcheck.py before presenting it. ## Quick Start Ask the agent to write a PR description or README and have it route through writing-core, then run writingcheck.py on the draft before delivering it.