cloud-functions

Automate CloudBase cloud function deployment across Node.js, Python, Go, and Java.

1|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/xianmingyao/openclaw-CaySon --skill cloud-functions-xianmingyao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-functions
Source: https://github.com/xianmingyao/openclaw-CaySon/tree/main/skills/cloudbase/references/cloud-functions
Command: npx skills add https://github.com/xianmingyao/openclaw-CaySon --skill cloud-functions-xianmingyao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the development, deployment, and management of CloudBase Cloud Functions, reducing the complexity of handling both Event Functions and HTTP Functions across multiple runtimes.

Core Features & Use Cases

  • Supports Event Functions and HTTP Functions across Node.js, Python, Go, and Java with explicit runtime selection.
  • Handles deployment, logging, invocation, and gateway/http access configuration using MCP tooling (queryFunctions, manageFunctions, manageGateway).
  • Includes best practices for environment variables, security, and monitoring for reliable serverless function workflows.

Quick Start

Create a new Event or HTTP function, specify runtime, and deploy with the MCP tools to verify end-to-end operation.

Frequently Asked Questions about cloud-functions

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

FAQPage Schema
How do I deploy CloudBase cloud functions across different runtimes?

To deploy CloudBase cloud functions, you specify a runtime like Node.js, Python, Go, or Java, provide a functionRootPath, and use MCP tooling such as manageFunctions to create and update serverless functions.

What is the difference between Event Functions and HTTP Functions in CloudBase?

Event Functions handle background triggers, while HTTP Functions expose endpoints for direct web access. Both cloud function types are managed using MCP tooling, with HTTP Functions requiring additional manageGateway configuration for gateway access.

Can I change the runtime of an existing CloudBase cloud function after deployment?

No, you cannot change the runtime of an existing CloudBase cloud function. The system enforces runtime immutability, meaning you must select your Node.js, Python, Go, or Java environment during initial function creation and keep it fixed.

How do I expose an HTTP Function to the web using CloudBase?

You expose an HTTP Function by configuring gateway access through the manageGateway MCP tool. This creates a web endpoint for your serverless function, allowing external HTTP requests to trigger its execution.

Do I need a specific directory structure to manage CloudBase cloud functions?

Yes, you need a proper functionRootPath to manage CloudBase cloud functions. This directory structure is required for the MCP tooling to correctly locate, deploy, and update your serverless function code and configuration files.

What MCP tools are required for end-to-end CloudBase cloud function management?

End-to-end management requires queryFunctions, manageFunctions, and manageGateway MCP tools. These handle querying existing functions, deploying or updating function code, and exposing HTTP Functions through the gateway for external access.