github-pat-private-repos

Configure GitHub token authentication for private repository clone and push operations.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill github-pat-private-repos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pat-private-repos
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/skills/github-pat-private-repos
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill github-pat-private-repos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of authenticating GitHub access for private repositories, especially when clone, push, or workflow updates fail due to token scope or repository permissions.

Core Features & Use Cases

  • Fine-grained PAT setup: Configure repository-specific access and the required Contents and Workflows permissions.
  • Private repo clone and push: Use the correct GitHub token format to authenticate git operations against private repositories.
  • Troubleshooting auth failures: Diagnose common 403, 404, and workflow-scope errors in GitHub CLI, git, and API requests.
  • Non-interactive recovery: Use OAuth device flow guidance when browser-based or TTY-based auth refresh is unavailable.

Quick Start

Ask the Skill to help you configure GitHub token access for a private repository and troubleshoot any clone or push permission errors.

Frequently Asked Questions about github-pat-private-repos

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a fine-grained PAT for cloning a private GitHub repository?

A 403 error during git push usually indicates insufficient token scope or repository permissions. Diagnose GitHub authentication failures by checking if your PAT has the required Contents and Workflows permissions for the target private repository.

Can I use a classic OAuth token for git push and clone operations on private repos?

When browser-based or TTY-based GitHub authentication refresh is unavailable in non-interactive agent sessions, use the OAuth device flow fallback. This guidance helps recover authorization failures without requiring interactive login prompts.

Why does my GitHub CLI return a 404 error when accessing a private repository?

A 404 error when accessing a private repository often means your token lacks the correct repo-scoped permissions. Troubleshoot this GitHub authentication failure by verifying your token has the required Contents and Workflows permissions for the target repository.

Do I need workflow scope permissions to update workflows in a private GitHub repository?

Yes, updating workflows in a private GitHub repository requires workflow scope permissions. Configuring your PAT with the correct workflow scope handling ensures your git push and API requests for workflow updates succeed without 403 errors.