Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
CloudBase auth provider configuration and login-readiness guide.
Install Auth Tool Cloudbase
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit auth-tool-cloudbase --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/config/source/skills/auth-tool-cloudbase .claude/skills/auth-tool-cloudbase && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "auth-tool-cloudbase" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/config/source/skills/auth-tool-cloudbase into .claude/skills/auth-tool-cloudbase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auth-tool-cloudbase", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/config/source/skills/auth-tool-cloudbaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit auth-tool-cloudbase --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/config/source/skills/auth-tool-cloudbase .agents/skills/auth-tool-cloudbase && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "auth-tool-cloudbase" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/config/source/skills/auth-tool-cloudbase into .agents/skills/auth-tool-cloudbase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auth-tool-cloudbase", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit auth-tool-cloudbase --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/config/source/skills/auth-tool-cloudbase .cursor/skills/auth-tool-cloudbase && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "auth-tool-cloudbase" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/config/source/skills/auth-tool-cloudbase into .cursor/skills/auth-tool-cloudbase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auth-tool-cloudbase", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git --path config/source/skills/auth-tool-cloudbase--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit auth-tool-cloudbase --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/config/source/skills/auth-tool-cloudbase .gemini/skills/auth-tool-cloudbase && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "auth-tool-cloudbase" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/config/source/skills/auth-tool-cloudbase into .gemini/skills/auth-tool-cloudbase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auth-tool-cloudbase", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit auth-tool-cloudbaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/config/source/skills/auth-tool-cloudbase .github/skills/auth-tool-cloudbase && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "auth-tool-cloudbase" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/config/source/skills/auth-tool-cloudbase into .github/skills/auth-tool-cloudbase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auth-tool-cloudbase", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TencentCloudBase/CloudBase-AI-Toolkit auth-tool-cloudbase --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/config/source/skills/auth-tool-cloudbase .opencode/skills/auth-tool-cloudbase && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "auth-tool-cloudbase" agent skill from https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/config/source/skills/auth-tool-cloudbase into .opencode/skills/auth-tool-cloudbase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auth-tool-cloudbase", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
auth-tool-cloudbase- GitHub stars
- 1.1k
- Used in
- 2 other repos
- Token cost
- ~1.2k tokens
- SKILL.md length
- 538 words
- Files
- 3 (incl. references)
- Skills in repo
- 49
- Repo updated
- First seen
- Licence
- MIT
At a glance
CloudBase auth provider configuration and login-readiness guide.
- Works in 4 steps: Use queryAppAuth / manageAppAuth first… → Use callCloudApi only as a fallback or… → Do not route app-side provider… → …
- Tasks that involve Authentication
- SKILL.md covers Sibling skills (local only), Activation Contract, Overview and MCP Tool Boundary, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Auth Tool Cloudbase is an agent skill from TencentCloudBase/CloudBase-AI-Toolkit. 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.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `checklist.md` and `references/extended-guide.md`).
It sits in Backend & APIs, covering Authentication. The repository describes itself as: Backend for AI coding agents on CloudBase — database, auth, functions via Plugin, Skills & MCP. The licence is MIT.
When your agent uses it
- Tasks that involve Authentication
Example prompts
- “/auth-tool-cloudbase”
Requirements
- Node.js
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Use queryAppAuth / manageAppAuth first when the needed action exists there.
- Use callCloudApi only as a fallback or for debugging raw request shapes.
- Do not route app-side provider configuration back to the MCP auth tool.
- In existing projects with active login and register handlers, stop revisiting provider setup after the required login method and…
What it can do on your machine
Read from SKILL.md and the folder at commit ea2c202. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Auth Tool Cloudbase loads about 1.2k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 538 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from TencentCloudBase/CloudBase-AI-Toolkit at commit ea2c202, republished under its MIT licence (© TencentCloudBase). 538 words, ~1,187 tokens.
Download SKILL.mdSave it as
.claude/skills/auth-tool-cloudbase/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- auth-tool-cloudbase
- description
- 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.
- version
- 2.34.8
- alwaysApply
- false
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.
Read before writing code if
- The request mentions provider setup, auth console configuration, publishable key retrieval, login method availability, SMS/email sender setup, or third-party provider credentials.
- The task mixes provider configuration with Web, mini program, Node, or raw HTTP auth implementation.
Then also read
- Web auth UI ->
../auth-web-cloudbase/SKILL.md - Mini program native auth ->
../auth-wechat-miniprogram/SKILL.md - Node server-side identity / custom ticket ->
../auth-nodejs-cloudbase/SKILL.md - 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). - In an existing application, looping on provider queries after readiness is already known instead of wiring the active login and register handlers.
Show full SKILL.md (244 more words)Show less
Minimal checklist
- Read Authentication Activation Checklist before auth implementation.
- Anonymous login is disabled by default. Publishable
accessKeyalone does not create a gateway-authenticated anonymous session. With@cloudbase/js-sdk3.x, enable anonymous via this skill when needed, then clients must callawait auth.signInAnonymously()(or an equivalent authenticated session) before NoSQLapp.database()CRUD — otherwise the gateway returns 401. For apps that require verified login (e.g. admin panels), enforce AuthGuard / RLS and rejectis_anonymousrather than relying on the login strategy toggle alone.
Overview
Configure CloudBase authentication providers: Anonymous, Username/Password, SMS, Email, WeChat, Google, and more.
Prerequisites: CloudBase environment ID (env)
MCP Tool Boundary
Keep these two auth domains separate:
auth: MCP / management-side login only. Use it forstatus,start_auth,set_env,logout, andget_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:
- Use
queryAppAuth/manageAppAuthfirst when the needed action exists there. - Use
callCloudApionly as a fallback or for debugging raw request shapes. - Do not route app-side provider configuration back to the MCP
authtool. - In existing projects with active login and register handlers, stop revisiting provider setup after the required login method and publishable key are confirmed. Move back to the active frontend handler and finish the actual user flow.
Extended guide
For detailed scenarios, examples, and patterns, read extended-guide.md.
Reference index
All packaged reference files (required for skill lint reachability):
© TencentCloudBase, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in config/source/skills/auth-tool-cloudbase of TencentCloudBase/CloudBase-AI-Toolkit.
- SKILL.md
- checklist.md
- references/extended-guide.md
Open the folder on GitHubat commit ea2c202
Used in 2 other repositories
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in TencentCloudBase/CloudBase-AI-Toolkit, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Auth Tool Cloudbase next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Auth Tool Cloudbase this skillTencentCloudBase/CloudBase-AI-Toolkit | 1.1k | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Fortify Developmentcoollabsio/coolify | 63k | 4 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Supabase Development and Debuggingsupabase/agent-skills | 2.7k | 3 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Better Auth Best Practiceslatitude-dev/latitude-llm | 4.7k | 7 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Supabasecurvenote/curvenote | 169 | 5 repos | ~2.2k | Automated safety check: Pass | Custom licence | |
| Gitnexus Exploringaws-samples/sample-kolya-br-proxy | 106 | 11 repos | ~749 | Automated safety check: Pass | MIT-0 |
Similar skills
- Official
Supabase Development and Debugging
supabase/agent-skills
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
Better Auth Best Practices
latitude-dev/latitude-llm
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.
Supabase
curvenote/curvenote
A skill your agent uses when doing ANY task involving Supabase.
- Official
Gitnexus Exploring
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.
- Official
Gemini Live API Dev
google-gemini/gemini-skills
A skill your agent uses when building real-time, bidirectional streaming applications with the Gemini Live API, or migrating legacy Live models (2.0/2.5/3.1) to Gemini 3.8 Live.
More from TencentCloudBase/CloudBase-AI-Toolkit
All 49 skills in this repoAI Model Nodejs
TencentCloudBase/CloudBase-AI-Toolkit
A skill your agent uses for Node.js backend AI via @cloudbase/node-sdk (=3.16.0) — cloud functions, CloudRun, Express/Koa/NestJS, serverless APIs, scheduled jobs, LLM proxies, agent orchestration.
HTTP API Cloudbase
TencentCloudBase/CloudBase-AI-Toolkit
CloudBase official HTTP API client guide. An agent skill from TencentCloudBase/CloudBase-AI-Toolkit.
Cloud API Recipe Authoring
TencentCloudBase/CloudBase-AI-Toolkit
Author or revise a cloud-api-operations recipe (config/source/skills/cloud-api-operations/references/recipes/).
Manage Local Skills
TencentCloudBase/CloudBase-AI-Toolkit
Analyze, standardize, validate, and sync locally maintained skills into agent skill directories with a skills CLI-aligned workflow.
Cloudbase Agent Python
TencentCloudBase/CloudBase-AI-Toolkit
Build production-ready AI agent backends using the CloudBase Agent Python SDK — create agents with LangGraph/CrewAI/LlamaIndex, serve them via FastAPI with AG-UI protocol streaming +…
Cloudbase
TencentCloudBase/CloudBase-AI-Toolkit
A skill your agent uses when you develop, design, build, deploy, debug, migrate, or troubleshoot CloudBase (腾讯云开发, 云开发, TCB, 微信云开发) projects — Web, 微信小程序, 小程序, uni-app, mobile (iOS, Android…
Related
Categories
Questions about Auth Tool Cloudbase
What does Auth Tool Cloudbase do?
CloudBase auth provider configuration and login-readiness guide. Auth Tool Cloudbase is an agent skill from TencentCloudBase/CloudBase-AI-Toolkit. CloudBase auth provider configuration and login-readiness guide.
When should I use Auth Tool Cloudbase?
Auth Tool Cloudbase fits situations like: tasks that involve Authentication.
How do I install Auth Tool Cloudbase in Claude Code?
Run `npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a claude-code`. Or copy the skill folder (config/source/skills/auth-tool-cloudbase in TencentCloudBase/CloudBase-AI-Toolkit) into .claude/skills/auth-tool-cloudbase in your project. Claude Code loads it when a task matches its description.
How do I install Auth Tool Cloudbase in Codex?
Run `npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a codex`. Or copy the skill folder (config/source/skills/auth-tool-cloudbase in TencentCloudBase/CloudBase-AI-Toolkit) into .agents/skills/auth-tool-cloudbase in your project. Codex loads it when a task matches its description.
Can I use Auth Tool Cloudbase in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill auth-tool-cloudbase -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/auth-tool-cloudbase, .gemini/skills/auth-tool-cloudbase, .github/skills/auth-tool-cloudbase and .opencode/skills/auth-tool-cloudbase in your project.
What does Auth Tool Cloudbase need to run?
SKILL.md names no scripts, command-line tools or credentials: Auth Tool Cloudbase is instructions for the agent only. Our summary lists: Node.js.
Does Auth Tool Cloudbase access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Auth Tool Cloudbase safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Auth Tool Cloudbase use?
Auth Tool Cloudbase is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Auth Tool Cloudbase use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.7k tokens, read only when the agent opens those files.
What are the alternatives to Auth Tool Cloudbase?
Skills that share tags, products or a category with Auth Tool Cloudbase: Fortify Development (coollabsio/coolify, 63k stars), Supabase Development and Debugging (supabase/agent-skills, 2.7k stars), Better Auth Best Practices (latitude-dev/latitude-llm, 4.7k stars) and Supabase (curvenote/curvenote, 169 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Auth Tool Cloudbase?
TencentCloudBase (a GitHub organization) maintains it in TencentCloudBase/CloudBase-AI-Toolkit, which has 1,132 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 6, 2026.
Source: TencentCloudBase/CloudBase-AI-Toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.