nix-github-api-auth

What problem does it solve? When running nix flake update or nix build, unauthenticated requests to api.github.com hit the 60 requests/hour IP rate limit, producing HTTP 403 errors and causing nix to silently fall back to cached flake inputs instead of updating them. ## Core Features & Use Cases - Symptom Diagnosis: Distinguish 403 rate-limit errors (unauthenticated) from 401 Bad credentials errors (invalid or malformed token) in nix output. - Private Token Configuration: Set up access-tokens via a 0600-permission file referenced by NIX_USER_CONF_FILES, keeping tokens out of git repositories and the nix store. - Anti-Pattern Catalog: Avoid documented pitfalls such as the nonexistent file: token syntax, trailing newlines in token files, home-manager pure evaluation blocking builtins.readFile, and misplaced --extra-config flags. - Use Case: Your nix flake update keeps printing "API rate limit exceeded" and "using cached version". This Skill walks you through extracting a token from gh auth token, writing a private nix config, and verifying end-to-end without polluting flake.lock. ## Quick Start Diagnose why my nix flake update shows GitHub API 403 rate limit errors and configure token authentication for it.