cloud-functions

Author, deploy, and debug CloudBase Event and HTTP Functions.

Updated May 14, 2026
One-click install
npx skills add https://github.com/williamwang25/ams-admin --skill cloud-functions-williamwang25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-functions
Source: https://github.com/williamwang25/ams-admin/tree/main/.windsurf/skills/cloudbase/references/cloud-functions
Command: npx skills add https://github.com/williamwang25/ams-admin --skill cloud-functions-williamwang25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

CloudBase function development can fail due to choosing the wrong function model, incorrect runtime packaging, missing scf_bootstrap for HTTP Functions, or misconfigured gateway/security access, causing broken endpoints, confusing logs, and slow iteration.

Core Features & Use Cases

  • Event vs HTTP Function guidance: clearly separates the two runtime contracts (Event handler shape vs HTTP server on port 9000) so you implement the correct model from the start.
  • Deployment-ready authoring rules: enforces Node.js HTTP Function packaging expectations (scf_bootstrap, port 9000, dependency bundling) and response/route handling discipline to avoid runtime contract mismatches.
  • Operations and debugging pathways: directs you to the right tools for logs, gateway exposure, environment/config updates, and includes safe fallbacks when MCP is unavailable.
  • Gotcha prevention: highlights common failure patterns like runtime immutability, wrong scf_bootstrap binary path, incorrect JSON/body handling, and confusing gateway access with runtime behavior.

Quick Start

Ask your agent to deploy an HTTP Function that listens on port 9000, includes the correct scf_bootstrap for Nodejs18.15, and configures public invocation rules if the endpoint must be accessible without authentication.

Frequently Asked Questions about cloud-functions

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

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

CloudBase Event Functions use an SDK or timer-driven handler shape for background logic, while HTTP Functions require a server listening on port 9000 with a valid scf_bootstrap file to handle REST, SSE, or WebSocket endpoints.

How do I deploy a CloudBase HTTP Function that is publicly accessible without authentication?

To deploy a public CloudBase HTTP Function, package the Node.js runtime with scf_bootstrap and port 9000, then configure gateway exposure and public invocation rules separately from the runtime behavior to bypass authentication requirements.

Why does my CloudBase HTTP Function fail to start with a runtime contract mismatch?

CloudBase HTTP Function startup failures often stem from missing or incorrectly configured scf_bootstrap files, wrong binary paths, or not binding the server to port 9000 as required by the Node.js runtime packaging expectations.

Do I need scf_bootstrap for Node.js 18.15 CloudBase functions?

Yes, scf_bootstrap is required for CloudBase HTTP Functions running Node.js 18.15 to define the startup command and ensure the server binds to port 9000 for correct runtime contract execution.

How do I debug CloudBase function logs when MCP tools are unavailable?

When MCP tools are unavailable for CloudBase function debugging, use safe fallback pathways to inspect logs directly, verify gateway access configurations, and check environment or config updates to identify runtime issues.

Can I update environment variables and configurations for deployed CloudBase functions?

Yes, CloudBase functions support environment and configuration updates through safe MCP tools for function lifecycle operations, though runtime immutability means you must redeploy to apply structural changes to the function package.