Exchange user credentials for test JWTs across Supabase, Auth0, Cognito, and OAuth2 endpoints.
npx skills add https://github.com/Elmanuel1/skills --skill get-test-token
Please help me install this Agent Skill. Skill: get-test-token Source: https://github.com/Elmanuel1/skills/tree/main/get-test-token Command: npx skills add https://github.com/Elmanuel1/skills --skill get-test-token
Manually writing boilerplate curl commands to exchange credentials for test JWTs is time-consuming and error-prone, especially when auth provider endpoints or response formats change. This Skill eliminates that repetitive work and centralizes all auth provider logic in one place, so test plans stay clean and up-to-date.
Use the get-test-token skill with the test user email [email protected] and corresponding password to generate a JWT for your staging Supabase environment.
High-intent search queries and answers about installing and using this skill.
Generate a test JWT by providing test user credentials to automatically exchange them for access tokens via Supabase, Auth0, Cognito, or OAuth2 endpoints. This eliminates manual boilerplate curl commands and centralizes authentication provider logic.
Yes, fetching tokens supports Auth0, Supabase, Cognito, and generic OAuth2 password-grant endpoints. It handles the credential exchange process across these multiple authentication providers for your staging or development environments.
Yes, you can decode JWT claims to verify user identity, expiry, issuer, and custom claims. This token validation feature ensures the generated access tokens are correct before executing authenticated API requests or test plans.
Avoid re-entering parameters by using per-project config persistence, which reads non-sensitive auth parameters from a local config file. This keeps authentication details ready for repeated API testing workflows without manual input.
The best way to automate authenticated requests is using a centralized token generation process that exchanges credentials for temporary access tokens. This keeps curl or Postman testing clean and up-to-date across changing auth provider endpoints.
Yes, the limitation is that test tokens apply strictly to staging and development environments. You should not use these generated access tokens for production authentication, as they are designed for temporary API testing workflows only.
diegolirioConfigure a Cloudflare MCP server and export credentials to shell profiles.
mnishanth02Access Clerk REST API endpoints to list users and manage organizations.
jhouserAutomate validation of authenticated API endpoints in the ActionPhase backend.
paarths-collabConnect Auth0 to a self-hosted Hermes agent over SSH.
