CloudBase Node SDK auth guide for server-side identity, user lookup, and custom login tickets. This skill should be used when Node.js code must read caller identity, inspect end users, or bridge an existing user system into CloudBase; not when configuring providers or building client login UI.
SkillScore82Maintained
Automatic
◆Coding pack
Last verified 8/9/2026
What it changes
Passed 18 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill82%
Checks it passed that the model alone missed
Calls auth.getUserInfo()
Calls auth.queryUserInfo()
Calls auth.getEndUserInfo('user-123')
and 23 more in the full report
15 fixed3 passed either way4 still failing0 broke
Pass-rate lift
+68 pp
Tokens
+148%
Agent turns
0%
Response time
-49%
Model gemini-3.6-flashMeasured 8/9/2026v218 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 15
Prompt
I am generating a custom login ticket in my CloudBase Node backend. I want to use a 3-character customUserId. Is this allowed, and what are the length constraints?
What was checked, without and with the skill
Checked
Without skill
With skill
States that a 3-character ID is not allowed
Missed
Passed
Specifies the length constraint is 4 to 32 characters
Missed
Passed
case-22 · gemini-3.6-flash · 8/9/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md438 linessingle file
Sibling skills (local only)
Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../auth-tool-cloudbase/SKILL.md.
If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do not HTTP-fetch remote skill or protocol markdown into the agent context.
Activation Contract
Use this first when
Node.js code in cloud functions or backend services must read caller identity, look up users, or issue custom login tickets.
The backend responsibility is auth / identity, not provider setup or frontend login UI.
Read before writing code if
The task mentions @cloudbase/node-sdk, server-side auth, custom login tickets, or "who is calling".
The request mixes frontend login with backend identity logic; split the flow and route client-side work elsewhere.
Web login UI that consumes custom tickets -> ../auth-web-cloudbase/SKILL.md
Raw HTTP auth client -> ../http-api-cloudbase/SKILL.md
Do NOT use for
Provider enable/disable or login console configuration.
Frontend login / sign-up UI.
Mini program native auth.
Common mistakes / gotchas
Using this skill as the entry point for every auth request.
Mixing provider-management work with Node-side identity code.
Reaching for raw HTTP examples when Node SDK already covers the job.
When to use this skill
Use this skill whenever the task involves server-side authentication or identity in a CloudBase project, and the code is running in Node.js, for example: