Validator now catches YAML the runtime would drop
skill_validate previously accepted frontmatter that opencode's strict YAML parser rejects at runtime — the skill would validate fine, then silently never load. The hand-rolled validator (still zero dependencies) now rejects unquoted top-level values that are invalid YAML, with the offending key, the actual file line number, and a quoting hint:
- values containing
:(colon-space) or:<tab>— e.g.description: Use for PDF files: reading - values ending with
:— e.g.description: Note:
Quoted values, block scalars (including |2- style indicators), continuation lines, and list items are unaffected. (#33, reworking #30 — thanks @mxl for the report and test scenarios.)
Worked example for new users
New examples/docker-compose-helper/ (#34, addressing #21): a small complete skill, an 8-query trigger eval set in the exact skill_eval format, and a copy-pasteable walkthrough of the eval → optimize → benchmark loop — linked from the README's new Examples section. The fastest way to see eval-driven skill development end to end.
Full changelog: v0.2.22...v0.2.23