auth-tool-cloudbase

Configure CloudBase authentication providers for login and registration flows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/eninem123/hunterclaw --skill auth-tool-cloudbase-eninem123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-tool-cloudbase
Source: https://github.com/eninem123/hunterclaw/tree/main/skills/cloudbase/references/auth-tool
Command: npx skills add https://github.com/eninem123/hunterclaw --skill auth-tool-cloudbase-eninem123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the guesswork of configuring CloudBase authentication providers by guiding you to first read the current login configuration and then enable or disable the exact login methods your app needs.

Core Features & Use Cases

  • Provider Setup & Enable/Disable: Configure authentication methods such as Anonymous, Username/Password, SMS, Email, WeChat Open Platform, and Google by updating CloudBase login config and providers.
  • Scenario-Driven Configuration: Follow targeted flows for each login type, including SMS verification configuration, email provider (Tencent email or custom SMTP), and WeChat provider credential wiring.
  • Activation for Platform Skills: Ensures the correct auth configuration is prepared before proceeding to the next platform-specific skill (auth-web, auth-wechat, or http-api).

Use case example: You want to ship a web app that supports phone OTP and email OTP; you can enable both providers first, then move on to implementing the Web login UI using the correct mappings.

Quick Start

Use the auth-tool-cloudbase skill to describe the current CloudBase login configuration, enable the required providers (for example SMS and Email), and then proceed to auth-web.

Frequently Asked Questions about auth-tool-cloudbase

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

FAQPage Schema
How do I configure CloudBase authentication providers for login and registration flows?

CloudBase authentication providers are configured by first reading the current login configuration and then enabling or disabling specific login methods via MCP callCloudApi actions using your EnvId. This updates provider states for your Web, mini program, or native app.

What authentication methods can I enable in CloudBase for my web app?

CloudBase supports enabling Anonymous, Username/Password, SMS, Email, WeChat Open Platform, and Google authentication methods. You can update these login configs and providers for your web app by applying targeted scenario-driven configuration flows.

How do I set up SMS OTP and email SMTP for CloudBase user authentication?

SMS OTP and email SMTP are set up by enabling the respective providers in CloudBase. You configure SMS verification settings and email provider credentials, choosing between Tencent email or a custom SMTP server for authentication flows.

Can I use this to prepare WeChat Open Platform login configuration for a mini program?

Yes, you can prepare WeChat Open Platform login configuration for a mini program by wiring WeChat provider credentials through CloudBase. This ensures the correct auth configuration is established before proceeding to auth-wechat implementation.

Do I need to fetch the current login configuration before enabling CloudBase auth providers?

Yes, you must fetch DescribeLoginConfig first to read the current login configuration before updating providers. This ensures you accurately enable or disable login methods via ModifyLoginConfig or ModifyProvider actions.

Why does my CloudBase auth provider configuration fail to apply to my backend?

CloudBase auth provider configuration may fail if the EnvId is incorrect or if DescribeLoginConfig was not fetched first. Ensure you use the correct EnvId as the CloudBase environment identifier and read the current state before modifying providers.