What problem does it solve?
Local development JWTs expire frequently and cause the browser-held token to return 401 on every API call, interrupting local testing and debugging workflows; this skill re-mints the token in place so development can continue without regenerating keypairs or restarting containers.
Core Features & Use Cases
- Safe in-place re-minting: Uses the existing RSA keypair to generate a new JWT and writes it to the local config file so running containers pick it up from the bind mount.
- Verification and smoke test: Decodes and displays the token expiry, performs an HTTP smoke test against the local API, and advises the developer how to update the browser token.
- Use Case: When the geto-web frontend gets 401 errors due to an expired dev token, run this to restore authenticated access without re-running initial setup.
Quick Start
Run the refresh-dev-token skill to re-mint the local development JWT using the existing keypair, verify the new expiry, and run the smoke test against the local API.