CloudBase function runtime guide for building, deploying, and debugging your own Event Functions or HTTP Functions. This skill should be used when users need application runtime code on CloudBase, not when they are merely calling CloudBase official platform APIs.
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/16/2026
What it changes
Passed 19 of 22 test cases with the skill, and 9 of 22 without it.
Without skill41%
With skill86%
Checks it passed that the model alone missed
Includes an scf_bootstrap executable startup script.
Deploys using manageFunctions tool rather than CloudRun.
Excludes req.headers from the diagnostic response payload.
and 12 more in the full report
11 fixed8 passed either way2 still failing1 broke
Pass-rate lift
+45 pp
Tokens
+297%
Agent turns
0%
Response time
-28%
Model gemini-3.6-flashMeasured 8/16/2026v319 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
When deploying functions in a project structured as project-root/cloudfunctions/my-func/index.js using manageFunctions tool, what value should be passed for functionRootPath?
What was checked, without and with the skill
Checked
Without skill
With skill
Passes parent directory cloudfunctions/ as functionRootPath.
Missed
Passed
case-22 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md375 lines7 files
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):
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 ./references/http-function-credentials.md. HTTP Functions must use explicit credentials; do not rely on the Event Function passwordless runtime path.
Exception only (do not read by default)
Migrating an existing app that already uses classic TCP DB clients (DATABASE_URL / Prisma / mysql2 / pg / Redis) → read ./references/vpc-and-tcp-database.md via ./references.md. New business CRUD must prefer CloudBase native SDK (app.database() / app.rdb()) or MCP SQL tools instead of TCP.
Then also read
Detailed reference routing -> ./references.md
Auth setup or provider-related backend work -> ../auth-tool-cloudbase/SKILL.md
CloudBase Integration Center generated WeChat Pay or Official Account functions -> ../cloudbase-wechat-integration/SKILL.md (official docs: https://docs.cloudbase.net/integration/introduce/index.md)
AI in functions -> ../ai-model-nodejs/SKILL.md
Long-lived container services or Agent runtimes -> ../cloudrun-development/SKILL.md
Calling CloudBase official platform APIs from a client or script -> ../http-api-cloudbase/SKILL.md