cloud-functions

## Sibling skills (local only) Sibling CloudBase skills ship beside this skill. Use local relative paths such as `../auth-tool-cloudbase/SKILL.md`. If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do **not** HTTP-fetch remote skill or protocol markdown into the agent context. **Cross-cutting protocols** (required before code changes or deployments): - Change Safety Protocol: `../cloudbase-platform/references/protocols/change-safety-protocol.md` - Deployment Gate: `../cloudbase-platform/references/protocols/deployment-gate.md` - Sensitive Runtime Data Protection: `../cloudbase-platform/references/protocols/sensitive-runtime-data-protection.md` # Cloud Functions Development ## Activation Contract ### Use this first when - The task is to create, update, deploy, inspect, or debug a CloudBase Event Function or HTTP Function that serves application runtime logic. - The request mentions function runtime, function logs, `scf_bootstrap`, function triggers, or function gateway exposure. ### Read before writing code if - You still need to decide between Event Function and HTTP Function. - The task mentions `manageFunctions`, `queryFunctions`, `manageGateway`, or legacy function-tool names. - The task might require `callCloudApi` as a fallback for logs or gateway setup. - An HTTP Function will call CloudBase resources through `@cloudbase/node-sdk` or `@cloudbase/manager-node` -> read `....