Skip to content

fix(SKILL.md): quote argument-hint so YAML parses it as string#80

Open
thejesh23 wants to merge 1 commit into
therealXiaomanChu:mainfrom
thejesh23:fix/copilot-cli-1.0.65-argument-hint-string
Open

fix(SKILL.md): quote argument-hint so YAML parses it as string#80
thejesh23 wants to merge 1 commit into
therealXiaomanChu:mainfrom
thejesh23:fix/copilot-cli-1.0.65-argument-hint-string

Conversation

@thejesh23

@thejesh23 thejesh23 commented Jul 3, 2026

Copy link
Copy Markdown

Summary

SKILL.md has:

argument-hint: [ex-name-or-slug]

In YAML, an unquoted [...] value is a flow sequence (an array), not a string. Copilot CLI 1.0.65 requires argument-hint to be a string, so loading the skill currently fails validation on that runtime.

The fix quotes the value so YAML parses it as a string while preserving the visible [ex-name-or-slug] hint that users see:

argument-hint: "[ex-name-or-slug]"

Verified locally with yaml.safe_load — the value now parses as str '[ex-name-or-slug]' instead of list ['ex-name-or-slug']. Claude Code has been tolerant of the array form, but the same latent inconsistency has been reported there too (see refs below).

YAML rule

  • argument-hint: [X] → sequence [X] (WRONG for tools expecting a string)
  • argument-hint: "[X]" → string "[X]" (CORRECT)
  • argument-hint: ["X"] → sequence ["X"] (WRONG)
  • argument-hint: "X" → string "X" (CORRECT)

Scope

Full-tree scan for argument-hint: in this repo turned up exactly one occurrence — SKILL.md line 4. The generated per-ex SKILL.md template embedded in this file (Step 5) does not emit an argument-hint field, so no other changes are needed.

References

Test plan

  • yaml.safe_load on the updated frontmatter returns argument-hint as str
  • Load create-ex skill in Copilot CLI 1.0.65 and confirm the frontmatter validates
  • Load create-ex skill in Claude Code and confirm the [ex-name-or-slug] hint still renders as before

Unquoted `[ex-name-or-slug]` is parsed as a YAML flow sequence, but
Copilot CLI 1.0.65 requires `argument-hint` to be a string. Wrapping
the value in quotes keeps the visual `[...]` hint while satisfying
the string requirement.
@thejesh23

Copy link
Copy Markdown
Author

Tracking issue: #81 — captures the bug diagnosis and reproducer separately for anyone searching the repo who lands there before this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant