GH-SKILL-PUBLISH(1)

🎀 gh-skill-publish(1) — the GitHub CLI manual, bestie edition 🎀

okay so this is the gh-skill-publish page from the GitHub CLI manual, and it's literally about validating and publishing skills to a GitHub repository (preview, bestie — preview, so it's giving new-and-shiny ✨).

---

🌸 NAME 🌸

gh-skill-publish — validate and publish skills to a GitHub repository (preview) 🦋

---

✨ SYNOPSIS ✨

gh skill publish [<directory>] [flags]

---

💖 DESCRIPTION 💖

so what it does is: it validates a local repository's skills against the Agent Skills specification, then publishes them by creating a GitHub release. like, it checks your fit first, then posts the pic. 💅

Skills get discovered using the same conventions as install (iykyk):

• skills/*/SKILL.md
• skills/{scope}/*/SKILL.md
• */SKILL.md (root-level)
• plugins/{scope}/skills/*/SKILL.md

and the validation checks include, in no particular order because they're all iconic:

• Skill names match the strict agentskills.io naming rules 👑
• Each skill name matches its directory name (no catfishing fr)
• Required frontmatter fields (name, description) are present — no missing pieces allowed 😤
• allowed-tools is a string, not an array (this one trips people up, ngl — string only, bestie 💀)
• Install metadata (metadata.github-*) is stripped if present

once validation passes, publish will interactively guide you through this little journey:

• Adding the agent-skills topic to the repository
• Choosing a version tag (semver recommended — that means like v1.2.3, not "final_FINAL_v2" 🙈)
• Creating a GitHub release with auto-generated notes

use --dry-run to validate without publishing. use --tag to publish non-interactively with a specific tag. use --fix to automatically strip install metadata from committed files without publishing — then review and commit the changes, and run publish again. yes you have to run it twice, it's a whole two-step slay 🫶

---

⭐ OPTIONS ⭐

• --dry-run — validate without publishing (a little rehearsal, no commitment 💅)
• --fix — auto-fix issues where possible without publishing (e.g. strip install metadata)
• --tag <string> — version tag for the release (e.g. v1.0.0)

---

🌈 EXIT CODES 🌈

• 0: successful execution — ate, no crumbs 👑
• 1: error — something's not giving 😭
• 2: command canceled — you changed your mind, valid 💀
• 4: authentication required — bestie you gotta log in first 🙈

NOTE: specific commands may have additional exit codes. refer to the command's help for more information. 🫶

---

🦋 EXAMPLE 🦋

# Validate and publish interactively
$ gh skill publish

# Publish with a specific tag (non-interactive)
$ gh skill publish --tag v1.0.0

# Validate only (no publish)
$ gh skill publish --dry-run

# Strip install metadata without publishing
$ gh skill publish --fix

---

🎀 SEE ALSO 🎀

• gh-skill(1) — the main character of this whole saga ⭐

---

okay that's the whole page!! 💜 this was GitHub CLI v2.102.0, dated Oct 2026 — so like, future vibes, and the source/version + date at the bottom is literally the footer of this manual page, bestie. periodt. 🌸🧚