A skill your agent uses when a PinMe project (Worker TypeScript) needs to integrate user authentication — creating email/password users, verifying idtokens, querying user info, or listing users via…
$ npx skills add glitternetwork/pinme --skill pinme-auth -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install glitternetwork/pinme pinme-auth --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/glitternetwork/pinme.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pinme-auth .claude/skills/pinme-auth && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pinme-auth" agent skill from https://github.com/glitternetwork/pinme/tree/main/skills/pinme-auth into .claude/skills/pinme-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinme-auth", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/glitternetwork/pinme/tree/main/skills/pinme-authType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add glitternetwork/pinme --skill pinme-auth -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install glitternetwork/pinme pinme-auth --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glitternetwork/pinme.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pinme-auth .agents/skills/pinme-auth && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pinme-auth" agent skill from https://github.com/glitternetwork/pinme/tree/main/skills/pinme-auth into .agents/skills/pinme-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinme-auth", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add glitternetwork/pinme --skill pinme-auth -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install glitternetwork/pinme pinme-auth --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glitternetwork/pinme.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pinme-auth .cursor/skills/pinme-auth && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pinme-auth" agent skill from https://github.com/glitternetwork/pinme/tree/main/skills/pinme-auth into .cursor/skills/pinme-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinme-auth", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/glitternetwork/pinme.git --path skills/pinme-auth--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add glitternetwork/pinme --skill pinme-auth -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install glitternetwork/pinme pinme-auth --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glitternetwork/pinme.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pinme-auth .gemini/skills/pinme-auth && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pinme-auth" agent skill from https://github.com/glitternetwork/pinme/tree/main/skills/pinme-auth into .gemini/skills/pinme-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinme-auth", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install glitternetwork/pinme pinme-authInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add glitternetwork/pinme --skill pinme-auth -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/glitternetwork/pinme.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pinme-auth .github/skills/pinme-auth && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pinme-auth" agent skill from https://github.com/glitternetwork/pinme/tree/main/skills/pinme-auth into .github/skills/pinme-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinme-auth", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add glitternetwork/pinme --skill pinme-auth -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install glitternetwork/pinme pinme-auth --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glitternetwork/pinme.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pinme-auth .opencode/skills/pinme-auth && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pinme-auth" agent skill from https://github.com/glitternetwork/pinme/tree/main/skills/pinme-auth into .opencode/skills/pinme-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinme-auth", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
pinme-authA skill your agent uses when a PinMe project (Worker TypeScript) needs to integrate user authentication — creating email/password users, verifying idtokens, querying user info, or listing users via…
Pinme Auth is an agent skill from glitternetwork/pinme. Use when a PinMe project (Worker TypeScript) needs to integrate user authentication — creating email/password users, verifying idtokens, querying user info, or listing users via Identity Platform auth proxy APIs.
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs. It works with TypeScript. The repository describes itself as: Deploy Your Frontend in a Single Command. Claude Code Skills supported. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 7822b05. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and json).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
pinme.cloudFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pinme Auth loads about 2.6k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 376 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from glitternetwork/pinme at commit 7822b05, republished under its MIT licence (© glitternetwork). 376 words, ~2,561 tokens.
.claude/skills/pinme-auth/SKILL.md (or your agent's skills folder).Guides how to call PinMe platform's Identity Platform auth proxy APIs in a PinMe Worker (TypeScript).
// backend/src/worker.ts
export interface Env {
DB: D1Database;
API_KEY: string; // 项目 API Key — 用于所有 auth 接口认证
PROJECT_NAME: string; // 项目名 — 所有 auth 接口必须同时传递
BASE_URL?: string; // 可选，默认 https://pinme.cloud
}
API_KEY和PROJECT_NAME是所有 auth 接口的必填凭证，缺一不可。
| 参数 | 传递方式 | 必填 | 说明 |
|---|---|---|---|
X-API-Key | 请求头 | 是 | 项目 API Key |
project_name | Query 参数 | 是 | 必须与 X-API-Key 对应同一个项目 |
服务端会先校验这两个字段是否匹配同一个项目，再从项目配置中取出 tenant_id，然后转调 Identity Platform。
| 场景 | HTTP | data.error |
|---|---|---|
缺少 X-API-Key | 401 | X-API-Key header is required |
缺少 project_name | 400 | project_name is required |
| API Key 和项目不匹配 | 401 | Invalid API key or project name |
| 项目未配置认证租户 | 400 | Auth service not configured for this project |
type ApiEnvelope<T> = {
code: number // 200=成功，其他=失败
msg: string // "ok" | "fail" | "invalid param"
data: T
}
type ApiErrorData = { error?: string }
type UserInfo = {
uid: string
email: string
display_name: string
photo_url?: string
disabled: boolean
email_verified: boolean
}Endpoint: POST {BASE_URL}/api/v1/auth/create_user?project_name={project_name}
仅用于邮箱密码注册。成功时用户已创建且验证邮件已发出；失败时自动回滚，不会留下僵尸账号。
创建成功后用户默认仍是"未验证"状态，需点击邮件验证链接后，
verify_token才能通过校验。
{ "email": "alice@example.com", "password": "Test@12345678", "display_name": "Alice" }| 字段 | 类型 | 必填 |
|---|---|---|
email | string | 是 |
password | string | 是 |
display_name | string | 否 |
| 场景 | HTTP | data.error |
|---|---|---|
| 缺少 email/password | 400 | email and password are required |
| 上游创建失败 | 502 | Failed to create user |
| 发送验证邮件失败 | 500 | Failed to send verification email. Please try again. |
async function createAuthUser(
env: Env,
payload: { email: string; password: string; display_name?: string }
): Promise<{ user?: UserInfo; error?: string }> {
const baseUrl = env.BASE_URL ?? 'https://pinme.cloud';
const resp = await fetch(
`${baseUrl}/api/v1/auth/create_user?project_name=${encodeURIComponent(env.PROJECT_NAME)}`,
{
method: 'POST',
headers: { 'X-API-Key': env.API_KEY, 'Content-Type': 'application/json' },
body: JSON.stringify(payload),
}
);
const result = await resp.json() as ApiEnvelope<UserInfo | ApiErrorData>;
if (!resp.ok || result.code !== 200) {
return { error: (result.data as ApiErrorData)?.error ?? result.msg };
}
return { user: result.data as UserInfo };
}Endpoint: POST {BASE_URL}/api/v1/auth/verify_token?project_name={project_name}
校验前端登录后拿到的 id_token（邮箱密码或 Google 登录均适用）。
注意： token 合法但邮箱未验证时返回 403，不是 401。
{ "id_token": "eyJhbGciOiJSUzI1NiIsImtpZCI6..." }type VerifyTokenData = {
uid: string
email?: string
tenant_id: string
claims: Record<string, unknown>
}| 场景 | HTTP | data.error |
|---|---|---|
缺少 id_token | 400 | id_token is required |
| token 无效或过期 | 401 | Invalid or expired token |
| 邮箱未验证 | 403 | Email not verified. Please check your inbox and verify your email address. |
async function verifyAuthToken(
env: Env,
idToken: string
): Promise<{ uid?: string; email?: string; error?: string; emailNotVerified?: boolean }> {
const baseUrl = env.BASE_URL ?? 'https://pinme.cloud';
const resp = await fetch(
`${baseUrl}/api/v1/auth/verify_token?project_name=${encodeURIComponent(env.PROJECT_NAME)}`,
{
method: 'POST',
headers: { 'X-API-Key': env.API_KEY, 'Content-Type': 'application/json' },
body: JSON.stringify({ id_token: idToken }),
}
);
const result = await resp.json() as ApiEnvelope<VerifyTokenData | ApiErrorData>;
if (!resp.ok || result.code !== 200) {
const error = (result.data as ApiErrorData)?.error ?? result.msg;
return { error, emailNotVerified: resp.status === 403 };
}
const data = result.data as VerifyTokenData;
return { uid: data.uid, email: data.email };
}Endpoint: GET {BASE_URL}/api/v1/auth/user?project_name={project_name}&uid={uid}
| 场景 | HTTP | data.error |
|---|---|---|
缺少 uid | 400 | uid is required |
| 用户不存在 | 404 | User not found |
| 上游查询失败 | 502 | Failed to get user |
async function getAuthUser(env: Env, uid: string): Promise<{ user?: UserInfo; error?: string }> {
const baseUrl = env.BASE_URL ?? 'https://pinme.cloud';
const resp = await fetch(
`${baseUrl}/api/v1/auth/user?project_name=${encodeURIComponent(env.PROJECT_NAME)}&uid=${encodeURIComponent(uid)}`,
{ method: 'GET', headers: { 'X-API-Key': env.API_KEY } }
);
const result = await resp.json() as ApiEnvelope<UserInfo | ApiErrorData>;
if (!resp.ok || result.code !== 200) {
return { error: (result.data as ApiErrorData)?.error ?? result.msg };
}
return { user: result.data as UserInfo };
}Endpoint: GET {BASE_URL}/api/v1/auth/list_users?project_name={project_name}
默认 max_results=100，最大 1000。通过 next_page_token 循环翻页。
| 参数 | 必填 | 说明 |
|---|---|---|
project_name | 是 | 项目名 |
page_token | 否 | 分页游标 |
max_results | 否 | 每页数量，1–1000 |
async function listAuthUsers(
env: Env,
options: { pageToken?: string; maxResults?: number } = {}
): Promise<{ users?: UserInfo[]; nextPageToken?: string; error?: string }> {
const baseUrl = env.BASE_URL ?? 'https://pinme.cloud';
const url = new URL('/api/v1/auth/list_users', baseUrl);
url.searchParams.set('project_name', env.PROJECT_NAME);
if (options.pageToken) url.searchParams.set('page_token', options.pageToken);
if (options.maxResults) url.searchParams.set('max_results', String(options.maxResults));
const resp = await fetch(url.toString(), { method: 'GET', headers: { 'X-API-Key': env.API_KEY } });
const result = await resp.json() as ApiEnvelope<{ users: UserInfo[]; next_page_token?: string } | ApiErrorData>;
if (!resp.ok || result.code !== 200) {
return { error: (result.data as ApiErrorData)?.error ?? result.msg };
}
const data = result.data as { users: UserInfo[]; next_page_token?: string };
return { users: data.users, nextPageToken: data.next_page_token };
}
// 批量遍历所有用户示例
async function* iterAllUsers(env: Env) {
let pageToken: string | undefined;
do {
const { users, nextPageToken, error } = await listAuthUsers(env, { pageToken, maxResults: 1000 });
if (error) throw new Error(error);
for (const user of users ?? []) yield user;
pageToken = nextPageToken;
} while (pageToken);
}create_worker 响应中包含 public_client_config，前端用它初始化 Firebase Auth SDK。
| 字段 | 用途 | 是否可暴露到浏览器 |
|---|---|---|
data.api_key | 项目 API Key，调用本文所有代理接口 | 不能，只给 Worker/服务端 |
data.public_client_config.auth_api_key | Firebase Web API Key，初始化前端登录 SDK | 可以 |
| 字段 | 前端用途 |
|---|---|
public_client_config.auth_api_key | initializeApp({ apiKey }) |
public_client_config.auth_domain | initializeApp({ authDomain }) |
public_client_config.auth_project_id | initializeApp({ projectId }) |
public_client_config.tenant_id | auth.tenantId = config.tenant_id（必须设置，否则 token 归属错误） |
import { initializeApp } from 'firebase/app'
import {
type Auth,
getAuth,
GoogleAuthProvider,
signInWithEmailAndPassword,
signInWithPopup,
} from 'firebase/auth'
type PublicClientConfig = {
tenant_id: string
auth_api_key: string
auth_domain: string
auth_project_id: string
}
export function createProjectAuth(config: PublicClientConfig): Auth {
const app = initializeApp({
apiKey: config.auth_api_key,
authDomain: config.auth_domain,
projectId: config.auth_project_id,
})
const auth = getAuth(app)
auth.tenantId = config.tenant_id // 必须设置，确保 token 归属正确租户
return auth
}
// 邮箱密码登录，返回 id_token
export async function loginWithEmail(auth: Auth, email: string, password: string): Promise<string> {
const credential = await signInWithEmailAndPassword(auth, email, password)
return credential.user.getIdToken()
}
// Google 登录，返回 id_token
export async function loginWithGoogle(auth: Auth): Promise<string> {
const credential = await signInWithPopup(auth, new GoogleAuthProvider())
return credential.user.getIdToken()
}
// 用法示例
// pinme create 会自动将 public_client_config 写入 frontend/src/utils/config.ts
import { public_client_config } from '../utils/config'
const auth = createProjectAuth(public_client_config)
const idToken = await loginWithGoogle(auth)
// 然后把 idToken 发给自己的 Worker，由 Worker 调用 verify_token前端只负责登录和拿
id_token，不要直接持有项目api_key。verify_token必须由 Worker/服务端代调。frontend/src/utils/config.ts由pinme create自动生成，无需手动创建。
邮箱密码注册流程：
create_user → 创建用户并发出验证邮件id_tokenverify_token → 校验 token，取得 uidgetAuthUser 读取完整用户信息Google 登录流程：
id_tokenverify_token → 校验 token（无需调用 create_user）| 错误 | 正确做法 |
|---|---|
只传 X-API-Key，忘记 project_name | 每个请求都要同时带 X-API-Key header 和 project_name query |
verify_token 返回 403 时当 token 失效处理 | 403 = 邮箱未验证，提示用户检查邮箱；401 才是 token 失效 |
create_user 成功就认为邮箱已验证 | 创建成功只代表验证邮件已发，用户必须点击后才算验证 |
list_users 只取第一页 | 有 next_page_token 时需继续请求，直到为空 |
成功判断只看 resp.ok | 同时判断 resp.ok && result.code === 200 |
© glitternetwork, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/pinme-auth of glitternetwork/pinme.
Open the folder on GitHubat commit 7822b05
Pinme Auth next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pinme Auth this skillglitternetwork/pinme | 3.7k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Node Backend Development Guidelinesdiet103/claude-code-infrastructure-showcase | 10k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| cmux Backend Rulesmanaflow-ai/cmux | 28k | 1 repos | ~682 | Automated safety check: Pass | Custom licence | |
| Payloadpayloadcms/payload | 45k | 5 repos | ~6.2k | Automated safety check: Pass | MIT | |
| Better Auth Best Practiceslatitude-dev/latitude-llm | 4.7k | 7 repos | ~1.6k | Automated safety check: Pass | MIT |
diet103/claude-code-infrastructure-showcase
Sets layered architecture and coding rules for Node.js, Express and TypeScript microservices, covering routes, controllers, services, repositories, Prisma, Sentry and Zod.
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
manaflow-ai/cmux
Sets the backend TypeScript and Cloud VM rules for cmux: Effect-based services, thin route handlers, Postgres as source of truth, migrations and provider secrets.
payloadcms/payload
A skill your agent uses when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API).
latitude-dev/latitude-llm
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.
twentyhq/twenty
Contributor guide for step three of adding a syncable entity to the Twenty server: write the validator, the migration action builder and the orchestrator wiring.
glitternetwork/pinme
A skill your agent uses when a PinMe project (Worker TypeScript) needs to call OpenRouter-backed LLM APIs, including models, chat/completions, streaming, or OpenRouter web search.
glitternetwork/pinme
A skill your agent uses when the user mentions "pinme", or needs to upload files, store to IPFS, create/publish/deploy websites or full-stack services (including frontend pages, backend APIs…
glitternetwork/pinme
A skill your agent uses when a PinMe project (Worker TypeScript) needs to integrate email sending (sendemail).
glitternetwork/pinme
A skill your agent uses when a PinMe Cloudflare Worker needs R2 object storage, including secure file or image upload, streaming download, metadata lookup, deletion, listing, Range requests, or…
glitternetwork/pinme
A skill your agent uses when generating, modifying, or reviewing PinMe Worker (Cloudflare Worker TypeScript) code that accepts payments through UniwebPay — payment links, products/prices, checkout…
glitternetwork/pinme
A skill your agent uses when the user wants to share, publish, or upload a static result through PinMe, especially by generating a static HTML share page for a PinMe project link, deployed…
Works with
Categories
A skill your agent uses when a PinMe project (Worker TypeScript) needs to integrate user authentication — creating email/password users, verifying idtokens, querying user info, or listing users via…. Pinme Auth is an agent skill from glitternetwork/pinme. Use when a PinMe project (Worker TypeScript) needs to integrate user authentication — creating email/password users, verifying idtokens, querying user info, or listing users via Identity Platform auth proxy APIs.
Pinme Auth fits situations like: A PinMe project (Worker TypeScript) needs to integrate user authentication — creating email/password users; verifying idtokens; querying user info; listing users via Identity Platform auth proxy APIs.
Run `npx skills add glitternetwork/pinme --skill pinme-auth -a claude-code`. Or copy the skill folder (skills/pinme-auth in glitternetwork/pinme) into .claude/skills/pinme-auth in your project. Claude Code loads it when a task matches its description.
Run `npx skills add glitternetwork/pinme --skill pinme-auth -a codex`. Or copy the skill folder (skills/pinme-auth in glitternetwork/pinme) into .agents/skills/pinme-auth in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add glitternetwork/pinme --skill pinme-auth -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pinme-auth, .gemini/skills/pinme-auth, .github/skills/pinme-auth and .opencode/skills/pinme-auth in your project.
Going by SKILL.md and its folder, Pinme Auth needs credentials named API_KEY. Our summary lists: A credential in API_KEY.
SKILL.md names 1 domain. In commands or code: pinme.cloud; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Pinme Auth is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pinme Auth: Node Backend Development Guidelines (diet103/claude-code-infrastructure-showcase, 10k stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars), cmux Backend Rules (manaflow-ai/cmux, 28k stars) and Payload (payloadcms/payload, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
glitternetwork (a GitHub organization) maintains it in glitternetwork/pinme, which has 3,746 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 12, 2026.
Source: glitternetwork/pinme on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
