The Prompt BakeryTemplates and prompts

Fix · GitHub and Git

Token has the wrong permissions (403, resource not accessible)

Blocks your workSecurityNot checked against the vendor's current screens

What you may see

  • An automation or script says 403 or resource not accessible by personal access token
  • It says the token needs the workflow permission
  • A token that worked stopped working

Most likely cause

The token was created without the permission this action needs, it expired, or it was limited to other repositories.

Check first (about two minutes)

  1. Check on GitHub whether the token is expired or limited to certain repositories (the settings page for tokens, which may be labelled differently).
  2. Write down the ONE thing the token must do (read code, push code, edit workflows...).

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

  1. Ask me what exactly the token is used for and in which tool. Do not ask for the token itself.
  2. Tell me the smallest set of permissions for that job, and the settings page where I create a new token with a short expiry.
  3. Tell me where to store the new token (an environment variable or the tool's secret settings), then how to delete the old one on GitHub.
  4. Give me one harmless read-only call to test the new token.

Do not do this

  • Do not paste the token into chat, a screenshot or a file in the project.
  • Do not keep a token that never expires.
  • Do not widen the token to all permissions to "make it work".

Related

Try another entry

How can we help?

What do you need?
Your email, so we can reply (optional)Only enter your own email. We reply there.