GH-SKILL-SEARCH(1)

πŸ’… gh-skill-search(1) β€” the GitHub CLI manual, but make it make sense 🫢

okay so bestie, you know how the GitHub CLI has a whole manual? yeah. this is a page from it β€” gh-skill-search β€” and honestly it's giving "underrated icon." it's in preview rn, so treat it like a soft launch, not a wedding. πŸ’–


✨ NAME ✨

gh-skill-search β€” search for skills across GitHub, and yes the "(preview)" is staying in the title because that's literally what it is πŸ”


🌸 SYNOPSIS 🌸

gh skill search <query> [flags]

that's it. that's the whole vibe. a query and some flags, go off queen πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

so what does it do? it searches across all public GitHub repositories for skills that match a keyword. all of them. the whole entire site. no cap. 🌈

under the hood it's using the GitHub Code Search API to find SKILL.md files whose name or description matches your query term. that's the mechanism, that's the tea. β˜•

results come back ranked by relevance β€” and the way that ranking works is: skills whose name contains the query term show up first. so name-matchers are the main characters here πŸ‘‘βœ¨

you can also use --owner to scope results to a specific GitHub user or organization, which is lowkey the move when you already know whose skills you want. 🎯

and in interactive mode, you can pick skills straight out of the results and install them directly. no copy-paste era. we're selecting and installing in one flow, periodt. πŸ’…


πŸŽ€ OPTIONS πŸŽ€

  • -q, --jq <expression> β€” filter the JSON output using a jq expression. yes, jq. the beloved. πŸ“
  • --json <fields> β€” output JSON but only with the fields you specify. choose your fighters. ⭐
  • -L, --limit <int> (default 15)** β€” max number of results per page. default is 15, so don't act surprised when you get 15.
  • --owner <string> β€” filter results down to a specific GitHub user or organization. scope it, girl. πŸ”
  • --page <int> (default 1)** β€” which page of results to fetch. default is 1, aka page one, aka the beginning, aka where we all start. 🧚
  • -t, --template <string> β€” format the JSON output using a Go template; see gh help formatting for the details. the manual is pointing you somewhere, follow the pointer bestie 🫢

πŸ’œ JSON FIELDS πŸ’œ

here's the field situation β€” these are the ones in play:

  • description
  • namespace
  • path
  • repo
  • skillName
  • stars

six little fields, all iconic in their own way ✨


πŸ”₯ EXIT CODES πŸ”₯

okay this part matters, don't skip it, this is the vibe check at the door:

  • 0 β€” successful execution. you ate. πŸŽ‰
  • 1 β€” error. it's giving struggle. 😭
  • 2 β€” command canceled. you backed out, no shame. πŸ™ˆ
  • 4 β€” authentication required. go log in babes, it can't read your mind. πŸ”
NOTE: specific commands may have additional exit codes. refer to the command's help for more information β€” i'm just the messenger, not the whole encyclopedia πŸ’€

🌟 EXAMPLE 🌟

real examples, copy-paste ready, you're welcome:

# Search for skills related to terraform
$ gh skill search terraform

# Search for skills from a specific owner
$ gh skill search terraform --owner hashicorp

# View the second page of results
$ gh skill search terraform --page 2

# Limit results to 5
$ gh skill search terraform --limit 5

look at that. terraform, hashicorp, page 2, limit 5. every single one is in there and none of them got dropped. we keep all the details in this house πŸ πŸ’–


🌈 SEE ALSO 🌈

  • gh-skill(1) β€” the sibling. go read it next, i'll wait 🫢

and that's the page!! thank you for coming to my ted talk πŸ’…βœ¨

this was the GitHub CLI v2.102.0 manual, dated Oct 2026 β€” so if you're reading this from the future, hi, hope the vibes held up πŸ¦‹πŸ’–

bye bestie, go search some skills πŸŽ€

πŸ“¦ where this page comes from