[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWW8MW876GEXWHTY7P54WV":3,"skill-same:01M7BWW8MW876GEXWHTY7P54WV":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BWW8MW876GEXWHTY7P54WV","cloudrun-development",null,"CloudBase Run backend development rules (Function mode\u002FContainer mode). Use this skill when deploying backend services that require long connections, multi-language support, custom environments, or AI agent development.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-plugins\u002Fcloudbase\u002Fskills\u002Fcloudbase\u002Freferences\u002Fcloudrun-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloudrun-development\ndescription: CloudBase Run backend development rules (Function mode\u002FContainer mode). Use this skill when deploying backend services that require long connections, multi-language support, custom environments, or AI agent development.\nalwaysApply: false\n---\n\n## When to use this skill\n\nUse this skill for **CloudBase Run backend service development** when you need:\n\n- Long connection capabilities: WebSocket \u002F SSE \u002F server push\n- Long-running or persistent processes: tasks that are not suitable for cloud functions, background jobs\n- Custom runtime environments\u002Fsystem dependencies: custom images, specific system libraries\n- Multi-language\u002Farbitrary frameworks: Java, Go, PHP, .NET, Python, Node.js, etc.\n- Stable external services with elastic scaling: pay-as-you-go, can scale down to 0\n- Private\u002Finternal network access: VPC\u002FPRIVATE access, mini-program `callContainer` internal direct connection\n- AI agent development: develop personalized AI applications based on Function mode CloudRun\n\n**Do NOT use for:**\n- Simple cloud functions (use cloud function development instead)\n- Frontend-only applications\n- Database schema design (use data-model-creation skill)\n\n---\n\n## How to use this skill (for a coding agent)\n\n1. **Choose the right mode**\n   - **Function mode**: Fastest to get started, built-in HTTP\u002FWebSocket\u002FSSE, fixed port 3000, local running supported\n   - **Container mode**: Any language and runtime, requires Dockerfile, local running not supported by tools\n\n2. **Follow mandatory requirements**\n   - Must listen on `PORT` environment variable (real port in container)\n   - Stateless service: write data externally (DB\u002Fstorage\u002Fcache)\n   - No background persistent threads\u002Fprocesses outside requests\n   - Minimize dependencies, slim images; reduce cold start and deployment time\n   - Resource constraints: `Mem = 2 × CPU` (e.g., 0.25 vCPU → 0.5 GB)\n   - Access control: Only enable public network for Web scenarios; mini-programs prioritize internal direct connection, recommend closing public network\n\n3. **Use tools correctly**\n   - **Read operations**: `queryCloudRun` (list, detail, templates)\n   - **Write operations**: `manageCloudRun` (init, download, run, deploy, delete, createAgent)\n   - Always use absolute paths for `targetPath`\n   - Use `force: true` for delete operations\n\n4. **Follow the workflow**\n   - Initialize project → Check\u002Fgenerate Dockerfile (for container mode) → Local run (function mode only) → Configure access → Deploy → Verify\n\n---\n\n# CloudBase Run AI Development Rules\n\nA concise guide for AI assistants and engineering collaboration, providing \"when to use, how to use\" rules and tool workflows.\n\n## 1. When to use CloudBase Run (Use Cases)\n\n- Need long connection capabilities: WebSocket \u002F SSE \u002F server push\n- Need long-running or persistent processes: tasks that are not suitable for cloud functions, background jobs\n- Need custom runtime environments\u002Fsystem dependencies: custom images, specific system libraries\n- Use multi-language\u002Farbitrary frameworks: Java, Go, PHP, .NET, Python, Node.js, etc.\n- Need stable external services with elastic scaling: pay-as-you-go, can scale down to 0\n- Need private\u002Finternal network access: VPC\u002FPRIVATE access, mini-program `callContainer` internal direct connection\n- Need to develop AI agents: develop personalized AI applications based on Function mode CloudRun\n\n## 2. Mode Selection (Quick Comparison)\n\n- **Function mode**: Fastest to get started, built-in HTTP\u002FWebSocket\u002FSSE, fixed port 3000; local running supported by tools\n- **Container mode**: Any language and runtime, requires Dockerfile; local running not supported by tools\n\n### Mode Comparison Checklist\n\n| Dimension | Function Mode | Container Mode |\n| --- | --- | --- |\n| Language\u002FFramework | Node.js (via `@cloudbase\u002Ffunctions-framework`) | Any language\u002Fruntime (Java\u002FGo\u002FPHP\u002F.NET\u002FPython\u002FNode.js, etc.) |\n| Runtime | Function framework loads functions (Runtime) | Docker image starts process |\n| Port | Fixed 3000 | Application listens on `PORT` (injected by platform during deployment) |\n| Dockerfile | Not required | Required (and must pass local build) |\n| Local Running | Supported (built-in tools) | Not supported (recommend using Docker for debugging) |\n| Typical Scenarios | WebSocket\u002FSSE\u002Fstreaming responses, forms\u002Ffiles, low latency, multiple functions per instance, shared memory | Arbitrary system dependencies\u002Flanguages, migrating existing containerized applications |\n\n## 3. Development Requirements (Must Meet)\n\n- Must listen on `PORT` environment variable (real port in container)\n- Stateless service: write data externally (DB\u002Fstorage\u002Fcache)\n- No background persistent threads\u002Fprocesses outside requests\n- Minimize dependencies, slim images; reduce cold start and deployment time\n- Resource constraints: `Mem = 2 × CPU` (e.g., 0.25 vCPU → 0.5 GB)\n- Access control: Only enable public network for Web scenarios; mini-programs prioritize internal direct connection, recommend closing public network\n\n## 4. Tools (Plain Language & Read\u002FWrite Separation)\n\n- **Read operations** (`queryCloudRun`):\n  - `list`: What services do I have? Can filter by name\u002Ftype\n  - `detail`: Current configuration, version, access address of a service\n  - `templates`: Ready-to-use starter templates\n- **Write operations** (`manageCloudRun`):\n  - `init`: Create local project (optional template)\n  - `download`: Pull existing service code to local\n  - `run`: Run locally (Function mode only, supports normal function and Agent mode)\n  - `deploy`: Deploy local code to CloudRun\n  - `delete`: Delete service (requires explicit confirmation)\n  - `createAgent`: Create AI agent (based on Function mode CloudRun)\n- **Important parameters** (remember these):\n  - `targetPath`: Local directory (must be absolute path)\n  - `serverConfig`: Deployment parameters (CPU\u002FMem\u002Finstance count\u002Faccess type\u002Fenvironment variables, etc.)\n  - `runOptions`: Local running port and temporary environment variables (Function mode), supports `runMode: 'normal' | 'agent'`\n  - `agentConfig`: Agent configuration (agentName, botTag, description, template)\n  - Delete must include `force: true`, otherwise it won't execute\n\n## 5. Core Workflow (Understand Steps First, Then Examples)\n\n1) **Choose mode**\n   - Need multi-language\u002Fexisting container\u002FDocker: choose \"Container mode\"\n   - Need long connection\u002Fstreaming\u002Flow latency\u002Fmultiple functions coexisting: prioritize \"Function mode\"\n\n2) **Initialize local project**\n   - General: Use template `init` (both Function mode and Container mode can start from templates)\n   - Container mode must \"check or generate Dockerfile\":\n     - Node.js minimal example:\n       ```dockerfile\n       FROM node:18-alpine\n       WORKDIR \u002Fapp\n       COPY package*.json .\u002F\n       RUN npm ci --omit=dev\n       COPY . .\n       ENV NODE_ENV=production\n       EXPOSE 3000\n       CMD [\"node\",\"server.js\"]\n       ```\n     - Python minimal example:\n       ```dockerfile\n       FROM python:3.11-slim\n       WORKDIR \u002Fapp\n       COPY requirements.txt .\u002F\n       RUN pip install -r requirements.txt --no-cache-dir\n       COPY . .\n       ENV PORT=3000\n       EXPOSE 3000\n       CMD [\"python\",\"app.py\"]\n       ```\n\n3) **Local running** (Function mode only)\n   - Automatically use `npm run dev\u002Fstart` or entry file via `run`\n\n4) **Configure access**\n   - Set `OpenAccessTypes` (WEB\u002FVPC\u002FPRIVATE) as needed; configure security domain and authentication for Web scenarios\n\n5) **Deploy**\n   - Specify CPU\u002FMem\u002Finstance count\u002Fenvironment variables, etc. during `deploy`\n\n6) **Verify**\n   - Use `detail` to confirm access address and configuration meet expectations\n\n### Example Tool Calls\n\n1) **View templates\u002Fservices**\n```json\n{ \"name\": \"queryCloudRun\", \"arguments\": { \"action\": \"templates\" } }\n```\n```json\n{ \"name\": \"queryCloudRun\", \"arguments\": { \"action\": \"detail\", \"detailServerName\": \"my-svc\" } }\n```\n\n2) **Initialize project**\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"init\", \"serverName\": \"my-svc\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fmy-svc\", \"template\": \"helloworld\" } }\n```\n\n3) **Download code** (optional)\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"download\", \"serverName\": \"my-svc\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fmy-svc\" } }\n```\n\n4) **Local running** (Function mode only)\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"run\", \"serverName\": \"my-svc\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fmy-svc\", \"runOptions\": { \"port\": 3000 } } }\n```\n\n5) **Deploy**\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"deploy\", \"serverName\": \"my-svc\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fmy-svc\", \"serverConfig\": { \"OpenAccessTypes\": [\"WEB\"], \"Cpu\": 0.5, \"Mem\": 1, \"MinNum\": 0, \"MaxNum\": 5 } } }\n```\n\n6) **Create AI agent** (optional)\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"createAgent\", \"serverName\": \"my-agent\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fagents\", \"agentConfig\": { \"agentName\": \"MyAgent\", \"botTag\": \"demo\", \"description\": \"My agent\", \"template\": \"blank\" } } }\n```\n\n7) **Run agent** (optional)\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"run\", \"serverName\": \"my-agent\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fagents\u002Fmy-agent\", \"runOptions\": { \"port\": 3000, \"runMode\": \"agent\" } } }\n```\n\n## 6. Best Practices (Strongly Recommended)\n\n- Prioritize PRIVATE\u002FVPC or mini-program internal `callContainer`, reduce public network exposure\n- Web must use CloudBase Web SDK authentication; mini-programs authenticated by platform\n- Secrets via environment variables; separate configuration for multiple environments (dev\u002Fstg\u002Fprod)\n- Use `queryCloudRun.detail` to verify configuration and accessibility before and after deployment\n- Image layers reusable, small volume; monitor startup latency and memory usage\n- Agent development: Use `@cloudbase\u002Faiagent-framework`, supports SSE streaming responses, BotId format is `ibot-{name}-{tag}`\n\n## 7. Quick Troubleshooting\n\n- **Access failure**: Check OpenAccessTypes\u002Fdomain\u002Fport, whether instance scaled down to 0\n- **Deployment failure**: Verify Dockerfile\u002Fbuild logs\u002Fimage volume and CPU\u002FMem ratio\n- **Local running failure**: Only Function mode supported; requires `package.json` `dev`\u002F`start` or entry `index.js|app.js|server.js`\n- **Performance jitter**: Reduce dependencies and initialization; appropriately increase MinNum; optimize cold start\n- **Agent running failure**: Check `@cloudbase\u002Faiagent-framework` dependency, BotId format, SSE response format\n\n## 8. Function Mode CloudRun (Function Mode) Key Points (Concise)\n\n- **Definition**: CloudRun + function framework (`@cloudbase\u002Ffunctions-framework`) + function code, making container service development as simple as writing cloud functions\n- **When to choose**: Need WebSocket\u002FSSE\u002Ffile upload\u002Fstreaming responses; need long tasks or connect to DB\u002Fmessage queue; need multiple functions per instance and shared memory, low latency and better logs\u002Fdebugging\n- **Agent mode**: Develop AI agents based on Function mode CloudRun, use `@cloudbase\u002Faiagent-framework`, supports SSE streaming responses and personalized AI applications\n- **Tool support**: Local running only supports Function mode (`manageCloudRun` → `run`); deploy using `manageCloudRun` → `deploy`; query using `queryCloudRun`\n- **Migration tips**: Different from cloud function call chain\u002Fruntime, migration requires minor modifications (including client calling methods)\n- **Portability**: Based on function framework, can run locally\u002Fhost\u002FDocker, non-CloudRun requires self-managed build and deployment\n\n## 9. Service Invocation Methods (Concise Examples)\n\n### HTTP Direct Access (when WEB public network enabled)\n```bash\ncurl -L \"https:\u002F\u002F\u003Cyour-service-domain>\"\n```\n\n### WeChat Mini Program (internal direct connection, recommend closing public network)\n```js\n\u002F\u002F app.js (ensure wx.cloud.init() is called)\nconst res = await wx.cloud.callContainer({\n  config: { env: \"\u003CenvId>\" },\n  path: \"\u002F\",\n  method: \"GET\",\n  header: { \"X-WX-SERVICE\": \"\u003CserviceName>\" }\n});\n```\n\n### Web (JS SDK, need to configure security domain and authentication)\n```js\nimport cloudbase from \"@cloudbase\u002Fjs-sdk\";\n\nconst app = cloudbase.init({ env: \"\u003CenvId>\" });  \u002F\u002F Collect user's phone number into variable `phoneNum` by providing a input UI\n\nconst auth = app.auth();\n\n\u002F\u002F Send SMS code\nconst verificationInfo = await auth.getVerification({\n  phone_number: `+86 ${phoneNum}`,\n});\n\n\u002F\u002F Collect user's phone number into variable `verificationCode` by providing a input UI \n\n\u002F\u002F Sign in\nawait auth.signInWithSms({\n  verificationInfo,\n  verificationCode,\n  phoneNum,\n});\n\nconst res = await app.callContainer({\n  name: \"\u003CserviceName>\", method: \"POST\", path: \"\u002Fapi\",\n  header: { \"Content-Type\": \"application\u002Fjson\" },\n  data: { key: \"value\" }\n});\n```\n\n\u002F\u002F Web JS SDK initialization MUST be synchronous:\n\u002F\u002F - Always use top-level `import cloudbase from \"@cloudbase\u002Fjs-sdk\";`\n\u002F\u002F - Do NOT use dynamic imports like `import(\"@cloudbase\u002Fjs-sdk\")` or async wrappers such as `initCloudBase()` with internal `initPromise`\n\n### Node.js (server-side\u002Fcloud function internal call)\n```js\nimport tcb from \"@cloudbase\u002Fnode-sdk\";\nconst app = tcb.init({});\nconst res = await app.callContainer({\n  name: \"\u003CserviceName>\", method: \"GET\", path: \"\u002Fhealth\",\n  timeout: 5000\n});\n```\n\n### Recommendations\n- Mini Program\u002FServer side prioritize internal network (VPC\u002FPRIVATE) calls, reduce exposure surface\n- Web scenarios need to enable WEB, public domain and security domain, and use SDK authentication\n","## When to use this skill\n\nUse this skill for **CloudBase Run backend service development** when you need:\n\n- Long connection capabilities: WebSocket \u002F SSE \u002F server push\n- Long-running or persistent processes: tasks that are not suitable for cloud functions, background jobs\n- Custom runtime environments\u002Fsystem dependencies: custom images, specific system libraries\n- Multi-language\u002Farbitrary frameworks: Java, Go, PHP, .NET, Python, Node.js, etc.\n- Stable external services with elastic scaling: pay-as-you-go, can scale down to 0\n- Private\u002Finternal network access: VPC\u002FPRIVATE access, mini-program `callContainer` internal direct connection\n- AI agent development: develop personalized AI applications based on Function mode CloudRun\n\n**Do NOT use for:**\n- Simple cloud functions (use cloud function development instead)\n- Frontend-only applications\n- Database schema design (use data-model-creation skill)\n\n---\n\n## How to use this skill (for a coding agent)\n\n1. **Choose the right mode**\n   - **Function mode**: Fastest to get started, built-in HTTP\u002FWebSocket\u002FSSE, fixed port 3000, local running supported\n   - **Container mode**: Any language and runtime, requires Dockerfile, local running not supported by tools\n\n2. **Follow mandatory requirements**\n   - Must listen on `PORT` environment variable (real port in container)\n   - Stateless service: write data externally (DB\u002Fstorage\u002Fcache)\n   - No background persistent threads\u002Fprocesses outside requests\n   - Minimize dependencies, slim images; reduce cold start and deployment time\n   - Resource constraints: `Mem = 2 × CPU` (e.g., 0.25 vCPU → 0.5 GB)\n   - Access control: Only enable public network for Web scenarios; mini-programs prioritize internal direct connection, recommend closing public network\n\n3. **Use tools correctly**\n   - **Read operations**: `queryCloudRun` (list, detail, templates)\n   - **Write operations**: `manageCloudRun` (init, download, run, deploy, delete, createAgent)\n   - Always use absolute paths for `targetPath`\n   - Use `force: true` for delete operations\n\n4. **Follow the workflow**\n   - Initialize project → Check\u002Fgenerate Dockerfile (for container mode) → Local run (function mode only) → Configure access → Deploy → Verify\n\n---\n\n# CloudBase Run AI Development Rules\n\nA concise guide for AI assistants and engineering collaboration, providing \"when to use, how to use\" rules and tool workflows.\n\n## 1. When to use CloudBase Run (Use Cases)\n\n- Need long connection capabilities: WebSocket \u002F SSE \u002F server push\n- Need long-running or persistent processes: tasks that are not suitable for cloud functions, background jobs\n- Need custom runtime environments\u002Fsystem dependencies: custom images, specific system libraries\n- Use multi-language\u002Farbitrary frameworks: Java, Go, PHP, .NET, Python, Node.js, etc.\n- Need stable external services with elastic scaling: pay-as-you-go, can scale down to 0\n- Need private\u002Finternal network access: VPC\u002FPRIVATE access, mini-program `callContainer` internal direct connection\n- Need to develop AI agents: develop personalized AI applications based on Function mode CloudRun\n\n## 2. Mode Selection (Quick Comparison)\n\n- **Function mode**: Fastest to get started, built-in HTTP\u002FWebSocket\u002FSSE, fixed port 3000; local running supported by tools\n- **Container mode**: Any language and runtime, requires Dockerfile; local running not supported by tools\n\n### Mode Comparison Checklist\n\n| Dimension | Function Mode | Container Mode |\n| --- | --- | --- |\n| Language\u002FFramework | Node.js (via `@cloudbase\u002Ffunctions-framework`) | Any language\u002Fruntime (Java\u002FGo\u002FPHP\u002F.NET\u002FPython\u002FNode.js, etc.) |\n| Runtime | Function framework loads functions (Runtime) | Docker image starts process |\n| Port | Fixed 3000 | Application listens on `PORT` (injected by platform during deployment) |\n| Dockerfile | Not required | Required (and must pass local build) |\n| Local Running | Supported (built-in tools) | Not supported (recommend using Docker for debugging) |\n| Typical Scenarios | WebSocket\u002FSSE\u002Fstreaming responses, forms\u002Ffiles, low latency, multiple functions per instance, shared memory | Arbitrary system dependencies\u002Flanguages, migrating existing containerized applications |\n\n## 3. Development Requirements (Must Meet)\n\n- Must listen on `PORT` environment variable (real port in container)\n- Stateless service: write data externally (DB\u002Fstorage\u002Fcache)\n- No background persistent threads\u002Fprocesses outside requests\n- Minimize dependencies, slim images; reduce cold start and deployment time\n- Resource constraints: `Mem = 2 × CPU` (e.g., 0.25 vCPU → 0.5 GB)\n- Access control: Only enable public network for Web scenarios; mini-programs prioritize internal direct connection, recommend closing public network\n\n## 4. Tools (Plain Language & Read\u002FWrite Separation)\n\n- **Read operations** (`queryCloudRun`):\n  - `list`: What services do I have? Can filter by name\u002Ftype\n  - `detail`: Current configuration, version, access address of a service\n  - `templates`: Ready-to-use starter templates\n- **Write operations** (`manageCloudRun`):\n  - `init`: Create local project (optional template)\n  - `download`: Pull existing service code to local\n  - `run`: Run locally (Function mode only, supports normal function and Agent mode)\n  - `deploy`: Deploy local code to CloudRun\n  - `delete`: Delete service (requires explicit confirmation)\n  - `createAgent`: Create AI agent (based on Function mode CloudRun)\n- **Important parameters** (remember these):\n  - `targetPath`: Local directory (must be absolute path)\n  - `serverConfig`: Deployment parameters (CPU\u002FMem\u002Finstance count\u002Faccess type\u002Fenvironment variables, etc.)\n  - `runOptions`: Local running port and temporary environment variables (Function mode), supports `runMode: 'normal' | 'agent'`\n  - `agentConfig`: Agent configuration (agentName, botTag, description, template)\n  - Delete must include `force: true`, otherwise it won't execute\n\n## 5. Core Workflow (Understand Steps First, Then Examples)\n\n1) **Choose mode**\n   - Need multi-language\u002Fexisting container\u002FDocker: choose \"Container mode\"\n   - Need long connection\u002Fstreaming\u002Flow latency\u002Fmultiple functions coexisting: prioritize \"Function mode\"\n\n2) **Initialize local project**\n   - General: Use template `init` (both Function mode and Container mode can start from templates)\n   - Container mode must \"check or generate Dockerfile\":\n     - Node.js minimal example:\n       ```dockerfile\n       FROM node:18-alpine\n       WORKDIR \u002Fapp\n       COPY package*.json .\u002F\n       RUN npm ci --omit=dev\n       COPY . .\n       ENV NODE_ENV=production\n       EXPOSE 3000\n       CMD [\"node\",\"server.js\"]\n       ```\n     - Python minimal example:\n       ```dockerfile\n       FROM python:3.11-slim\n       WORKDIR \u002Fapp\n       COPY requirements.txt .\u002F\n       RUN pip install -r requirements.txt --no-cache-dir\n       COPY . .\n       ENV PORT=3000\n       EXPOSE 3000\n       CMD [\"python\",\"app.py\"]\n       ```\n\n3) **Local running** (Function mode only)\n   - Automatically use `npm run dev\u002Fstart` or entry file via `run`\n\n4) **Configure access**\n   - Set `OpenAccessTypes` (WEB\u002FVPC\u002FPRIVATE) as needed; configure security domain and authentication for Web scenarios\n\n5) **Deploy**\n   - Specify CPU\u002FMem\u002Finstance count\u002Fenvironment variables, etc. during `deploy`\n\n6) **Verify**\n   - Use `detail` to confirm access address and configuration meet expectations\n\n### Example Tool Calls\n\n1) **View templates\u002Fservices**\n```json\n{ \"name\": \"queryCloudRun\", \"arguments\": { \"action\": \"templates\" } }\n```\n```json\n{ \"name\": \"queryCloudRun\", \"arguments\": { \"action\": \"detail\", \"detailServerName\": \"my-svc\" } }\n```\n\n2) **Initialize project**\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"init\", \"serverName\": \"my-svc\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fmy-svc\", \"template\": \"helloworld\" } }\n```\n\n3) **Download code** (optional)\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"download\", \"serverName\": \"my-svc\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fmy-svc\" } }\n```\n\n4) **Local running** (Function mode only)\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"run\", \"serverName\": \"my-svc\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fmy-svc\", \"runOptions\": { \"port\": 3000 } } }\n```\n\n5) **Deploy**\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"deploy\", \"serverName\": \"my-svc\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fmy-svc\", \"serverConfig\": { \"OpenAccessTypes\": [\"WEB\"], \"Cpu\": 0.5, \"Mem\": 1, \"MinNum\": 0, \"MaxNum\": 5 } } }\n```\n\n6) **Create AI agent** (optional)\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"createAgent\", \"serverName\": \"my-agent\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fagents\", \"agentConfig\": { \"agentName\": \"MyAgent\", \"botTag\": \"demo\", \"description\": \"My agent\", \"template\": \"blank\" } } }\n```\n\n7) **Run agent** (optional)\n```json\n{ \"name\": \"manageCloudRun\", \"arguments\": { \"action\": \"run\", \"serverName\": \"my-agent\", \"targetPath\": \"\u002Fabs\u002Fws\u002Fagents\u002Fmy-agent\", \"runOptions\": { \"port\": 3000, \"runMode\": \"agent\" } } }\n```\n\n## 6. Best Practices (Strongly Recommended)\n\n- Prioritize PRIVATE\u002FVPC or mini-program internal `callContainer`, reduce public network exposure\n- Web must use CloudBase Web SDK authentication; mini-programs authenticated by platform\n- Secrets via environment variables; separate configuration for multiple environments (dev\u002Fstg\u002Fprod)\n- Use `queryCloudRun.detail` to verify configuration and accessibility before and after deployment\n- Image layers reusable, small volume; monitor startup latency and memory usage\n- Agent development: Use `@cloudbase\u002Faiagent-framework`, supports SSE streaming responses, BotId format is `ibot-{name}-{tag}`\n\n## 7. Quick Troubleshooting\n\n- **Access failure**: Check OpenAccessTypes\u002Fdomain\u002Fport, whether instance scaled down to 0\n- **Deployment failure**: Verify Dockerfile\u002Fbuild logs\u002Fimage volume and CPU\u002FMem ratio\n- **Local running failure**: Only Function mode supported; requires `package.json` `dev`\u002F`start` or entry `index.js|app.js|server.js`\n- **Performance jitter**: Reduce dependencies and initialization; appropriately increase MinNum; optimize cold start\n- **Agent running failure**: Check `@cloudbase\u002Faiagent-framework` dependency, BotId format, SSE response format\n\n## 8. Function Mode CloudRun (Function Mode) Key Points (Concise)\n\n- **Definition**: CloudRun + function framework (`@cloudbase\u002Ffunctions-framework`) + function code, making container service development as simple as writing cloud functions\n- **When to choose**: Need WebSocket\u002FSSE\u002Ffile upload\u002Fstreaming responses; need long tasks or connect to DB\u002Fmessage queue; need multiple functions per instance and shared memory, low latency and better logs\u002Fdebugging\n- **Agent mode**: Develop AI agents based on Function mode CloudRun, use `@cloudbase\u002Faiagent-framework`, supports SSE streaming responses and personalized AI applications\n- **Tool support**: Local running only supports Function mode (`manageCloudRun` → `run`); deploy using `manageCloudRun` → `deploy`; query using `queryCloudRun`\n- **Migration tips**: Different from cloud function call chain\u002Fruntime, migration requires minor modifications (including client calling methods)\n- **Portability**: Based on function framework, can run locally\u002Fhost\u002FDocker, non-CloudRun requires self-managed build and deployment\n\n## 9. Service Invocation Methods (Concise Examples)\n\n### HTTP Direct Access (when WEB public network enabled)\n```bash\ncurl -L \"https:\u002F\u002F\u003Cyour-service-domain>\"\n```\n\n### WeChat Mini Program (internal direct connection, recommend closing public network)\n```js\n\u002F\u002F app.js (ensure wx.cloud.init() is called)\nconst res = await wx.cloud.callContainer({\n  config: { env: \"\u003CenvId>\" },\n  path: \"\u002F\",\n  method: \"GET\",\n  header: { \"X-WX-SERVICE\": \"\u003CserviceName>\" }\n});\n```\n\n### Web (JS SDK, need to configure security domain and authentication)\n```js\nimport cloudbase from \"@cloudbase\u002Fjs-sdk\";\n\nconst app = cloudbase.init({ env: \"\u003CenvId>\" });  \u002F\u002F Collect user's phone number into variable `phoneNum` by providing a input UI\n\nconst auth = app.auth();\n\n\u002F\u002F Send SMS code\nconst verificationInfo = await auth.getVerification({\n  phone_number: `+86 ${phoneNum}`,\n});\n\n\u002F\u002F Collect user's phone number into variable `verificationCode` by providing a input UI \n\n\u002F\u002F Sign in\nawait auth.signInWithSms({\n  verificationInfo,\n  verificationCode,\n  phoneNum,\n});\n\nconst res = await app.callContainer({\n  name: \"\u003CserviceName>\", method: \"POST\", path: \"\u002Fapi\",\n  header: { \"Content-Type\": \"application\u002Fjson\" },\n  data: { key: \"value\" }\n});\n```\n\n\u002F\u002F Web JS SDK initialization MUST be synchronous:\n\u002F\u002F - Always use top-level `import cloudbase from \"@cloudbase\u002Fjs-sdk\";`\n\u002F\u002F - Do NOT use dynamic imports like `import(\"@cloudbase\u002Fjs-sdk\")` or async wrappers such as `initCloudBase()` with internal `initPromise`\n\n### Node.js (server-side\u002Fcloud function internal call)\n```js\nimport tcb from \"@cloudbase\u002Fnode-sdk\";\nconst app = tcb.init({});\nconst res = await app.callContainer({\n  name: \"\u003CserviceName>\", method: \"GET\", path: \"\u002Fhealth\",\n  timeout: 5000\n});\n```\n\n### Recommendations\n- Mini Program\u002FServer side prioritize internal network (VPC\u002FPRIVATE) calls, reduce exposure surface\n- Web scenarios need to enable WEB, public domain and security domain, and use SDK authentication\n",{"name":5,"alwaysApply":20,"description":7},"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-plugins\u002Fcloudbase\u002Fskills\u002Fcloudbase\u002Freferences\u002Fcloudrun-development",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill cloudrun-development",{"tool":39,"command":40},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill cloudrun-development",{"tool":42,"command":43},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill cloudrun-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-plugins\u002Fcloudbase\u002Fskills\u002Fcloudbase\u002Freferences\u002Fcloudrun-development\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]