cloud-functions

Develop and deploy CloudBase Event Functions and HTTP Functions with correct runtime selection.

2|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/lxb031018/qintu --skill cloud-functions-lxb031018
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-functions
Source: https://github.com/lxb031018/qintu/tree/main/.codebuddy/skills/cloud-functions
Command: npx skills add https://github.com/lxb031018/qintu --skill cloud-functions-lxb031018

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you create, update, deploy, and troubleshoot CloudBase Event Functions and HTTP Functions without mixing up the different runtime models or packaging requirements.

Core Features & Use Cases

  • Correctly choose the function runtime model: decide between Event Functions and HTTP Functions based on triggers and API needs.
  • Deploy and operate with the right workflows: create, update code, update config, and verify execution behavior using the intended tool actions.
  • Handle access and observability: manage gateway exposure for HTTP access patterns and inspect logs for debugging.
  • Use-case example: you need a server-side endpoint for a mobile app to call; you can use HTTP Functions (port 9000 with scf_bootstrap) and then add gateway access if browser/public routing is required.

Quick Start

Use the cloud-functions skill to implement and deploy your CloudBase Event Function or HTTP Function for application runtime logic, then validate it via the relevant references and execution checklist before exposing it through a gateway.

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 CloudBase Event Functions and HTTP Functions for serverless deployment?

Choose CloudBase Event Functions for event triggers and config updates, or HTTP Functions for exposed HTTP endpoints and gateway routing. The runtime model depends on whether your serverless workflow requires event-driven logic or direct HTTP access.

How do I deploy HTTP Functions to CloudBase with the correct packaging constraints?

Deploy HTTP Functions by enforcing correct runtime selection, handler shapes, and packaging constraints like using port 9000 with scf_bootstrap. This ensures your serverless endpoint is correctly packaged for CloudBase deployment.

Can I expose my CloudBase serverless function to a public browser route?

Yes, you can expose CloudBase HTTP Functions to public browser routing by adding gateway access. This manages gateway exposure for HTTP access patterns after your function is deployed and verified.

How do I debug CloudBase function logs in a serverless workflow?

Debug CloudBase functions by inspecting function logs for troubleshooting execution behavior. This log-driven debugging approach helps identify issues within your event or HTTP function workflows.

What are the handler shape requirements for CloudBase event functions?

CloudBase event functions require specific handler shapes and correct runtime selection to execute properly. Enforcing these packaging constraints ensures your function triggers operate within the serverless environment.