github

combined

Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries. Use when the user asks about GitHub issues, pull requests, workflows, or wants to interact with GitHub repositories from the command line — including tasks like check CI status, create PR, list issues, or query the GitHub API. Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.

When to use

When the user asks about GitHub issues, pull requests, workflow runs, or CI failures.
When you need `gh issue`, `gh pr`, `gh run`, or `gh api` from the command line.

When not to use

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The four copies share the name 'github' but describe two different procedures. kostja94/marketing-skills is a marketing/SEO skill for optimizing GitHub surfaces (profile README, pinned repos, repository README, GitHub Pages, gists, Awesome lists) for parasite SEO and GEO. The other three (Dimillian/Skills, sickn33/agentic-awesome-skills, LeoYeAI/openclaw-master-skills) are a devops/software-engineering skill for interacting with GitHub via the gh CLI (issues, PRs, CI runs, API queries). The gh-CLI copies are near-identical, with sickn33 adding a 'When to Use' section and a 'Limitations' section, and explicitly citing Dimillian/Skills as the source. Because the two procedures overlap only in the name and do not reproduce each other's steps, crowning one would hide a real alternative.