How do I install the Blink Github skill?

Run npx skillmds@latest add blink-new/blink-github-2 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 Blink Github safe to use?

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

Which AI agents work with Blink 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 Blink Github free to use?

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

Who published Blink Github?

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

Blink Github by blink-new — Agent Skill

Name: Blink Github
Author: blink-new

Blink Github

GitHub operations via the Blink GitHub App — clone repos, push code, open pull requests, create issues, check CI, and call the GitHub REST API. No PAT needed. Connect once at blink.new/settings?tab=connectors and every surface (CLI, MCP, Claw agents) works automatically.

blink-new Updated Sep 22, 2026

File contents

Blink GitHub

Full GitHub access backed by a workspace GitHub App installation. Tokens are short-lived (1h), minted just-in-time server-side — no personal access token, no gh auth login, no secrets on disk.

CLI

# Show all connected GitHub accounts (workspaces can link multiple)
blink github status

# Clone a repo (token is used for auth, stripped from .git/config after)
blink github clone owner/repo
blink github clone https://github.com/owner/repo.git --branch feat/x

# Print a short-lived token for scripting
blink github token --json | jq -r .token

# Multi-account: pick a specific installation
blink github clone owner/repo --account blink-new
blink github token --account my-employer-org

REST API (connector exec)

# List repos
blink connector exec github /user/repos GET

# Get a specific repo
blink connector exec github /repos/owner/repo GET

# Create an issue
blink connector exec github /repos/owner/repo/issues POST \
  '{"title":"Bug report","body":"Steps to reproduce..."}'

# List open PRs
blink connector exec github /repos/owner/repo/pulls GET '{"state":"open"}'

# CI status (last 5 runs)
blink connector exec github /repos/owner/repo/actions/runs GET '{"per_page":5}'

# Read a file (returns base64-encoded content)
blink connector exec github /repos/owner/repo/contents/README.md GET

MCP Tools

Use the blink_connector_exec tool with provider: "github":

{
  "tool": "blink_connector_exec",
  "provider": "github",
  "projectId": "proj_xxx",
  "endpoint": "/repos/owner/repo/issues",
  "httpMethod": "POST",
  "params": { "title": "Bug", "body": "Details..." }
}

Prerequisites

Connect GitHub once at blink.new/settings?tab=connectors.

The workspace links a GitHub App installation — not a personal OAuth token. This means:

Works on SSO/SAML-enforced orgs (no per-token SSO dance)
Short-lived 1h tokens — no long-lived secrets
Revoke by uninstalling the App; no keys to rotate manually
Multi-account: link your personal account + work orgs independently

On Blink Claw agents

git clone, git push, gh pr create work with zero setup — the Claw image ships a system-level git credential helper that mints tokens automatically. No gh auth login, no PAT.

---name: blink-github-2description: GitHub operations via the Blink GitHub App — clone repos, push code, open pull requests, create issues, check CI, and call the GitHub REST API. No PAT needed. Connect once at blink.new/settings?tab=connectors and every surface (CLI, MCP, Claw agents) works automatically.---# Blink GitHubFull GitHub access backed by a workspace GitHub App installation. Tokens areshort-lived (1h), minted just-in-time server-side — no personal access token,no `gh auth login`, no secrets on disk.## CLI```bash# Show all connected GitHub accounts (workspaces can link multiple)blink github status# Clone a repo (token is used for auth, stripped from .git/config after)blink github clone owner/repoblink github clone https://github.com/owner/repo.git --branch feat/x# Print a short-lived token for scriptingblink github token --json | jq -r .token# Multi-account: pick a specific installationblink github clone owner/repo --account blink-newblink github token --account my-employer-org```## REST API (connector exec)```bash# List reposblink connector exec github /user/repos GET# Get a specific repoblink connector exec github /repos/owner/repo GET# Create an issueblink connector exec github /repos/owner/repo/issues POST \ '{"title":"Bug report","body":"Steps to reproduce..."}'# List open PRsblink connector exec github /repos/owner/repo/pulls GET '{"state":"open"}'# CI status (last 5 runs)blink connector exec github /repos/owner/repo/actions/runs GET '{"per_page":5}'# Read a file (returns base64-encoded content)blink connector exec github /repos/owner/repo/contents/README.md GET```## MCP ToolsUse the `blink_connector_exec` tool with `provider: "github"`:```json{ "tool": "blink_connector_exec", "provider": "github", "projectId": "proj_xxx", "endpoint": "/repos/owner/repo/issues", "httpMethod": "POST", "params": { "title": "Bug", "body": "Details..." }}```## PrerequisitesConnect GitHub once at **blink.new/settings?tab=connectors**.The workspace links a GitHub App installation — not a personal OAuth token.This means:- Works on SSO/SAML-enforced orgs (no per-token SSO dance)- Short-lived 1h tokens — no long-lived secrets- Revoke by uninstalling the App; no keys to rotate manually- Multi-account: link your personal account + work orgs independently## On Blink Claw agents`git clone`, `git push`, `gh pr create` work with zero setup — the Clawimage ships a system-level git credential helper that mints tokensautomatically. No `gh auth login`, no PAT.

Frequently asked questions