permissioned-github

Requests user permissions for restricted GitHub operations using gh CLI and git commands.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill permissioned-github-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: permissioned-github
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/permissioned-github
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill permissioned-github-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents operating in sandboxed environments are restricted to a subset of GitHub actions, causing commands to fail without a clear recovery path. This Skill defines a structured permission format and workflow so the agent can request exactly the access it needs from the user when a GitHub command is denied. ## Core Features & Use Cases - Structured Permission Format: Defines a command.action(resource_json) syntax covering PRs, issues, and branches with read, create, update, approve, merge, and delete actions. - gh CLI and git Governance: Establishes authoritative rules for using the gh CLI with -R ORG/REPO and git for branch operations, forbidding curl or direct API scripts. - Least-Privilege Requests: Provides 11 worked examples showing how to construct lean permission strings for tasks like creating issues, approving PRs, pushing branches, and searching commits. - Use Case: An agent tries gh pr comment 123 -R myorg/myrepo and the command fails due to sandbox restrictions. The agent constructs gh.update({"org": "myorg", "repo": "myrepo", "pr": "123"}), calls the ask_permission tool, and retries the command after the user grants access. ## Quick Start Ask the agent to comment on a pull request or push a branch, and it will request the matching GitHub permission from you if the command is blocked.

Frequently Asked Questions about permissioned-github

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

FAQPage Schema
How do I request GitHub permissions when a gh command fails?

Construct a permission string in the format command.action(resource_json), such as gh.update({"org": "myorg", "repo": "myrepo", "pr": "123"}), then call the ask_permission tool with Action set to custom and Target set to that string before retrying the command.

What permission format is used for git push operations?

Use git.create for pushing a branch that does not yet exist on the remote and git.update for pushing to an existing branch, including force-pushes. Both require org, repo, and branch fields in the resource JSON.

Can I use curl or scripts to call the GitHub API instead of gh CLI?

No. The skill mandates the gh CLI with the -R ORG/REPO argument for all GitHub interactions and git for branch operations. Direct API scripts and curl commands are explicitly forbidden.

When should the agent ask for GitHub permissions?

Only after a command has actually failed due to restrictions. Each permission request prompts the user, so asking preemptively degrades the experience. The agent should run the command first and request access only on failure.

What GitHub actions are not supported by the permission system?

Only PR, issue, and branch actions listed in the format are supported: read, create, update, approve, merge, and delete where applicable. Any other operation will not be granted, and the agent must stop and explain the limitation.