gh

A 'Resource not accessible by personal access token' 403 error during GitHub org repo creation means your fine-grained PAT lacks the precise repository-administration permissions. You must probe and verify the token's capabilities using the GH CLI and curl before attempting provisioning.

To apply organization-level rulesets for branch protection, use the gh CLI to target your org and enforce protections on main, staging, and prod branches. This Skill automates ruleset application while detecting if your GitHub plan requires a Team tier upgrade.

Yes, applying organization-level rulesets for branch protection often requires a GitHub Team plan. This Skill detects plan gating requirements during ruleset application and triages any related access failures to ensure your branch protection rules apply successfully.

The best way to automate idempotent private repo creation in a GitHub org is using the gh CLI with safe defaults to create new repositories or skip existing ones. This prevents duplicate repos and ensures non-destructive provisioning for your automation workflows.

You can check your fine-grained personal access token's repo management permissions by running a non-destructive capability probe. This Skill uses python3, curl, and the GH CLI to verify token access and diagnose 403 errors before you attempt org-level changes.