cloudbase_skill
- TypeScript
975
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill tencentcloudbase/cloudbase-mcp --skill cloudbase- SKILL.md17.9 KB
Overview
This skill provides essential CloudBase (Tencent CloudBase) development guidelines and workflow rules for building web apps, WeChat mini programs, backend services, databases, storage, deployment, and AI features. It emphasizes using CloudBase MCP (Model Context Protocol) or mcporter to inspect and run CloudBase tools, and it guides developers on platform-specific constraints and recommended skill mappings. Read this before starting or contributing to any CloudBase project.
How this skill works
The skill inspects the project context and maps user requests to CloudBase capabilities (hosting, functions, databases, auth, storage, AI). It enforces a workflow: understand tools first via MCP (or mcporter), authenticate with device-code login, then run tool descriptions before calling actions. It recommends the right sub-skills for SDK integration, deployment, and platform-specific patterns.
When to use it
- Starting a new CloudBase full-stack web app or migrating an existing app to CloudBase
- Building or deploying WeChat mini programs that rely on wx.cloud and OPENID
- Creating or deploying cloud functions, container services (CloudRun), or static hosting
- Implementing database models (NoSQL collections or MySQL tables) and security rules
- Adding authentication providers or using AI models (text/chat/image) with streaming
- Working in environments where MCP is not available and mcporter CLI is required
Best practices
- Always run npx mcporter describe cloudbase (or MCP describe) before managing or deploying CloudBase
- Prefer device-code login via MCP auth tool; do not hard-code SecretId/SecretKey/EnvId in configs
- Install CloudBase MCP in your agent/workspace for consistent environment management and deployments
- Deploy backend components before frontend previews when backend services are required
- Use SDKs directly for database access where possible; use cloud functions only when necessary
- Map user needs to specific CloudBase skills (auth-web, no-sql-web-sdk, ai-model-web, etc.)
Example use cases
- Deploy a React site to CloudBase static hosting and wire in Web SDK authentication
- Create a WeChat mini program using wx.cloud with cloud functions and document DB
- Set up a Node.js cloud function that calls a CloudBase AI model with streaming output
- Provision a MySQL database, design tables, and use relational-database-tool for management
- Use mcporter to start device-code login, bind an envId, then deploy cloud functions
FAQ
No. Use MCP device-code auth or interactive login via mcporter to avoid embedding secrets.
What if my environment doesn't support MCP?
Use the mcporter CLI to call CloudBase MCP tools (npx mcporter call cloudbase.<tool> key=value).