auth-tool-cloudbase
Configure and verify CloudBase authentication providers before implementing application login flows.
Install
mkdir -p .claude/skills/auth-tool-cloudbase && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4146" && unzip -o skill.zip -d .claude/skills/auth-tool-cloudbase && rm skill.zipInstalls to .claude/skills/auth-tool-cloudbase
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Enable or disable specific login providers
- →Retrieve publishable keys for auth configuration
- →Verify SMS/email delivery settings
- →Audit third-party provider credentials
How it works
It performs an inspection and configuration routine against the CloudBase backend to ensure all necessary auth infrastructure is initialized.
Inputs & outputs
When to use auth-tool-cloudbase
- →Enable OAuth or SAML login methods
- →Configure SMS or email sender settings
- →Verify publishable key requirements
- →Check provider availability before app deployment
About auth-tool-cloudbase
This skill enables developers to inspect, enable, and configure authentication providers within the CloudBase environment. It ensures all prerequisites, such as publishable keys and messaging configurations, are met before implementing client-side auth code.
Use CloudBase Auth tool to configure and manage authentication providers for web applications - enable/disable login methods (SMS, Email, WeChat Open Platform, Google, Anonymous, Username/password, OAuth, SAML, CAS, Dingding, etc.) and configure provider settings via MCP tools `callCloudApi`.
When not to use it
- →For actual login implementation or user data handling
- →If the goal is to write frontend auth logic
Prerequisites
Limitations
- →Requires administrative environment access
- →Changes take effect on the cloud backend
How it compares
It focuses on the control-plane configuration of security providers before any application-level auth code is executed.
Compared to similar skills
auth-tool-cloudbase side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| auth-tool-cloudbase (this skill) | 1 | 2mo | No flags | Beginner |
| springboot-security | 5 | 5mo | No flags | Intermediate |
| django-security | 5 | 5mo | Review | Intermediate |
| middleware-protection | 1 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by TencentCloudBase
View all by TencentCloudBase →You might also like
springboot-security
affaan-m
Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.
django-security
affaan-m
Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.
middleware-protection
dadbodgeoff
Protect routes with Next.js middleware. Check authentication once, protect routes declaratively. Supports public routes, protected routes, and role-based access.
cognito
itsmostafa
AWS Cognito user authentication and authorization service. Use when setting up user pools, configuring identity pools, implementing OAuth flows, managing user attributes, or integrating with social identity providers.
security-hardening
boctulus
Security best practices for SimpleRest including JWT configuration, ACL hardening, input sanitization, CSRF protection, and encryption.
configuration-sso-app
greenpau
caddy-security SSO app Caddyfile configuration for Single Sign-On with SAML. Use when creating, reviewing, or modifying sso provider blocks, AWS SAML app drivers, SAML entity IDs, signing certificates, PKCS8 private keys, SSO metadata locations, authentication portal enablement, /apps/sso endpoints,