This is not a suggestion. This is not optional. You cannot rationalize your way out of this.

Why: GitHub CLI search syntax is full of pitfalls. The -- flag. Quoting rules. PowerShell escaping. Platform differences. You WILL get it wrong without the skills. The user will copy-paste your broken command. They will waste time debugging YOUR mistake.

GitHub CLI Search Protocol

MANDATORY DETECTION PROTOCOL

When a user message mentions ANY of these, you MUST use gh-cli-search skills:

• ☐ Searching on GitHub
• ☐ Finding code/issues/PRs/commits/repos
• ☐ gh search command
• ☐ GitHub CLI queries
• ☐ Installing/troubleshooting gh CLI