This skill documents four PinMe auth proxy endpoints that a Worker written in TypeScript can call: create a user with email and password, verify an id token, fetch one user, and list users with paging. Each comes with request and error tables and a TypeScript example.
It also covers the frontend side, where Firebase Auth uses the public client config for email or Google sign-in, and a list of common mistakes such as treating a 403 as an expired token. The SKILL.md is written mostly in Chinese with English code.
What You Get
- TypeScript functions for create_user, verify_token, get user and list_users
- Error tables with HTTP status and message for each endpoint
- Firebase Auth frontend code for email and Google login that returns an id token
- A rule that the project API key stays in the Worker and never reaches the browser
- A list of common mistakes, such as 403 meaning an unverified email
Common Use Cases
- Adding email and password registration to a PinMe app
- Verifying a login token inside a Worker before serving protected data
- Paging through every user of a project
What Makes It Unique
It is limited to the PinMe auth proxy and spells out its quirks: a valid token with an unverified email returns 403, not 401, and a failed sign-up rolls back so no half-created account remains. It pairs with the main pinme skill for project setup.
Under The Hood
The skill gives the agent code for a Worker that calls the PinMe platform auth API over HTTPS with the project API key and project name. It does not run commands or scripts by itself. The agent writes Worker and frontend code in your project, and the API key must stay in Worker secrets, never in browser code. Sign-up triggers a verification email sent by the platform.