CloudBase auth provider configuration and login-readiness guide. This skill should be used when users need to inspect, enable, disable, or configure auth providers, publishable-key prerequisites, login methods, SMS/email sender setup, or other provider-side readiness before implementing a client or backend auth flow.
SkillScore86Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/9/2026
What it changes
Passed 17 of 20 test cases with the skill, and 10 of 20 without it.
Without skill50%
With skill86%
Checks it passed that the model alone missed
References the relative path ../auth-nodejs-cloudbase/SKILL.md.
References the sibling skill file ../auth-web-cloudbase/SKILL.md.
References the relative path ../auth-wechat-miniprogram/SKILL.md.
and 6 more in the full report
9 fixed10 passed either way2 still failing1 broke
Pass-rate lift
+36 pp
Tokens
+7%
Agent turns
0%
Response time
-43%
Model gemini-3.6-flashMeasured 8/9/2026v219 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Which relative file path holds guidelines for backend Node.js custom ticket verification in CloudBase?
What was checked, without and with the skill
Checked
Without skill
With skill
References the relative path ../auth-nodejs-cloudbase/SKILL.md.
Missed
Passed
case-15 · 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.md78 lines2 files
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
The task is to inspect, enable, disable, or configure CloudBase auth providers, login methods, publishable key prerequisites, SMS/email delivery, or third-party login readiness.
An auth implementation cannot proceed until provider status and login configuration are confirmed.
A CloudBase Web auth flow needs provider verification before auth-web-cloudbase.
Native App / raw HTTP auth client -> ../http-api-cloudbase/SKILL.md
Do NOT use this as
The default implementation guide for every login or registration request.
A replacement for mini program native auth behavior when no provider change is involved.
A replacement for Node-side caller identity, user lookup, or custom login ticket flows.
A replacement for frontend integration, session handling, or client UX implementation.
Common mistakes / gotchas
Writing login UI before enabling the required provider.
Treating any mention of "auth" as a provider-management task.
Implementing Web login in cloud functions.
Routing native App auth to Web SDK flows.
Making configuration or code changes without first following the Change Safety Protocol (cloudbase-platform/references/protocols/change-safety-protocol.md).