MANDATORY skill when users mention GitHub CLI searches - establishes non-negotiable requirement to use gh-cli-search skills for correct syntax, quoting, and platform handling
Mandatory skill for GitHub CLI searches. Prevents broken commands by handling the `--` flag, quoting, and platform-specific syntax. Automatically triggers when users mention `gh search`, finding code/issues/PRs, or GitHub CLI queries.
/plugin marketplace add aaddrick/gh-cli-search/plugin install gh-cli-search@helpful-tools-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
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.
</EXTREMELY-IMPORTANT>
When a user message mentions ANY of these, you MUST use gh-cli-search skills:
gh search commandIf detected → Use the Skill tool to load the appropriate gh-cli-search skill
You have access to these gh-cli-search skills:
Pick the right skill. Use the Skill tool. Follow it exactly.
If you catch yourself thinking ANY of these thoughts, STOP. You are about to give the user a broken command.
-- flag for exclusions.-- flag. Or quote incorrectly. Or miss PowerShell escaping.Why: Every time you skip these skills for "simple" gh CLI questions, you give incorrect commands. The -- flag gets missed. Quoting breaks. PowerShell fails. The user's time is wasted.
-- Flag Will Bite YouThe most common mistake: Forgetting the -- flag before queries with exclusions.
Without the skill, you WILL write:
gh search issues "is:open -label:bug" # BROKEN - shell interprets -label as a flag
The skill ensures you write:
gh search issues -- "is:open -label:bug" # CORRECT
This is not optional. This is why the skills exist.
-- flag for exclusions--% requirementUsing the skill takes 30 seconds. Debugging your broken command takes 10 minutes.
User mentions GitHub CLI searching:
User asks about installation/troubleshooting:
These skills are not "nice to have" documentation. They are battle-tested patterns that prevent the specific, predictable mistakes you make when constructing gh CLI commands without them.
The skills encode:
-- flag is requiredYou cannot replicate this from memory. Stop trying.
User asks about GitHub CLI searching → You MUST use the gh-cli-search skill.
Not optional. Not negotiable. The skill exists to prevent you from giving broken commands.
Use it every single time.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.