auth-tool-cloudbase

Verify and configure CloudBase authentication providers and login methods.

2|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/lxb031018/qintu --skill auth-tool-cloudbase-lxb031018
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-tool-cloudbase
Source: https://github.com/lxb031018/qintu/tree/main/.codebuddy/skills/auth-tool
Command: npx skills add https://github.com/lxb031018/qintu --skill auth-tool-cloudbase-lxb031018

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents failed or blocked authentication flows by helping you verify and configure CloudBase authentication provider readiness before implementing any login functionality.

Core Features & Use Cases

  • Provider status & login-method readiness: Check current login configuration and understand which login methods (anonymous, username/password, SMS, email, WeChat, Google) are enabled and usable.
  • Safe configuration changes: Use the correct CloudBase actions to inspect login strategy and update provider settings without reusing unwritable fields.
  • Cross-platform boundary guidance: Ensure you choose the correct downstream skill after provider-side readiness is confirmed (Web, mini program, Node server-side, or native/raw HTTP).

Quick Start

Use this skill to inspect your CloudBase env authentication configuration and enable the required providers and login methods before proceeding to the platform-specific auth implementation.

Frequently Asked Questions about auth-tool-cloudbase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which CloudBase authentication providers are enabled?

To check CloudBase authentication providers, use the login-config action with the correct EnvId to inspect current login configuration and verify which methods like SMS, email, or OAuth are enabled and usable.

What is the best way to configure SMS login in CloudBase?

The best way to configure SMS login in CloudBase is using provider configuration actions with correct EnvId scoping and safe payload construction to ensure the SMS provider is properly set up before client auth code is generated.

Why does my CloudBase email SMTP authentication fail?

CloudBase email SMTP authentication often fails due to misconfigured or disabled login methods. You must inspect the login strategy and update provider settings, ensuring unwritable fields are not reused in the payload.

Can I set up third-party OAuth providers in CloudBase without a publishable key?

No, setting up third-party OAuth providers in CloudBase requires publishable-key prerequisites. You must verify provider-side login readiness and configure the correct publishable keys before authentication flows can proceed.

Do I need to configure CloudBase auth providers before implementing client login code?

Yes, you must configure CloudBase auth providers first. Verifying provider readiness prevents failed authentication flows, ensuring you can then choose the correct downstream platform skill for Web, mini program, or Node implementations.

How do I safely update CloudBase login configuration without breaking existing flows?

To safely update CloudBase login configuration, use the correct CloudBase actions to inspect the login strategy and apply provider settings changes with safe payload construction, avoiding the reuse of unwritable fields.