fix: quote SKILL.md description values containing colons

[ds1ter]

Problem

8 SKILL.md files have description frontmatter values containing : (colon + space), which strict YAML parsers interpret as a new mapping key — causing this error:

invalid YAML: mapping values are not allowed in this context

Affected skills: design-html, design-consultation, design-review, design-shotgun, guard, plan-tune, setup-gbrain, ship

This breaks any tool that uses a strict YAML parser to load SKILL.md files (confirmed with OpenAI Codex CLI, which uses js-yaml in strict mode).

Fix

Wrap the affected description values in double quotes so the colon is unambiguously part of the string value, not a mapping indicator.

Before:

description: Design finalization: generates production-quality Pretext-native HTML/CSS. (gstack)

After:

description: "Design finalization: generates production-quality Pretext-native HTML/CSS. (gstack)"

Test

import yaml
# parses cleanly with PyYAML, js-yaml, and other strict parsers
yaml.safe_load('description: "Design finalization: generates foo"')

[jbetala7]

Thanks for chasing the strict-YAML parse error — it's a real failure for js-yaml/Codex hosts. Heads up though: this looks already resolved on main, so the PR is effectively a no-op as written.

• All 8 files here already carry quoted description: values on current main (3bef43bc, shipped in the v1.55.0.0 fix wave v1.55.0.0 fix wave: gbrain data-loss guards + browser crash-loop + 6 more #1808). e.g. design-html/SKILL.md:

  description: "Design finalization: generates production-quality Pretext-native HTML/CSS. (gstack)"

  Same for design-consultation, design-review, design-shotgun, guard, plan-tune, setup-gbrain, and ship. GitHub reports this branch as behind_by=5, so it was opened just before that wave merged — rebasing onto current main should show these edits already present.

• The durable fix is generator-level, not hand-editing the generated SKILL.md outputs. These files are emitted by scripts/gen-skill-docs.ts, so a future regeneration would reintroduce unquoted descriptions. v1.55.1.0 Fix generated skill YAML frontmatter #1752 is the canonical place for that — it adds scripts/skill-frontmatter-check.ts validation so this can't regress (with earlier overlap in Fix Codex skill loading errors from unquoted descriptions #1739 / fix(gen-skill-docs): quote frontmatter descriptions containing colons #1786).

Not a knock on the diff — the repro and affected-skill list are accurate; it's just that the symptom was already swept up by #1808 and the root-cause guard is tracked in #1752.