[christso]

The write-naturally skill now uses straight apostrophes and spaced hyphens for dashes, including when proofreading a draft that already contains typographic punctuation. Its own prose and technical design reference follow the apostrophe rule.

Two fictional proofreading cases check that plain punctuation survives spelling fixes and that curly apostrophes and an em dash become keyboard punctuation. They use deterministic not-regex and equals assertions plus a skill-use check, with the default model graders disabled. The exact-message check also rejects missing hyphen spacing, unchanged typos, empty output and added commentary. The README documents the focused command.

Validation:

• bun run validate passed.
• bun test passed (58 tests).
• bun run eval:validate passed.
• git diff --check passed.
• Assertion calibration through Promptfoo's real assertion API: 16 controls passed (2 correct outputs accepted, 14 deliberately incorrect outputs rejected).
• bun run eval:write-naturally --filter-metadata group=punctuation --max-concurrency 2 --no-progress-bar -o /tmp/write-naturally-punctuation-20261028-rerun.json: 2 passed, 0 failed, 0 errors, using Promptfoo 0.124.1 and gpt-6.1-sol with medium reasoning. Both traces recorded the repository-local skill read. No model grader was used.

The focused live run covers the two new cases; the full 30-case model eval suite was not run. Local results: /tmp/write-naturally-punctuation-20261028-rerun.json.