From db1d3a3e4124b785a4e30b184a5f35cd752194a3 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Mon, 16 Nov 2026 01:36:50 -0500 Subject: [PATCH] fix(playbooks): say style example pairs show their input, not a Bad/Good contrast The structured-output rule in skill-authoring's skill-criteria.md asked for labeled input/output pairs, but every failing Sonnet run of the skill-authoring-style-output-labeled-pairs case printed a Bad:/Good: pair of two titles with no input, the shape of the file's own worked example for another rule. The rule now says each pair shows the input beside the output, labeled apart, and that a Bad:/Good: contrast of two outputs is not such a pair. Refs: #16323 Co-Authored-By: Claude Fable 5.2 --- .../fix-16323-skill-authoring-labeled-pairs-a7a6b6e4.md | 7 +++++++ .../skills/skill-authoring/reference/skill-criteria.md | 5 ++++- 2 files changed, 11 insertions(+), 1 deletion(-) create mode 100644 .changes/playbooks/fix-16323-skill-authoring-labeled-pairs-a7a6b6e4.md diff --git a/.changes/playbooks/fix-16323-skill-authoring-labeled-pairs-a7a6b6e4.md b/.changes/playbooks/fix-16323-skill-authoring-labeled-pairs-a7a6b6e4.md new file mode 100644 index 0000000000..4528702c03 --- /dev/null +++ b/.changes/playbooks/fix-16323-skill-authoring-labeled-pairs-a7a6b6e4.md @@ -0,0 +1,7 @@ +--- +bump: patch +--- + +### Fixed + +- skill-authoring's structured-output rule now says each style example pair shows the input it came from beside the output, labeled apart, and that a `Bad:`/`Good:` contrast of two outputs is not such a pair. diff --git a/plugins/playbooks/skills/skill-authoring/reference/skill-criteria.md b/plugins/playbooks/skills/skill-authoring/reference/skill-criteria.md index 6b9223051b..946bfdfa10 100644 --- a/plugins/playbooks/skills/skill-authoring/reference/skill-criteria.md +++ b/plugins/playbooks/skills/skill-authoring/reference/skill-criteria.md @@ -162,7 +162,10 @@ except the pointer swap that **Cutting text** exempts ([Measurement](#measuremen machine-read output, a default with a release line otherwise. Give a few diverse, canonical examples that portray the expected behavior, not a laundry list of edge cases that tries to state every possible rule; where style matters, make them labeled input/output pairs and add a - line naming the rule. Name a default tool, and an escape hatch + line naming the rule. Each pair shows the input the skill is given (a described change, a + request) and the output it should produce from it, labeled apart, as in `Input:`/`Output:`. + A `Bad:`/`Good:` contrast of two outputs is not such a pair, because it never shows which + input calls for the good output. Name a default tool, and an escape hatch only with its trigger. - Deterministic work goes in a bundled script. SKILL.md cites it as `${CLAUDE_SKILL_DIR}/scripts/` with the verb ("Run" to execute, "See" to read), forward