Primary finding
gh api contents .content jq extraction will fail to base64-decode without `-r`
- skills/skill-update-check/SKILL.md:53-58
`--jq '.content'` outputs the JSON-encoded string with surrounding quotes (since jq is not given `-r` and gh's `--jq` mirrors jq behavior). Piping a quoted string into `base64 -d` will fail with `invalid input` because the leading `"` is not valid base64. Additionally, GitHub's contents API returns base64 with embedded newlines that base64 handles, but the quotes are the blocker. Also, `-f ref=` sends ref as a body param; for GET it becomes a query param, which is correct, but the quote issue still breaks decoding.
Recommendation
Use `--jq -r '.content'` is not valid syntax; instead use `| jq -r '.content'` or `gh api ... -q '.content'` is also quoted. Correct form: `gh api ... --jq '.content' | tr -d '"\n' | base64 -d` or use `gh api ... | jq -r '.content' | base64 -d`.