Skip to content
Skills Library
Programming · Tool integration

github

/github

Read and manage GitHub repos, issues, pull requests, and code search via the GitHub REST API. Use when the user asks about GitHub repos, issues, PRs, or code.

Repository
intentic ↗
Licence
MIT
Last repository change
28.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Read and manage GitHub repos, issues, pull requests, and code search via the GitHub REST API. Use when the user asks about GitHub repos, issues, PRs, or code.

Original author description

Read and manage GitHub repos, issues, pull requests, and code search via the GitHub REST API. Use when the user asks about GitHub repos, issues, PRs, or code.

How it works

  1. Git (clone / pull / push)
Original SKILL.md headings · 22 lines, 224 words
SKILL.md preview
---
name: github
description: Read and manage GitHub repos, issues, pull requests, and code search via the GitHub REST API. Use when the user asks about GitHub repos, issues, PRs, or code.
---

# GitHub (connected)

Token in `$GITHUB_TOKEN`. Talk to `$GITHUB_API_URL` (it stands in for https://api.github.com) with `curl`.
Headers: `-H "Authorization: Bearer $GITHUB_TOKEN" -H "Accept: application/vnd.github+json"`.

- Who am I: `curl -s -H "Authorization: Bearer $GITHUB_TOKEN" "$GITHUB_API_URL/user" | jq '{login}'`
- Your repos: `curl -s -H "Authorization: Bearer $GITHUB_TOKEN" "$GITHUB_API_URL/user/repos?per_page=50&sort=updated" | jq '.[] | {full_name, private}'`
- Open issues in a repo: `curl -s -H "Authorization: Bearer $GITHUB_TOKEN" "$GITHUB_API_URL/repos/<OWNER>/<REPO>/issues?state=open" | jq '.[] | {number, title}'`
- Open pull requests: `curl -s -H "Authorization: Bearer $GITHUB_TOKEN" "$GITHUB_API_URL/repos/<OWNER>/<REPO>/pulls?state=open" | jq '.[] | {number, title}'`
- Search issues/PRs: `curl -s -H "Authorization: Bearer $GITHUB_TOKEN" "$GITHUB_API_URL/search/issues?q=<URL_ENCODED_QUERY>" | jq '.items[] | {number, title, html_url}'`
- Create an issue: `curl -s -X POST -H "Authorization: Bearer $GITHUB_TOKEN" "$GITHUB_API_URL/repos/<OWNER>/<REPO>/issues" -d '{"title":"...","body":"..."}'`

## Git (clone / pull / push)
If this connection has git access enabled, https is credential-cached and ssh-form URLs work too (over a native
SSH key when the token could register one, otherwise transparently rerouted over https), so git needs no per-command auth:
- Clone: `git clone https://github.com/<OWNER>/<REPO>.git` (`ssh://git@github.com/<OWNER>/<REPO>.git` works too).
- Pull/push an existing repo (https or ssh clone): `git -C <REPO> pull` / `git -C <REPO> push`
- If native SSH is active, `ssh -T git@github.com` greets you; if it isn't, ssh-form URLs still pull/push over https.

Notes: paginate with `?per_page=100&page=N`. The token's scopes bound what you can reach.

Versions

RepositoryScoreLicence
This page · intentic/intentic90MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
VincenzoImp/pitcrew100MIT
AceDataCloud/Skills100Apache-2.0
the-open-agent/openagent100Apache-2.0
OpenHands/extensions100MIT
TerminalSkills/skills100Apache-2.0
atomicbot-ai/atomic-agent100MIT

Database snapshot: 13.11.2026 · package version 9f89a7f9ce21 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100gh-cli
    The gh CLI is GitHub's official command line tool for interacting with GitHub repositories, issues, pull requests, and more. When needs to interact with GitHub repositories, issues, pull requests, and more, use this skill.
  • 95github-cli
    MUST USE for GitHub-related operations, including a GitHub URL, repository or code search, Issues, pull requests, Actions, Releases, permissions, and API requests. Use the local GitHub CLI (`gh`).
  • 90gitlab
    Read and manage GitLab projects, issues, merge requests, and pipelines via the GitLab REST API. Use when the user asks about GitLab projects, issues, MRs, or pipelines.
  • 95gh-helper
    Complete GitHub operations via gh CLI - repos, issues, PRs, code search, releases, file management When user mentions GitHub, repositories, issues, PRs, gh command, code search, commits, file contents
  • 100gh-cli
    Use for GitHub-related tasks such as managing issues, pull requests, actions runs, and repository configuration using the GitHub CLI (gh).
  • 100github-operations
    gh CLI and REST patterns for issues, PRs, milestones and Projects v2. Use when managing GitHub issues, PRs or projects.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.