Individual skill

github-push

Push a local directory to a GitHub repository without needing the raw personal access token. Use when the user wants to publish, upload, or push files or a project to GitHub and a GitHub connector credential is stored in the Secure Vault. Works from any machine via the GitHub git-database API — no git CLI credentials needed.

skills-imported/github-push/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# GitHub Push

Pushes a local directory's files to a GitHub repo (`owner/repo`, branch) using the GitHub git-database REST API. Authenticates through the Secure Vault GitHub connector via the authd surrogate exchange — the real token is never exposed; the script fetches a short-lived surrogate (`authdc cred surrogate custom.github`) and sends it as a Bearer header, which authd swaps for the real credential at egress.

## When to use

- The user asked to publish/push/upload a local project or folder to their GitHub repo.
- A GitHub connector credential is already stored (via `credentials.request_api_access` with provider `github`).
- The git CLI can't be authenticated (e.g., no credential helper, mobile-driven workflows, sandboxed machines).

## How it works

`scripts/push_repo.py` performs the equivalent of an initial (or updating) push: