fix(skills): codex-fleet and omp-fleet frontmatter fails YAML parsing

[UBRN]

Both codex-fleet and omp-fleet currently fail to load. Their description values are unquoted plain YAML scalars containing ": " (colon-space), which YAML reads as a mapping indicator:

$ ruby -ryaml -e YAML.safe_load(File.read("skills/codex-fleet/SKILL.md")[4..])
mapping values are not allowed in this context at line 2 column 129

The failure is silent — a SKILL.md whose frontmatter does not parse is skipped with no error and no warning, so the skill simply never triggers. It looks identical to a skill that was loaded but did not match.

Three colon-space sequences per file, not one:

file	columns
skills/codex-fleet/SKILL.md	129 (describes): ), 371 (locked: ), 562 (on: )
skills/omp-fleet/SKILL.md	241, 446, 527

Fix

Converted both to >- folded block scalars. No wording changed — the descriptions round-trip byte-identical (882 and 686 chars), so every trigger keyword is preserved verbatim.

skills/gptpro/SKILL.md was not broken, but its description is the same unquoted plain-scalar construct — one future ": " away from the identical failure. Hardened alongside, same zero-content-change treatment (423 chars, unchanged).

Verification

$ ruby -ryaml -e Dir["skills/*/SKILL.md"].each { |f| r=File.read(f,encoding:"UTF-8"); YAML.safe_load(r[4..r.index("\n---\n",3)]) }

Fails on the two files before this change, clean after. All 10 skills parse; name matches directory in every case; every description is under the 1024-char limit.

Note

Happy to follow up with a small CI check (ruby scripts/validate-skills.rb + a workflow) that parses every SKILL.md and fails the build on malformed frontmatter, if that is wanted — kept out of this PR to keep it to one concern. This bug class is invisible without one.

🤖 Generated with Claude Code