cloud-functions

Guide CloudBase users in developing, deploying, invoking, and debugging Event and HTTP Functions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the confusion and delays involved in creating the right CloudBase function type, deploying it correctly, and diagnosing runtime/log issues when building serverless HTTP APIs or event-driven handlers.

Core Features & Use Cases

  • Choose the correct function type: Event Functions vs HTTP Functions, avoiding handler-shape mismatches.
  • Deploy with correct runtime and bootstrap: Locks runtime at creation time and ensures HTTP Functions use scf_bootstrap and listen on port 9000.
  • Debug with logs and safe invocation: Guides querying logs by RequestId and handling HTTP access configuration (HTTP Access vs HTTP API).
  • Supports real-world scenarios: Build REST endpoints, SSE/WebSocket streaming services, scheduled tasks, and event-driven backends.

Quick Start

Use the cloud-functions skill to deploy an HTTP endpoint by creating an HTTP Function with the correct runtime and scf_bootstrap, then verify behavior by checking function logs for a given invocation.

Frequently Asked Questions about cloud-functions

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

FAQPage Schema
How do I choose between Event Functions and HTTP Functions in CloudBase?

CloudBase Event Functions handle asynchronous, event-driven backend workflows, while HTTP Functions expose REST API endpoints and require an executable `scf_bootstrap` file listening on port 9000. Selecting the correct function type prevents handler-shape mismatches during deployment.

Can I build a serverless SSE or WebSocket streaming service with CloudBase functions?

Yes, you can build serverless SSE streaming and WebSocket-style real-time services using CloudBase HTTP Functions. You must configure the HTTP access gateway correctly to expose these endpoints and handle real-time client connections.

How do I deploy a CloudBase HTTP Function correctly without runtime errors?

To deploy a CloudBase HTTP Function, lock the runtime at creation time since it is immutable afterward, create an executable `scf_bootstrap` file, and ensure the function listens on port 9000 to avoid runtime and deployment errors.

Why does my CloudBase function deployment fail when I try to change the runtime?

CloudBase function deployment fails on runtime changes because the runtime is immutable and must be selected at creation time. You must create a new function with the correct runtime instead of updating the existing one.

How do I debug a CloudBase serverless function using logs?

Debug CloudBase serverless functions by querying logs with the specific RequestId from the failed invocation. Use supported MCP tool actions to inspect execution logs and verify the HTTP access configuration to isolate gateway issues.

What is the difference between HTTP Access and HTTP API for CloudBase functions?

HTTP Access and HTTP API are two distinct gateway exposure methods for CloudBase functions. HTTP API is typically used for standard REST API endpoints, while proper HTTP Access configuration is required to expose SSE streaming or WebSocket-style real-time services.