How do I install the Github skill?

Run npx skillmds@latest add tomevault-io/github-20 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github by tomevault-io — Agent Skill

Name: Github
Author: tomevault-io

File contents

GitHub Skill

Work with GitHub repositories using the gh CLI for all GitHub operations.

Using the gh CLI

Always use the gh CLI for GitHub interactions instead of direct API calls or web URLs:

Pull Requests

# Create PR
gh pr create --title "Title" --body "Description"

# List PRs
gh pr list

# View PR details
gh pr view 123

# Check out a PR locally
gh pr checkout 123

# Merge PR
gh pr merge 123 --squash

# Review PR
gh pr review 123 --approve
gh pr review 123 --request-changes --body "Please fix..."

Issues

# Create issue
gh issue create --title "Title" --body "Description"

# List issues
gh issue list

# View issue
gh issue view 123

# Close issue
gh issue close 123

Workflows (GitHub Actions)

# List workflows
gh workflow list

# View workflow runs
gh run list

# View specific run
gh run view 123456

# Watch a running workflow
gh run watch 123456

# Trigger workflow manually
gh workflow run workflow-name.yml

# Download artifacts
gh run download 123456

Releases

# Create release
gh release create v1.0.0 --title "Release v1.0.0" --notes "Release notes"

# List releases
gh release list

# Download release assets
gh release download v1.0.0

Repository Operations

# Clone repository
gh repo clone owner/repo

# Fork repository
gh repo fork owner/repo

# View repository
gh repo view owner/repo

Multiple GitHub Profiles

The user may have multiple GitHub accounts authenticated (e.g., personal and work accounts).

Handling 404 Errors

If a gh command fails with a 404 error, it likely means you're authenticated as the wrong account for that repository.

To diagnose:

# List all authenticated profiles
gh auth status -h github.com

This shows all authenticated accounts and which one is currently active.

To fix:

# Switch to a different profile
gh auth switch -h github.com -u <username>

Replace <username> with the appropriate GitHub username for the repository you're trying to access.

Example Workflow

# Command fails with 404
gh pr list
# error: Could not resolve to a Repository...

# Check which account is active
gh auth status -h github.com
# github.com
#   ✓ Logged in to github.com account personal-user (keyring)
#   - Active account: true
#   ✓ Logged in to github.com account work-user (keyring)
#   - Active account: false

# Switch to work account
gh auth switch -h github.com -u work-user

# Retry the command
gh pr list
# Now it works!

Proactive Approach

When working with a repository, if you're unsure which account has access:

Check the repository's organization/owner
Run gh auth status -h github.com to see available accounts
Switch to the appropriate account before running commands

Common Patterns

Create PR with Labels and Reviewers

gh pr create \
  --title "feat: add new feature" \
  --body "Description of changes" \
  --label "enhancement" \
  --reviewer username1,username2

View PR Comments

gh api repos/{owner}/{repo}/pulls/{pr_number}/comments

Check CI Status

gh pr checks 123

Search Issues

gh issue list --search "bug in:title"

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: github-20description: Work with GitHub using gh CLI - create/update PRs, manage workflows, issues, and releases. Handles multiple authenticated profiles. Use when this capability is needed.---# GitHub SkillWork with GitHub repositories using the `gh` CLI for all GitHub operations.## Using the gh CLIAlways use the `gh` CLI for GitHub interactions instead of direct API calls or web URLs:### Pull Requests```bash# Create PRgh pr create --title "Title" --body "Description"# List PRsgh pr list# View PR detailsgh pr view 123# Check out a PR locallygh pr checkout 123# Merge PRgh pr merge 123 --squash# Review PRgh pr review 123 --approvegh pr review 123 --request-changes --body "Please fix..."```### Issues```bash# Create issuegh issue create --title "Title" --body "Description"# List issuesgh issue list# View issuegh issue view 123# Close issuegh issue close 123```### Workflows (GitHub Actions)```bash# List workflowsgh workflow list# View workflow runsgh run list# View specific rungh run view 123456# Watch a running workflowgh run watch 123456# Trigger workflow manuallygh workflow run workflow-name.yml# Download artifactsgh run download 123456```### Releases```bash# Create releasegh release create v1.0.0 --title "Release v1.0.0" --notes "Release notes"# List releasesgh release list# Download release assetsgh release download v1.0.0```### Repository Operations```bash# Clone repositorygh repo clone owner/repo# Fork repositorygh repo fork owner/repo# View repositorygh repo view owner/repo```## Multiple GitHub ProfilesThe user may have multiple GitHub accounts authenticated (e.g., personal and work accounts).### Handling 404 ErrorsIf a `gh` command fails with a **404 error**, it likely means you're authenticated as the wrong account for that repository.**To diagnose:**```bash# List all authenticated profilesgh auth status -h github.com```This shows all authenticated accounts and which one is currently active.**To fix:**```bash# Switch to a different profilegh auth switch -h github.com -u <username>```Replace `<username>` with the appropriate GitHub username for the repository you're trying to access.### Example Workflow```bash# Command fails with 404gh pr list# error: Could not resolve to a Repository...# Check which account is activegh auth status -h github.com# github.com# ✓ Logged in to github.com account personal-user (keyring)# - Active account: true# ✓ Logged in to github.com account work-user (keyring)# - Active account: false# Switch to work accountgh auth switch -h github.com -u work-user# Retry the commandgh pr list# Now it works!```### Proactive ApproachWhen working with a repository, if you're unsure which account has access:1. Check the repository's organization/owner2. Run `gh auth status -h github.com` to see available accounts3. Switch to the appropriate account before running commands## Common Patterns### Create PR with Labels and Reviewers```bashgh pr create \ --title "feat: add new feature" \ --body "Description of changes" \ --label "enhancement" \ --reviewer username1,username2```### View PR Comments```bashgh api repos/{owner}/{repo}/pulls/{pr_number}/comments```### Check CI Status```bashgh pr checks 123```### Search Issues```bashgh issue list --search "bug in:title"```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/igrybkov) — claim your Tome and manage your conversions.

Frequently asked questions

Github