Open with why AI text sounds the way it does: the default choice that fits
the widest range of cases. Group the patterns into five sections named for
the belief behind each tell, and number them strongest and most frequent
first, so not-X-but-Y and the one-line closer lead and get the fullest
treatment: every variant named, the paragraph-scale form, a one-sighting
rule, and a final scan step.
Consolidate 35 patterns into 25 with nothing dropped. Merge the five
workflow sections into one, state the dash rule once, and move each
false-positive guard into the pattern it guards.
Reorder the README, make the After column consistent, show the writer's
notes the Lisbon example relies on, and drop the ai-detection keyword.
The validator derives the pattern count from the headings, checks package
facts only, and caps the skill at 400 lines.
- Missing or unreadable package files exit with a plain-language
message instead of a traceback, per the AGENTS.md style rule;
malformed plugin.json does the same.
- metadata.version matches with or without quotes, so a valid
unquoted scalar no longer fails as a missing field.
- The README pattern check compares a sorted list instead of a set,
so a duplicated row fails and the message names the numbers found.
- AGENTS.md Key files now lists agents/openai.yaml, the one tracked
file no doc or check mentioned.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
