pinme-auth

Use when a PinMe project (Worker TypeScript) needs to integrate user authentication — creating email/password users, verifying id_tokens, querying user info, or listing users via Identity Platform auth proxy APIs.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, actionable integration guide with executable code, clear error handling, and well-sequenced call chains. The main gap is progressive disclosure: everything lives in one large file with no external references splitting the frontend material from the core Worker API reference.

Suggestions

Move the frontend Firebase Auth integration ("前端集成" section, ~60 lines) into a separate reference file (e.g. references/frontend-firebase.md) and link to it from a short overview, keeping SKILL.md focused on the Worker-side auth proxy APIs.

Consider extracting the shared TypeScript types (ApiEnvelope, UserInfo, VerifyTokenData) and the four API snippets into a bundled script/reference so the main body can stay a concise overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is dense and task-oriented — error tables, request/response types, and executable snippets with minimal prose — and explains only PinMe-specific behavior (auto-rollback, the 403 vs 401 distinction) rather than concepts Claude already knows.	3 / 3
Actionability	Each of the four APIs ships a complete, copy-paste-ready TypeScript function with the exact endpoint, headers, query params, and typed response handling, plus a pagination iterator and frontend Firebase example.	3 / 3
Workflow Clarity	Provides numbered call chains for email/password and Google flows, per-API error tables, an explicit success-check rule ("同时判断 resp.ok && result.code === 200"), and a pitfall checklist covering error recovery — matching the explicit-checkpoint anchor.	3 / 3
Progressive Disclosure	Sections are well-organized and there are no broken/nested references, but the file is a single monolithic ~360-line document with substantial inline content (notably the frontend Firebase integration block) that could be split into a one-level reference rather than kept inline.	2 / 3
	Total	11 / 12 Passed

Description

85%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, explicit trigger description that clearly states when to use it and lists concrete capabilities, distinguished by a tight PinMe/Identity Platform niche. The only weakness is jargon-heavy phrasing (auth proxy APIs, id_tokens) in the trigger terms.

Suggestions

Soften jargon in the trigger phrasing — e.g. add plain terms like "login", "verify login token", or "manage users" alongside "id_tokens" and "Identity Platform auth proxy APIs" to widen natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions — "creating email/password users, verifying id_tokens, querying user info, or listing users" — matching the anchor for listing several specific capabilities rather than vague language.	3 / 3
Completeness	Explicitly answers both halves: a "Use when a PinMe project ... needs to integrate user authentication" trigger (when) and an enumerated capability list (what), satisfying the top anchor for explicit what-and-when.	3 / 3
Trigger Term Quality	Includes relevant action terms a developer would say ("user authentication", "create users", "list users"), but is weighed down by technical jargon ("Identity Platform auth proxy APIs", "id_tokens") that is not the most natural phrasing; not quite the full natural-term coverage of the top anchor.	2 / 3
Distinctiveness Conflict Risk	Scoped tightly to "PinMe project (Worker TypeScript)" and "Identity Platform auth proxy APIs", a distinct niche unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: glitternetwork/pinme
Path: skills/pinme-auth/SKILL.md
Commit: 7822b05

Reviewed: 25 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.