{{One-sentence what-it-does + when to use it. Mention it bypasses the MCP via the REST API with {{ENV_VAR}}. Use when the user wants X, Y, Z programmatically without the {{service}} MCP installed.}}
日本語の概要は準備中です。原文の説明を表示しています。
Operate on GitHub via the REST API — repos, PRs, issues, code search, actions, releases. Use when the user wants scripted / cross-repo operations, doesn't have `gh` installed, or needs behavior the `gh` CLI doesn't expose cleanly.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Direct REST access to GitHub — repos, PRs, issues, code search, Actions, releases. Use when the answer depends on current state and gh is absent or too narrow.
jq, CI status reads, when gh isn't installed.git), one-shot reads when user has gh (gh pr view), concept questions.[ -n "${GITHUB_TOKEN:-$GITHUB_PERSONAL_ACCESS_TOKEN}" ] && echo "GITHUB_TOKEN: PRESENT" || echo "GITHUB_TOKEN: MISSING"
Never echo the variable directly (e.g. echo "$GITHUB_TOKEN") — the value would appear in the conversation transcript. Use only the boolean pattern above.
If MISSING, respond to the user with EXACTLY this message (do NOT paraphrase, do NOT suggest manual JSON edits):
I need your github credential. Run this in another terminal — it'll open the signup page, validate format, and save it safely with masked input:
teleport-setup add-key githubThen restart Claude Code (
/exit, thenclaude) and ask me again.
Do NOT suggest editing ~/.claude/settings.local.json manually. The teleport-setup add-key command handles it with backup, validation, and masked input. Stop execution until the user has run the command and restarted.
https://api.github.comAuthorization: Bearer $GITHUB_TOKENAccept: application/vnd.github+json (recommended on every call for stable response shape).X-GitHub-Api-Version: 2022-11-28 — pin this header or the default floats to whatever GitHub promotes next.x-ratelimit-*.per_page (max 100), page 1-indexed. Follow the Link response header (rel="next") — not offset math.Fine-grained PAT (preferred: per-repo, named permissions like contents:read) vs classic PAT (coarse scopes like repo, workflow). Inside Actions, GITHUB_TOKEN is workflow-scoped. Scopes matter: a token missing the required scope returns 404, not 401 (see Gotchas).
Samples below use a helper that bundles the three standard headers:
GH() { curl -sL -H "Authorization: Bearer $GITHUB_TOKEN" -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" "$@"; }
| Area | Path |
|---|---|
| Repo metadata | GET /repos/{owner}/{repo} (read .default_branch) |
| Contents | GET /repos/{owner}/{repo}/contents/{path}?ref={sha} (base64) |
| Issues | GET/POST /repos/{owner}/{repo}/issues (returns PRs too) |
| Issue comments | POST /repos/{owner}/{repo}/issues/{n}/comments |
| Pulls | GET /repos/{owner}/{repo}/pulls · GET .../pulls/{n} (diff via Accept) |
| PR reviews | POST /repos/{owner}/{repo}/pulls/{n}/reviews (APPROVE/REQUEST_CHANGES/COMMENT) |
| Search | GET /search/code · /search/issues · /search/repositories |
| Actions | GET /repos/{owner}/{repo}/actions/runs |
| Releases | GET /repos/{owner}/{repo}/releases/latest |
1. Issue triage (list + comment)
GH "https://api.github.com/repos/OWNER/REPO/issues?state=open&labels=bug&sort=updated&per_page=50"
GH -X POST "https://api.github.com/repos/OWNER/REPO/issues/NUM/comments" \
-d '{"body":"Thanks — reproduced on main, PR incoming."}'
2. PR review (list + diff + review)
GH "https://api.github.com/repos/OWNER/REPO/pulls?state=open&sort=updated"
# Unified diff: swap Accept on the same endpoint
curl -sL -H "Authorization: Bearer $GITHUB_TOKEN" -H "Accept: application/vnd.github.diff" \
"https://api.github.com/repos/OWNER/REPO/pulls/NUM"
GH -X POST "https://api.github.com/repos/OWNER/REPO/pulls/NUM/reviews" \
-d '{"event":"APPROVE","body":"LGTM, tests cover the edge case."}'
3. Code search (trim with jq)
# Qualifiers: repo:, language:, path:, user:, org:, in:file, extension:
GH "https://api.github.com/search/code?q=useState+repo:facebook/react+language:typescript&per_page=30" \
| jq '[.items[] | {repo: .repository.full_name, path, url: .html_url}]'
X-GitHub-Api-Version floats to the current default — breaks silently over time when GitHub ships a new version. Pin it.repo sees private repos as "not found." If GET /repos/{owner}/{repo} 404s on a repo you know exists, suspect scopes before spelling.403 with x-ratelimit-remaining still positive. Throttle and retry with backoff./issues returns pull requests too (every PR is an issue in GitHub's model). Filter .pull_request == null when you want pure issues.main. Read .default_branch from GET /repos/{owner}/{repo} before building any ref= URL.Link header is authoritative for pagination, not offset math. Missing rel="next" = done.When done, state: Used skill: GitHub (from teleport catalog).
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
{{One-sentence what-it-does + when to use it. Mention it bypasses the MCP via the REST API with {{ENV_VAR}}. Use when the user wants X, Y, Z programmatically without the {{service}} MCP installed.}}
日本語の概要は準備中です。原文の説明を表示しています。
Manage Cloudflare DNS zones, Workers, Pages, R2, KV, D1, and analytics via REST API. Use when the user wants to query DNS, deploy a Worker, list R2 buckets, manage KV namespaces, run D1 queries, or check analytics without the Cloudflare MCP installed.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch up-to-date library, framework, and SDK documentation via Context7's search and docs endpoints. Use when the user asks about a library/API (React, Next.js, Prisma, Supabase, Tailwind, Django, Vue, etc.) and you need current docs, not Claude's training-time knowledge. Skip this skill for generic programming questions that don't require library-specific docs.
日本語の概要は準備中です。原文の説明を表示しています。
Operate Discord via its REST API — post/read channel messages, manage guilds + roles, fire webhooks, register slash commands. Use when the user wants a bot to post to a channel, read recent history, run a community admin task, or ship one-way notifications via webhook URL without running a bot process.
日本語の概要は準備中です。原文の説明を表示しています。
AI-first web search via Exa — semantic/neural ranking, category-scoped results, fresh content retrieval, and one-shot answer synthesis with citations. Use when the user needs current web information better ranked than general web search, or a grounded answer with sources.
日本語の概要は準備中です。原文の説明を表示しています。
Read Figma files, component libraries, styles, comments, and export rendered assets (PNG / SVG / JPG / PDF) via Figma's REST API. Use when the user needs programmatic access to design files, to pull node data into code generation, or to export assets without opening the Figma desktop app.
日本語の概要は準備中です。原文の説明を表示しています。