Repository navigation
fix(skills): quote-safe YAML in 4 skill descriptions (strict-parser compatible) - #250
Merged
Merged
Conversation
…calar) The description: values of tina4-a11y, tina4-architect, tina4-design and tina4-seo were plain unquoted scalars containing ": " (from "Triggers:" / "Trigger phrases:"), which strict YAML 1.2 reads as a nested mapping. A strict reader (the `yaml` npm package, YAML 2.6.1) rejects them with "Nested mappings are not allowed in compact mappings"; Claude Code's lenient header reader accepted them, so it never surfaced. Fold each to a `description: >` block scalar — the same form the three already-valid skills (tina4-developer-*, tina4-js, tina4-maintainer) use. Folding needs no escaping, so the inner quotes, the apostrophe in seo's "AI systems can't find us", the colons and the em dashes all survive verbatim. Verified: all seven skill frontmatters now parse under the same `yaml` package, descriptions byte-intact. Reaches installed users at the next skills bundle regen. Co-Authored-By: Tina4 <82961293+tina4stack@users.noreply.github.com> Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Andre van Zuydam <andrevanzuydam@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Quote-safe YAML in 4 skill descriptions
The
description:values of tina4-a11y, tina4-architect, tina4-design, tina4-seo were plain unquoted scalars containing": "(fromTriggers:/Trigger phrases:). Strict YAML 1.2 reads that as a nested mapping — theyamlnpm package (2.6.1) rejects them with "Nested mappings are not allowed in compact mappings". Claude Code's lenient header reader accepted them, so it never surfaced until a strict consumer read them.Fix
Fold each to
description: >— the exact form the three already-valid skills (tina4-developer-*,tina4-js,tina4-maintainer) use. Folding needs no escaping, so inner quotes, the apostrophe in seo's "AI systems can't find us", colons and em-dashes all survive verbatim (a single-quote fix would've had to escape that apostrophe).Verified
All seven skill frontmatters now parse under the same
yaml@2.6.1package; the parseddescriptionstrings are byte-intact (checked length + head/tail). The other three repos' skills were swept — none affected (the broken 4 are tina4-python-only).Reaches installed users at the next skills bundle regen; the harness copy needs no change (it passes a clean header through unchanged).
🤖 Generated with Claude Code