- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/HEAD/config/.claude/skills/auth-tool-cloudbaseDe l'éditeur
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.
auth-web-cloudbase.../auth-web-cloudbase/SKILL.md../auth-wechat-miniprogram/SKILL.md../auth-nodejs-cloudbase/SKILL.md../http-api-cloudbase/SKILL.mdcloudbase-platform/references/protocols/change-safety-protocol.md).accessKey alone does not create a gateway-authenticated anonymous session. With @cloudbase/js-sdk 3.x, enable anonymous via this skill when needed, then clients must call await auth.signInAnonymously() (or an equivalent authenticated session) before NoSQL app.database() CRUD — otherwise the gateway returns 401. For apps that require verified login (e.g. admin panels), enforce AuthGuard / RLS and reject is_anonymous rather than relying on the login strategy toggle alone.Configure CloudBase authentication providers: Anonymous, Username/Password, SMS, Email, WeChat, Google, and more.
Default login path: use email verification-code login to get a login flow working. Phone SMS login requires the user to bring their own SMS provider — enabling patch.phone = true alone will not deliver codes. Point the user to https://docs.cloudbase.net/authentication-v2/auth/custom-sms-provider for the SMS channel setup (the guide also covers other SMS providers through a cloud function). See references/extended-guide.md §4.
Prerequisites: CloudBase environment ID (env)
Keep these two auth domains separate:
auth: MCP / management-side login only. Use it for status, start_auth, set_env, logout, and get_temp_credentials.queryAppAuth / manageAppAuth: app-side authentication configuration. Use them for login methods, provider settings, publishable key, static domain, client config, and custom login keys.Preferred execution order for this skill:
queryAppAuth / manageAppAuth first when the needed action exists there.callCloudApi only as a fallback or for debugging raw request shapes.auth tool.Read this before telling a user to "re-authorize" after a permission-shaped failure. Re-authorizing does not widen a key's scope; it just issues the same scope again.
auth(status) → credential_scope: account): reaches control-plane APIs, subject to that identity's own CAM policies.credential_scope: single_env): scoped to one environment's data plane plus the fixed TCB policies. It is not an account-level credential, so control-plane calls outside that scope fail, and there is no channel to attach additional CAM policies to a single key — issuing the key again changes nothing. When a task needs a capability the current credential cannot have, switch to an account-level login or follow the role route rather than retrying the same key.Full identity table and how to grant what is missing: ../../cloud-api-operations/references/calling-methods.md.
For detailed scenarios, examples, and patterns, read extended-guide.md.
All packaged reference files (required for skill lint reachability):
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, logi
---name: auth-tool-cloudbasedescription: CloudBase auth provider configuration and login-readiness guide. This skill should be used when users need to…---# config/.claude/skills/auth-tool-cloudbase/SKILL.mdVue d'ensemble
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.
FAQ
Téléchargez config/.claude/skills/auth-tool-cloudbase/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.