[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HSBCQP2X8ZMWTRMP1W4RAZ":3,"skill-same:01M6HSBCQP2X8ZMWTRMP1W4RAZ":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6HSBCQP2X8ZMWTRMP1W4RAZ","cloud-functions",null,"Complete guide for CloudBase cloud functions development - supports both Event Functions (Node.js) and HTTP Functions (multi-language Web services). Covers runtime selection, deployment, logging, invocation, scf_bootstrap, SSE, WebSocket, and HTTP access configuration.","welflau\u002Fai-dev-system","welflau","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7010385?v=4","01M6HPTDGF18RFY07M229P8CTM","01M6HPTDMRMZCJPYBFEA9XVVYT",3,"MIT","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fcloudbase\u002Fskills\u002Fcloudbase\u002Freferences\u002Fcloud-functions\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"cloud functions","cloud","functions","guide","web services","cloudbase","for","event","complete","false","runtime","selection","http","node","access","sse","websocket","logging","development","deployment","bootstrap","2026-11-10 10:12:30",false,"---\nname: cloud-functions\ndescription: Complete guide for CloudBase cloud functions development - supports both Event Functions (Node.js) and HTTP Functions (multi-language Web services). Covers runtime selection, deployment, logging, invocation, scf_bootstrap, SSE, WebSocket, and HTTP access configuration.\nalwaysApply: false\n---\n\n# Cloud Functions Development\n\nUse this skill when developing, deploying, and managing CloudBase cloud functions. CloudBase supports two types of cloud functions:\n\n- **Event Functions (普通云函数)**: Traditional serverless functions triggered by events (SDK calls, timers)\n- **HTTP Functions (HTTP 云函数)**: Web service functions triggered by HTTP requests, supporting multiple languages\n\n## When to use this skill\n\nUse this skill for **cloud function operations** when you need to:\n\n- Create and deploy Event Functions (Node.js)\n- Create and deploy HTTP Functions (Node.js\u002FPython\u002FGo\u002FJava)\n- Understand runtime limitations and selection\n- Query function logs and monitor execution\n- Invoke cloud functions from applications\n- Configure HTTP access for cloud functions\n- Implement SSE (Server-Sent Events) or WebSocket\n\n**Do NOT use for:**\n- CloudRun backend services (use `cloudrun-development` skill)\n- Complex container-based services (use `cloudrun-development` skill)\n- Database operations (use database skills)\n\n## How to use this skill (for a coding agent)\n\n1. **Choose the right function type**\n   - **Event Function**: For SDK calls, scheduled tasks, event-driven scenarios\n   - **HTTP Function**: For Web APIs, REST services, SSE\u002FWebSocket, multi-language support\n\n2. **Understand runtime limitations**\n   - Runtime **CANNOT be changed** after function creation\n   - Must select correct runtime during initial creation\n   - If runtime needs to change, must delete and recreate function\n\n3. **Deploy functions correctly**\n   - **MCP Tool**: Use `createFunction` with `type: \"Event\"` or `type: \"HTTP\"`\n   - **CLI**: Use `tcb fn deploy` (Event) or `tcb fn deploy --httpFn` (HTTP)\n   - HTTP Functions require `scf_bootstrap` file in the function directory\n   - Provide correct `functionRootPath` (parent directory of function folder)\n\n4. **Query logs properly**\n   - Use `getFunctionLogs` for log list (basic info)\n   - Use `getFunctionLogDetail` with RequestId for detailed logs\n   - Note time range limitations (max 1 day interval)\n\n---\n\n## Function Types Comparison\n\n| Feature | Event Function (普通云函数) | HTTP Function (HTTP 云函数) |\n|---------|---------------------------|----------------------------|\n| Trigger | Event-driven (SDK, timer) | HTTP request |\n| Entry Point | `exports.main = async (event, context) => {}` | Web Server (Express\u002FFlask\u002FGin etc.) |\n| Port | No port required | **Must listen on port 9000** |\n| Bootstrap | Not required | Requires `scf_bootstrap` |\n| Connection | Short connection | Supports long connection |\n| Languages | Node.js only | Node.js, Python, Go, Java |\n| Protocols | N\u002FA | HTTP, SSE, WebSocket |\n| Use Cases | Event processing, scheduled tasks | Web APIs, REST services, real-time streaming |\n\n---\n\n## Core Knowledge - Event Functions\n\n### Runtime Environment\n\n**⚠️ CRITICAL: Runtime cannot be modified after function creation**\n\nOnce a cloud function is created with a specific runtime, the runtime **cannot be changed**. If you need a different runtime:\n\n1. Delete the existing function\n2. Create a new function with the desired runtime\n\n**Supported Node.js Runtimes:**\n\n- `Nodejs18.15` (Default, Recommended)\n- `Nodejs16.13`\n- `Nodejs14.18`\n- `Nodejs12.16`\n- `Nodejs10.15`\n- `Nodejs8.9`\n\n**Runtime Selection Guidelines:**\n\n- **Use `Nodejs18.15`** for new projects (default, most modern)\n- Choose older versions only if dependencies require specific Node.js versions\n- Consider security updates and support lifecycle\n- Test thoroughly with selected runtime before deployment\n\n### Event Function Structure\n\nEvent functions require:\n\n1. **Function Directory**: Contains function code\n   - Must have `index.js` (or specified entry file)\n   - Must export handler: `exports.main = async (event, context) => {}`\n   - Include `package.json` with dependencies\n\n2. **Function Root Path**: Parent directory containing function directories\n   - Example: If function is at `\u002Fproject\u002Fcloudfunctions\u002FmyFunction\u002F`\n   - `functionRootPath` should be `\u002Fproject\u002Fcloudfunctions\u002F`\n   - **Important**: Do NOT include function name in root path\n\n3. **Entry Point**: Default is `index.js` with `exports.main`\n   - Can be customized via `handler` parameter\n\n### Event Function Deployment\n\n**Creating New Functions:**\n\nUse `createFunction` tool (see MCP tool documentation for full parameter list):\n- **Important**: Always specify `func.runtime` explicitly (defaults to `Nodejs18.15`)\n- Provide `functionRootPath` as parent directory of function folders (absolute path)\n- Use `force=true` to overwrite existing function\n\n**Updating Function Code:**\n\nUse `updateFunctionCode` tool:\n- **⚠️ Note**: Only updates code, **cannot change runtime**\n- If runtime needs to change, delete and recreate function\n\n**Deployment Best Practices:**\n\n1. **Always specify runtime** explicitly when creating functions\n2. **Use absolute paths** for `functionRootPath`\n3. **Don't upload node_modules** - dependencies installed automatically\n4. **Test locally** before deployment when possible\n5. **Use environment variables** for configuration, not hardcoded values\n\n---\n\n## Core Knowledge - HTTP Functions\n\n### HTTP Function Overview\n\nHTTP Functions are optimized for Web service scenarios, supporting standard HTTP request\u002Fresponse patterns.\n\n**Key Characteristics:**\n- **Must listen on port 9000** (platform requirement)\n- Requires `scf_bootstrap` startup script\n- Supports multiple languages: Node.js, Python, Go, Java\n- Supports HTTP, SSE, WebSocket protocols\n\n### scf_bootstrap Startup Script\n\n**⚠️ CRITICAL: HTTP Functions require `scf_bootstrap` file**\n\n| Requirement | Description |\n|-------------|-------------|\n| File name | Must be exactly `scf_bootstrap` (no extension) |\n| Permission | Must have execute permission (`chmod +x scf_bootstrap`) |\n| Port | Must start server on port **9000** |\n| Line endings | Must use LF (Unix), not CRLF (Windows) |\n\n**Examples:**\n```bash\n# Node.js\n#!\u002Fbin\u002Fbash\nnode index.js\n\n# Python\n#!\u002Fbin\u002Fbash\nexport PYTHONPATH=\".\u002Fthird_party:$PYTHONPATH\"\n\u002Fvar\u002Flang\u002Fpython310\u002Fbin\u002Fpython3.10 app.py\n\n# Go\n#!\u002Fbin\u002Fbash\n.\u002Fmain\n\n# Java\n#!\u002Fbin\u002Fbash\njava -jar *.jar\n```\n\n### HTTP Function Structure & Example\n\n```\nmy-http-function\u002F\n├── scf_bootstrap      # Required: startup script\n├── package.json       # Dependencies\n└── index.js           # Application code\n```\n\n**Node.js Example (Express):**\n```javascript\nconst express = require('express');\nconst app = express();\n\napp.get('\u002F', (req, res) => res.json({ message: 'Hello!' }));\napp.listen(9000);  \u002F\u002F Must be port 9000\n```\n\n### HTTP Function Deployment\n\n**MCP Tool:**\n```javascript\ncreateFunction({\n  func: {\n    name: \"myHttpFunction\",\n    type: \"HTTP\",           \u002F\u002F Required for HTTP Function\n    protocolType: \"HTTP\",   \u002F\u002F \"HTTP\" (default) or \"WS\" (WebSocket)\n    timeout: 60\n  },\n  functionRootPath: \"\u002Fpath\u002Fto\u002Ffunctions\",\n  force: false\n})\n```\n\n**CLI:**\n```bash\ntcb fn deploy \u003Cname> --httpFn        # HTTP Function\ntcb fn deploy \u003Cname> --httpFn --ws   # With WebSocket\n```\n\n**⚠️ Notes:**\n- Function type **cannot be changed** after creation\n- HTTP Functions do NOT auto-install dependencies; include `node_modules` or use layers\n\n### Invoking HTTP Functions\n\n**Method 1: HTTP API (with Access Token)**\n```bash\ncurl -L 'https:\u002F\u002F{envId}.api.tcloudbasegateway.com\u002Fv1\u002Ffunctions\u002F{name}?webfn=true' \\\n  -H 'Authorization: Bearer \u003CTOKEN>'\n```\n**⚠️ Must include `webfn=true` parameter**\n\n**Method 2: HTTP Access Service (Custom Domain)**\n\nUse `createFunctionHTTPAccess` MCP tool to configure HTTP access:\n\n```javascript\ncreateFunctionHTTPAccess({\n  name: \"myHttpFunction\",\n  type: \"HTTP\",           \u002F\u002F \"HTTP\" for HTTP Function\n  path: \"\u002Fapi\u002Fhello\",     \u002F\u002F Trigger path\n  \u002F\u002F domain: \"your-domain.com\"  \u002F\u002F Optional custom domain\n})\n```\n\n```bash\n# Access via default domain\ncurl https:\u002F\u002F{envId}.{region}.app.tcloudbase.com\u002F{path}\n\n# Access via custom domain\ncurl https:\u002F\u002Fyour-domain.com\u002F{path}\n```\n\n| Method | Auth Required | Use Case |\n|--------|--------------|----------|\n| HTTP API (`?webfn=true`) | Yes (Bearer Token) | Server-to-server |\n| HTTP Access Service | Optional | Browser, public APIs |\n\n### SSE & WebSocket Support\n\n**SSE (Server-Sent Events):** Enabled by default, for server-to-client streaming (AI chat, progress updates).\n\n```javascript\n\u002F\u002F Server\nres.setHeader('Content-Type', 'text\u002Fevent-stream');\nres.write(`data: ${JSON.stringify({ content: 'Hello' })}\\n\\n`);\n\n\u002F\u002F Client\nconst es = new EventSource('https:\u002F\u002Fyour-domain\u002Fstream');\nes.onmessage = (e) => console.log(JSON.parse(e.data));\n```\n\n**WebSocket:** Enable via `protocolType: \"WS\"` in `createFunction`. For bidirectional real-time communication.\n\n| Limit | Value |\n|-------|-------|\n| Idle timeout | 10 - 7200 seconds |\n| Max message size | 256KB |\n\n```javascript\nconst wss = new WebSocket.Server({ port: 9000 });\nwss.on('connection', (ws) => {\n  ws.on('message', (msg) => ws.send(`Echo: ${msg}`));\n});\n```\n\n---\n\n### Function Logs\n\n**Querying Logs:**\n\n**Primary Method:** Use `getFunctionLogs` and `getFunctionLogDetail` tools (see MCP tool documentation).\n\n**Alternative Method (Plan B):** If tools unavailable, use `callCloudApi`:\n\n1. **Get Log List** - Use `GetFunctionLogs` action:\n```\ncallCloudApi({\n  service: \"tcb\",\n  action: \"GetFunctionLogs\",\n  params: {\n    EnvId: \"{envId}\",\n    FunctionName: \"functionName\",\n    Offset: 0,\n    Limit: 10,\n    StartTime: \"2024-01-01 00:00:00\",\n    EndTime: \"2024-01-01 23:59:59\",\n    LogRequestId: \"optional-request-id\",\n    Qualifier: \"$LATEST\"\n  }\n})\n```\n\n2. **Get Log Details** - Use `GetFunctionLogDetail` action (requires LogRequestId from step 1):\n```\ncallCloudApi({\n  service: \"tcb\",\n  action: \"GetFunctionLogDetail\",\n  params: {\n    StartTime: \"2024-01-01 00:00:00\",\n    EndTime: \"2024-01-01 23:59:59\",\n    LogRequestId: \"request-id-from-log-list\"\n  }\n})\n```\n\n**Log Query Limitations:**\n\n- `Offset + Limit` cannot exceed 10000\n- `StartTime` and `EndTime` interval cannot exceed 1 day\n- Use pagination for large time ranges\n\n**Log Query Best Practices:**\n\n1. Query logs within 1-day windows\n2. Use RequestId for specific invocation debugging\n3. Combine list and detail queries for comprehensive debugging\n4. Check logs after deployment to verify function behavior\n\n### Invoking Event Functions\n\n**From Web Applications:**\n\n```javascript\nimport cloudbaseSDK from \"@cloudbase\u002Fjs-sdk\";\n\nconst cloudbase = cloudbaseSDK.init({\n  env: 'your-env-id',\n  region: 'ap-shanghai',\n  accessKey: 'your-access-key'\n});\n\n\u002F\u002F Call event function\nconst result = await cloudbase.callFunction({\n  name: \"functionName\",\n  data: { \u002F* function parameters *\u002F }\n});\n```\n\n**From Mini Programs:**\n\n```javascript\nwx.cloud.callFunction({\n  name: \"functionName\",\n  data: { \u002F* function parameters *\u002F }\n}).then(res => {\n  console.log(res.result);\n});\n```\n\n**From Node.js Backend:**\n\n```javascript\nconst cloudbase = require(\"@cloudbase\u002Fnode-sdk\");\n\nconst app = cloudbase.init({\n  env: \"your-env-id\"\n});\n\nconst result = await app.callFunction({\n  name: \"functionName\",\n  data: { \u002F* function parameters *\u002F }\n});\n```\n\n**From HTTP API:**\n\nUse CloudBase HTTP API to invoke event functions:\n- Endpoint: `https:\u002F\u002F{envId}.api.tcloudbasegateway.com\u002Fv1\u002Ffunctions\u002F{functionName}`\n- Requires authentication token (Bearer Token)\n- See `http-api` skill for details\n\n### HTTP Access Configuration (for Event Functions)\n\n**HTTP Access vs HTTP API:**\n\n- **HTTP API**: Uses CloudBase API endpoint with authentication token\n- **HTTP Access**: Creates direct HTTP\u002FHTTPS endpoint for standard REST API access without SDK\n\n**Creating HTTP Access:**\n\n**Primary Method:** Use `createFunctionHTTPAccess` tool (see MCP tool documentation).\n\n**Alternative Method (Plan B):** If tool unavailable, use `callCloudApi` with `CreateCloudBaseGWAPI`:\n\n```\ncallCloudApi({\n  service: \"tcb\",\n  action: \"CreateCloudBaseGWAPI\",\n  params: {\n    EnableUnion: true,\n    Path: \"\u002Fapi\u002Fusers\",\n    ServiceId: \"{envId}\",\n    Type: 6,\n    Name: \"functionName\",\n    AuthSwitch: 2,\n    PathTransmission: 2,\n    EnableRegion: true,\n    Domain: \"*\"  \u002F\u002F Use \"*\" for default domain, or custom domain name\n  }\n})\n```\n\n**Key Parameters:**\n- `Type: 6` - Cloud Function type (required)\n- `AuthSwitch: 2` - No auth (1 = with auth)\n- `Domain: \"*\"` - Default domain, or specify custom domain\n\n**Access URL:** `https:\u002F\u002F{envId}.{region}.app.tcloudbase.com\u002F{path}` or `https:\u002F\u002F{domain}\u002F{path}`\n\n### Function Configuration\n\n**Environment Variables:**\n\nSet via `func.envVariables` when creating\u002Fupdating:\n```javascript\n{\n  envVariables: {\n    \"DATABASE_URL\": \"mysql:\u002F\u002F...\",\n    \"API_KEY\": \"secret-key\"\n  }\n}\n```\n\n**⚠️ CRITICAL: Environment Variable Update Constraint**\n\nWhen updating environment variables for existing functions:\n\n1. **MUST first query current environment variables** using `getFunctionList` with `action=detail` to get the function's current configuration\n2. **MUST merge** new environment variables with existing ones\n3. **DO NOT directly overwrite** - this will delete existing environment variables not included in the update\n\n**Correct Update Pattern:**\n\n```javascript\n\u002F\u002F 1. First, get current function details\nconst currentFunction = await getFunctionList({\n  action: \"detail\",\n  name: \"functionName\"\n});\n\n\u002F\u002F 2. Merge existing envVariables with new ones\nconst mergedEnvVariables = {\n  ...currentFunction.EnvVariables,  \u002F\u002F Existing variables\n  ...newEnvVariables                 \u002F\u002F New\u002Fupdated variables\n};\n\n\u002F\u002F 3. Update with merged variables\nawait updateFunctionConfig({\n  funcParam: {\n    name: \"functionName\",\n    envVariables: mergedEnvVariables\n  }\n});\n```\n\n**Why This Matters:**\n\n- Direct overwrite will **delete** all environment variables not included in the update\n- This can break function functionality if critical variables are removed\n- Always preserve existing configuration when making partial updates\n\n**Timeout Configuration:**\n\nSet via `func.timeout` (in seconds):\n- Default timeout varies by runtime\n- Maximum timeout depends on runtime version\n- Consider function execution time when setting\n\n**Timer Triggers:**\n\nConfigure via `func.triggers`:\n- Type: `timer` (only supported type)\n- Config: Cron expression (7 fields: second minute hour day month week year)\n- Examples:\n  - `\"0 0 2 1 * * *\"` - 2:00 AM on 1st of every month\n  - `\"0 30 9 * * * *\"` - 9:30 AM every day\n\n**VPC Configuration:**\n\nFor accessing VPC resources:\n```javascript\n{\n  vpc: {\n    vpcId: \"vpc-xxxxx\",\n    subnetId: \"subnet-xxxxx\"\n  }\n}\n```\n\n## MCP Tools Reference\n\n**Function Management:**\n- `getFunctionList` - List functions or get function details\n- `createFunction` - Create cloud function (supports both Event and HTTP types via `type` parameter)\n  - `type: \"Event\"` - Event Function (default)\n  - `type: \"HTTP\"` - HTTP Function\n  - `protocolType: \"WS\"` - Enable WebSocket for HTTP Function\n- `updateFunctionCode` - Update function code (runtime cannot change)\n- `updateFunctionConfig` - Update function configuration (⚠️ when updating envVariables, must first query and merge with existing values to avoid overwriting)\n\n**Logging:**\n- `getFunctionLogs` - Get function log list (basic info)\n- `getFunctionLogDetail` - Get detailed log content by RequestId\n- `callCloudApi` (Plan B) - Use `GetFunctionLogs` and `GetFunctionLogDetail` actions if direct tools unavailable\n\n**HTTP Access:**\n- `createFunctionHTTPAccess` - Create HTTP access for function (supports both Event and HTTP types via `type` parameter)\n- `callCloudApi` (Plan B) - Use `CreateCloudBaseGWAPI` action if direct tool unavailable\n\n**Triggers:**\n- `manageFunctionTriggers` - Create or delete function triggers\n\n**CLI Commands:**\n- `tcb fn deploy \u003Cname>` - Deploy Event Function\n- `tcb fn deploy \u003Cname> --httpFn` - Deploy HTTP Function\n- `tcb fn deploy \u003Cname> --httpFn --ws` - Deploy HTTP Function with WebSocket\n- `tcb fn deploy --all` - Deploy all functions in config\n\n## Common Patterns\n\n### Error Handling\n\n```javascript\nexports.main = async (event, context) => {\n  try {\n    \u002F\u002F Function logic\n    return {\n      code: 0,\n      message: \"Success\",\n      data: result\n    };\n  } catch (error) {\n    return {\n      code: -1,\n      message: error.message,\n      data: null\n    };\n  }\n};\n```\n\n### Environment Variable Usage\n\n```javascript\nexports.main = async (event, context) => {\n  const apiKey = process.env.API_KEY;\n  const dbUrl = process.env.DATABASE_URL;\n  \n  \u002F\u002F Use environment variables\n};\n```\n\n### Database Operations\n\n```javascript\nconst cloudbase = require(\"@cloudbase\u002Fnode-sdk\");\n\nconst app = cloudbase.init({\n  env: process.env.ENV_ID\n});\n\nexports.main = async (event, context) => {\n  const db = app.database();\n  const result = await db.collection(\"users\").get();\n  return result;\n};\n```\n\n## Best Practices\n\n### General Best Practices\n1. **Runtime Selection**: Always specify runtime explicitly, use `Nodejs18.15` for new projects\n2. **Code Organization**: Keep functions focused and single-purpose\n3. **Error Handling**: Always implement proper error handling\n4. **Environment Variables**: Use env vars for configuration, never hardcode secrets\n5. **Logging**: Add meaningful logs for debugging\n6. **Testing**: Test functions locally when possible before deployment\n7. **Security**: Implement authentication\u002Fauthorization for HTTP access\n8. **Performance**: Optimize cold start time, use connection pooling for databases\n9. **Monitoring**: Regularly check logs and monitor function performance\n10. **Documentation**: Document function parameters and return values\n\n### HTTP Function Specific Best Practices\n1. **Port Configuration**: Always listen on port 9000\n2. **scf_bootstrap**: Ensure correct file permissions and LF line endings\n3. **Health Check**: Add `\u002Fhealth` endpoint for monitoring\n4. **CORS**: Configure CORS headers for browser access\n5. **Graceful Shutdown**: Handle process signals properly\n6. **Dependencies**: Include `node_modules` in package or use layers (no auto-install for HTTP Functions)\n7. **Timeout**: Set appropriate timeout for long-running SSE\u002FWebSocket connections\n8. **Error Responses**: Return proper HTTP status codes and error messages\n\n### Choosing Between Event and HTTP Functions\n\n| Scenario | Recommended Type |\n|----------|-----------------|\n| SDK\u002FMini Program calls | Event Function |\n| Scheduled tasks (cron) | Event Function |\n| REST API \u002F Web services | HTTP Function |\n| SSE streaming (AI chat) | HTTP Function |\n| WebSocket real-time | HTTP Function |\n| File upload\u002Fdownload | HTTP Function |\n| Multi-language support | HTTP Function |\n\n## Related Skills\n\n- `cloudrun-development` - For container-based backend services\n- `http-api` - For HTTP API invocation patterns\n- `cloudbase-platform` - For general CloudBase platform knowledge\n\n","# Cloud Functions Development\n\nUse this skill when developing, deploying, and managing CloudBase cloud functions. CloudBase supports two types of cloud functions:\n\n- **Event Functions (普通云函数)**: Traditional serverless functions triggered by events (SDK calls, timers)\n- **HTTP Functions (HTTP 云函数)**: Web service functions triggered by HTTP requests, supporting multiple languages\n\n## When to use this skill\n\nUse this skill for **cloud function operations** when you need to:\n\n- Create and deploy Event Functions (Node.js)\n- Create and deploy HTTP Functions (Node.js\u002FPython\u002FGo\u002FJava)\n- Understand runtime limitations and selection\n- Query function logs and monitor execution\n- Invoke cloud functions from applications\n- Configure HTTP access for cloud functions\n- Implement SSE (Server-Sent Events) or WebSocket\n\n**Do NOT use for:**\n- CloudRun backend services (use `cloudrun-development` skill)\n- Complex container-based services (use `cloudrun-development` skill)\n- Database operations (use database skills)\n\n## How to use this skill (for a coding agent)\n\n1. **Choose the right function type**\n   - **Event Function**: For SDK calls, scheduled tasks, event-driven scenarios\n   - **HTTP Function**: For Web APIs, REST services, SSE\u002FWebSocket, multi-language support\n\n2. **Understand runtime limitations**\n   - Runtime **CANNOT be changed** after function creation\n   - Must select correct runtime during initial creation\n   - If runtime needs to change, must delete and recreate function\n\n3. **Deploy functions correctly**\n   - **MCP Tool**: Use `createFunction` with `type: \"Event\"` or `type: \"HTTP\"`\n   - **CLI**: Use `tcb fn deploy` (Event) or `tcb fn deploy --httpFn` (HTTP)\n   - HTTP Functions require `scf_bootstrap` file in the function directory\n   - Provide correct `functionRootPath` (parent directory of function folder)\n\n4. **Query logs properly**\n   - Use `getFunctionLogs` for log list (basic info)\n   - Use `getFunctionLogDetail` with RequestId for detailed logs\n   - Note time range limitations (max 1 day interval)\n\n---\n\n## Function Types Comparison\n\n| Feature | Event Function (普通云函数) | HTTP Function (HTTP 云函数) |\n|---------|---------------------------|----------------------------|\n| Trigger | Event-driven (SDK, timer) | HTTP request |\n| Entry Point | `exports.main = async (event, context) => {}` | Web Server (Express\u002FFlask\u002FGin etc.) |\n| Port | No port required | **Must listen on port 9000** |\n| Bootstrap | Not required | Requires `scf_bootstrap` |\n| Connection | Short connection | Supports long connection |\n| Languages | Node.js only | Node.js, Python, Go, Java |\n| Protocols | N\u002FA | HTTP, SSE, WebSocket |\n| Use Cases | Event processing, scheduled tasks | Web APIs, REST services, real-time streaming |\n\n---\n\n## Core Knowledge - Event Functions\n\n### Runtime Environment\n\n**⚠️ CRITICAL: Runtime cannot be modified after function creation**\n\nOnce a cloud function is created with a specific runtime, the runtime **cannot be changed**. If you need a different runtime:\n\n1. Delete the existing function\n2. Create a new function with the desired runtime\n\n**Supported Node.js Runtimes:**\n\n- `Nodejs18.15` (Default, Recommended)\n- `Nodejs16.13`\n- `Nodejs14.18`\n- `Nodejs12.16`\n- `Nodejs10.15`\n- `Nodejs8.9`\n\n**Runtime Selection Guidelines:**\n\n- **Use `Nodejs18.15`** for new projects (default, most modern)\n- Choose older versions only if dependencies require specific Node.js versions\n- Consider security updates and support lifecycle\n- Test thoroughly with selected runtime before deployment\n\n### Event Function Structure\n\nEvent functions require:\n\n1. **Function Directory**: Contains function code\n   - Must have `index.js` (or specified entry file)\n   - Must export handler: `exports.main = async (event, context) => {}`\n   - Include `package.json` with dependencies\n\n2. **Function Root Path**: Parent directory containing function directories\n   - Example: If function is at `\u002Fproject\u002Fcloudfunctions\u002FmyFunction\u002F`\n   - `functionRootPath` should be `\u002Fproject\u002Fcloudfunctions\u002F`\n   - **Important**: Do NOT include function name in root path\n\n3. **Entry Point**: Default is `index.js` with `exports.main`\n   - Can be customized via `handler` parameter\n\n### Event Function Deployment\n\n**Creating New Functions:**\n\nUse `createFunction` tool (see MCP tool documentation for full parameter list):\n- **Important**: Always specify `func.runtime` explicitly (defaults to `Nodejs18.15`)\n- Provide `functionRootPath` as parent directory of function folders (absolute path)\n- Use `force=true` to overwrite existing function\n\n**Updating Function Code:**\n\nUse `updateFunctionCode` tool:\n- **⚠️ Note**: Only updates code, **cannot change runtime**\n- If runtime needs to change, delete and recreate function\n\n**Deployment Best Practices:**\n\n1. **Always specify runtime** explicitly when creating functions\n2. **Use absolute paths** for `functionRootPath`\n3. **Don't upload node_modules** - dependencies installed automatically\n4. **Test locally** before deployment when possible\n5. **Use environment variables** for configuration, not hardcoded values\n\n---\n\n## Core Knowledge - HTTP Functions\n\n### HTTP Function Overview\n\nHTTP Functions are optimized for Web service scenarios, supporting standard HTTP request\u002Fresponse patterns.\n\n**Key Characteristics:**\n- **Must listen on port 9000** (platform requirement)\n- Requires `scf_bootstrap` startup script\n- Supports multiple languages: Node.js, Python, Go, Java\n- Supports HTTP, SSE, WebSocket protocols\n\n### scf_bootstrap Startup Script\n\n**⚠️ CRITICAL: HTTP Functions require `scf_bootstrap` file**\n\n| Requirement | Description |\n|-------------|-------------|\n| File name | Must be exactly `scf_bootstrap` (no extension) |\n| Permission | Must have execute permission (`chmod +x scf_bootstrap`) |\n| Port | Must start server on port **9000** |\n| Line endings | Must use LF (Unix), not CRLF (Windows) |\n\n**Examples:**\n```bash\n# Node.js\n#!\u002Fbin\u002Fbash\nnode index.js\n\n# Python\n#!\u002Fbin\u002Fbash\nexport PYTHONPATH=\".\u002Fthird_party:$PYTHONPATH\"\n\u002Fvar\u002Flang\u002Fpython310\u002Fbin\u002Fpython3.10 app.py\n\n# Go\n#!\u002Fbin\u002Fbash\n.\u002Fmain\n\n# Java\n#!\u002Fbin\u002Fbash\njava -jar *.jar\n```\n\n### HTTP Function Structure & Example\n\n```\nmy-http-function\u002F\n├── scf_bootstrap      # Required: startup script\n├── package.json       # Dependencies\n└── index.js           # Application code\n```\n\n**Node.js Example (Express):**\n```javascript\nconst express = require('express');\nconst app = express();\n\napp.get('\u002F', (req, res) => res.json({ message: 'Hello!' }));\napp.listen(9000);  \u002F\u002F Must be port 9000\n```\n\n### HTTP Function Deployment\n\n**MCP Tool:**\n```javascript\ncreateFunction({\n  func: {\n    name: \"myHttpFunction\",\n    type: \"HTTP\",           \u002F\u002F Required for HTTP Function\n    protocolType: \"HTTP\",   \u002F\u002F \"HTTP\" (default) or \"WS\" (WebSocket)\n    timeout: 60\n  },\n  functionRootPath: \"\u002Fpath\u002Fto\u002Ffunctions\",\n  force: false\n})\n```\n\n**CLI:**\n```bash\ntcb fn deploy \u003Cname> --httpFn        # HTTP Function\ntcb fn deploy \u003Cname> --httpFn --ws   # With WebSocket\n```\n\n**⚠️ Notes:**\n- Function type **cannot be changed** after creation\n- HTTP Functions do NOT auto-install dependencies; include `node_modules` or use layers\n\n### Invoking HTTP Functions\n\n**Method 1: HTTP API (with Access Token)**\n```bash\ncurl -L 'https:\u002F\u002F{envId}.api.tcloudbasegateway.com\u002Fv1\u002Ffunctions\u002F{name}?webfn=true' \\\n  -H 'Authorization: Bearer \u003CTOKEN>'\n```\n**⚠️ Must include `webfn=true` parameter**\n\n**Method 2: HTTP Access Service (Custom Domain)**\n\nUse `createFunctionHTTPAccess` MCP tool to configure HTTP access:\n\n```javascript\ncreateFunctionHTTPAccess({\n  name: \"myHttpFunction\",\n  type: \"HTTP\",           \u002F\u002F \"HTTP\" for HTTP Function\n  path: \"\u002Fapi\u002Fhello\",     \u002F\u002F Trigger path\n  \u002F\u002F domain: \"your-domain.com\"  \u002F\u002F Optional custom domain\n})\n```\n\n```bash\n# Access via default domain\ncurl https:\u002F\u002F{envId}.{region}.app.tcloudbase.com\u002F{path}\n\n# Access via custom domain\ncurl https:\u002F\u002Fyour-domain.com\u002F{path}\n```\n\n| Method | Auth Required | Use Case |\n|--------|--------------|----------|\n| HTTP API (`?webfn=true`) | Yes (Bearer Token) | Server-to-server |\n| HTTP Access Service | Optional | Browser, public APIs |\n\n### SSE & WebSocket Support\n\n**SSE (Server-Sent Events):** Enabled by default, for server-to-client streaming (AI chat, progress updates).\n\n```javascript\n\u002F\u002F Server\nres.setHeader('Content-Type', 'text\u002Fevent-stream');\nres.write(`data: ${JSON.stringify({ content: 'Hello' })}\\n\\n`);\n\n\u002F\u002F Client\nconst es = new EventSource('https:\u002F\u002Fyour-domain\u002Fstream');\nes.onmessage = (e) => console.log(JSON.parse(e.data));\n```\n\n**WebSocket:** Enable via `protocolType: \"WS\"` in `createFunction`. For bidirectional real-time communication.\n\n| Limit | Value |\n|-------|-------|\n| Idle timeout | 10 - 7200 seconds |\n| Max message size | 256KB |\n\n```javascript\nconst wss = new WebSocket.Server({ port: 9000 });\nwss.on('connection', (ws) => {\n  ws.on('message', (msg) => ws.send(`Echo: ${msg}`));\n});\n```\n\n---\n\n### Function Logs\n\n**Querying Logs:**\n\n**Primary Method:** Use `getFunctionLogs` and `getFunctionLogDetail` tools (see MCP tool documentation).\n\n**Alternative Method (Plan B):** If tools unavailable, use `callCloudApi`:\n\n1. **Get Log List** - Use `GetFunctionLogs` action:\n```\ncallCloudApi({\n  service: \"tcb\",\n  action: \"GetFunctionLogs\",\n  params: {\n    EnvId: \"{envId}\",\n    FunctionName: \"functionName\",\n    Offset: 0,\n    Limit: 10,\n    StartTime: \"2024-01-01 00:00:00\",\n    EndTime: \"2024-01-01 23:59:59\",\n    LogRequestId: \"optional-request-id\",\n    Qualifier: \"$LATEST\"\n  }\n})\n```\n\n2. **Get Log Details** - Use `GetFunctionLogDetail` action (requires LogRequestId from step 1):\n```\ncallCloudApi({\n  service: \"tcb\",\n  action: \"GetFunctionLogDetail\",\n  params: {\n    StartTime: \"2024-01-01 00:00:00\",\n    EndTime: \"2024-01-01 23:59:59\",\n    LogRequestId: \"request-id-from-log-list\"\n  }\n})\n```\n\n**Log Query Limitations:**\n\n- `Offset + Limit` cannot exceed 10000\n- `StartTime` and `EndTime` interval cannot exceed 1 day\n- Use pagination for large time ranges\n\n**Log Query Best Practices:**\n\n1. Query logs within 1-day windows\n2. Use RequestId for specific invocation debugging\n3. Combine list and detail queries for comprehensive debugging\n4. Check logs after deployment to verify function behavior\n\n### Invoking Event Functions\n\n**From Web Applications:**\n\n```javascript\nimport cloudbaseSDK from \"@cloudbase\u002Fjs-sdk\";\n\nconst cloudbase = cloudbaseSDK.init({\n  env: 'your-env-id',\n  region: 'ap-shanghai',\n  accessKey: 'your-access-key'\n});\n\n\u002F\u002F Call event function\nconst result = await cloudbase.callFunction({\n  name: \"functionName\",\n  data: { \u002F* function parameters *\u002F }\n});\n```\n\n**From Mini Programs:**\n\n```javascript\nwx.cloud.callFunction({\n  name: \"functionName\",\n  data: { \u002F* function parameters *\u002F }\n}).then(res => {\n  console.log(res.result);\n});\n```\n\n**From Node.js Backend:**\n\n```javascript\nconst cloudbase = require(\"@cloudbase\u002Fnode-sdk\");\n\nconst app = cloudbase.init({\n  env: \"your-env-id\"\n});\n\nconst result = await app.callFunction({\n  name: \"functionName\",\n  data: { \u002F* function parameters *\u002F }\n});\n```\n\n**From HTTP API:**\n\nUse CloudBase HTTP API to invoke event functions:\n- Endpoint: `https:\u002F\u002F{envId}.api.tcloudbasegateway.com\u002Fv1\u002Ffunctions\u002F{functionName}`\n- Requires authentication token (Bearer Token)\n- See `http-api` skill for details\n\n### HTTP Access Configuration (for Event Functions)\n\n**HTTP Access vs HTTP API:**\n\n- **HTTP API**: Uses CloudBase API endpoint with authentication token\n- **HTTP Access**: Creates direct HTTP\u002FHTTPS endpoint for standard REST API access without SDK\n\n**Creating HTTP Access:**\n\n**Primary Method:** Use `createFunctionHTTPAccess` tool (see MCP tool documentation).\n\n**Alternative Method (Plan B):** If tool unavailable, use `callCloudApi` with `CreateCloudBaseGWAPI`:\n\n```\ncallCloudApi({\n  service: \"tcb\",\n  action: \"CreateCloudBaseGWAPI\",\n  params: {\n    EnableUnion: true,\n    Path: \"\u002Fapi\u002Fusers\",\n    ServiceId: \"{envId}\",\n    Type: 6,\n    Name: \"functionName\",\n    AuthSwitch: 2,\n    PathTransmission: 2,\n    EnableRegion: true,\n    Domain: \"*\"  \u002F\u002F Use \"*\" for default domain, or custom domain name\n  }\n})\n```\n\n**Key Parameters:**\n- `Type: 6` - Cloud Function type (required)\n- `AuthSwitch: 2` - No auth (1 = with auth)\n- `Domain: \"*\"` - Default domain, or specify custom domain\n\n**Access URL:** `https:\u002F\u002F{envId}.{region}.app.tcloudbase.com\u002F{path}` or `https:\u002F\u002F{domain}\u002F{path}`\n\n### Function Configuration\n\n**Environment Variables:**\n\nSet via `func.envVariables` when creating\u002Fupdating:\n```javascript\n{\n  envVariables: {\n    \"DATABASE_URL\": \"mysql:\u002F\u002F...\",\n    \"API_KEY\": \"secret-key\"\n  }\n}\n```\n\n**⚠️ CRITICAL: Environment Variable Update Constraint**\n\nWhen updating environment variables for existing functions:\n\n1. **MUST first query current environment variables** using `getFunctionList` with `action=detail` to get the function's current configuration\n2. **MUST merge** new environment variables with existing ones\n3. **DO NOT directly overwrite** - this will delete existing environment variables not included in the update\n\n**Correct Update Pattern:**\n\n```javascript\n\u002F\u002F 1. First, get current function details\nconst currentFunction = await getFunctionList({\n  action: \"detail\",\n  name: \"functionName\"\n});\n\n\u002F\u002F 2. Merge existing envVariables with new ones\nconst mergedEnvVariables = {\n  ...currentFunction.EnvVariables,  \u002F\u002F Existing variables\n  ...newEnvVariables                 \u002F\u002F New\u002Fupdated variables\n};\n\n\u002F\u002F 3. Update with merged variables\nawait updateFunctionConfig({\n  funcParam: {\n    name: \"functionName\",\n    envVariables: mergedEnvVariables\n  }\n});\n```\n\n**Why This Matters:**\n\n- Direct overwrite will **delete** all environment variables not included in the update\n- This can break function functionality if critical variables are removed\n- Always preserve existing configuration when making partial updates\n\n**Timeout Configuration:**\n\nSet via `func.timeout` (in seconds):\n- Default timeout varies by runtime\n- Maximum timeout depends on runtime version\n- Consider function execution time when setting\n\n**Timer Triggers:**\n\nConfigure via `func.triggers`:\n- Type: `timer` (only supported type)\n- Config: Cron expression (7 fields: second minute hour day month week year)\n- Examples:\n  - `\"0 0 2 1 * * *\"` - 2:00 AM on 1st of every month\n  - `\"0 30 9 * * * *\"` - 9:30 AM every day\n\n**VPC Configuration:**\n\nFor accessing VPC resources:\n```javascript\n{\n  vpc: {\n    vpcId: \"vpc-xxxxx\",\n    subnetId: \"subnet-xxxxx\"\n  }\n}\n```\n\n## MCP Tools Reference\n\n**Function Management:**\n- `getFunctionList` - List functions or get function details\n- `createFunction` - Create cloud function (supports both Event and HTTP types via `type` parameter)\n  - `type: \"Event\"` - Event Function (default)\n  - `type: \"HTTP\"` - HTTP Function\n  - `protocolType: \"WS\"` - Enable WebSocket for HTTP Function\n- `updateFunctionCode` - Update function code (runtime cannot change)\n- `updateFunctionConfig` - Update function configuration (⚠️ when updating envVariables, must first query and merge with existing values to avoid overwriting)\n\n**Logging:**\n- `getFunctionLogs` - Get function log list (basic info)\n- `getFunctionLogDetail` - Get detailed log content by RequestId\n- `callCloudApi` (Plan B) - Use `GetFunctionLogs` and `GetFunctionLogDetail` actions if direct tools unavailable\n\n**HTTP Access:**\n- `createFunctionHTTPAccess` - Create HTTP access for function (supports both Event and HTTP types via `type` parameter)\n- `callCloudApi` (Plan B) - Use `CreateCloudBaseGWAPI` action if direct tool unavailable\n\n**Triggers:**\n- `manageFunctionTriggers` - Create or delete function triggers\n\n**CLI Commands:**\n- `tcb fn deploy \u003Cname>` - Deploy Event Function\n- `tcb fn deploy \u003Cname> --httpFn` - Deploy HTTP Function\n- `tcb fn deploy \u003Cname> --httpFn --ws` - Deploy HTTP Function with WebSocket\n- `tcb fn deploy --all` - Deploy all functions in config\n\n## Common Patterns\n\n### Error Handling\n\n```javascript\nexports.main = async (event, context) => {\n  try {\n    \u002F\u002F Function logic\n    return {\n      code: 0,\n      message: \"Success\",\n      data: result\n    };\n  } catch (error) {\n    return {\n      code: -1,\n      message: error.message,\n      data: null\n    };\n  }\n};\n```\n\n### Environment Variable Usage\n\n```javascript\nexports.main = async (event, context) => {\n  const apiKey = process.env.API_KEY;\n  const dbUrl = process.env.DATABASE_URL;\n  \n  \u002F\u002F Use environment variables\n};\n```\n\n### Database Operations\n\n```javascript\nconst cloudbase = require(\"@cloudbase\u002Fnode-sdk\");\n\nconst app = cloudbase.init({\n  env: process.env.ENV_ID\n});\n\nexports.main = async (event, context) => {\n  const db = app.database();\n  const result = await db.collection(\"users\").get();\n  return result;\n};\n```\n\n## Best Practices\n\n### General Best Practices\n1. **Runtime Selection**: Always specify runtime explicitly, use `Nodejs18.15` for new projects\n2. **Code Organization**: Keep functions focused and single-purpose\n3. **Error Handling**: Always implement proper error handling\n4. **Environment Variables**: Use env vars for configuration, never hardcode secrets\n5. **Logging**: Add meaningful logs for debugging\n6. **Testing**: Test functions locally when possible before deployment\n7. **Security**: Implement authentication\u002Fauthorization for HTTP access\n8. **Performance**: Optimize cold start time, use connection pooling for databases\n9. **Monitoring**: Regularly check logs and monitor function performance\n10. **Documentation**: Document function parameters and return values\n\n### HTTP Function Specific Best Practices\n1. **Port Configuration**: Always listen on port 9000\n2. **scf_bootstrap**: Ensure correct file permissions and LF line endings\n3. **Health Check**: Add `\u002Fhealth` endpoint for monitoring\n4. **CORS**: Configure CORS headers for browser access\n5. **Graceful Shutdown**: Handle process signals properly\n6. **Dependencies**: Include `node_modules` in package or use layers (no auto-install for HTTP Functions)\n7. **Timeout**: Set appropriate timeout for long-running SSE\u002FWebSocket connections\n8. **Error Responses**: Return proper HTTP status codes and error messages\n\n### Choosing Between Event and HTTP Functions\n\n| Scenario | Recommended Type |\n|----------|-----------------|\n| SDK\u002FMini Program calls | Event Function |\n| Scheduled tasks (cron) | Event Function |\n| REST API \u002F Web services | HTTP Function |\n| SSE streaming (AI chat) | HTTP Function |\n| WebSocket real-time | HTTP Function |\n| File upload\u002Fdownload | HTTP Function |\n| Multi-language support | HTTP Function |\n\n## Related Skills\n\n- `cloudrun-development` - For container-based backend services\n- `http-api` - For HTTP API invocation patterns\n- `cloudbase-platform` - For general CloudBase platform knowledge\n\n",{"name":5,"alwaysApply":45,"description":7},"main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fcloudbase\u002Fskills\u002Fcloudbase\u002Freferences\u002Fcloud-functions",1,"https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system","https:\u002F\u002Fgithub.com\u002Fwelflau","2026-11-10 11:14:25",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add welflau\u002Fai-dev-system --skill cloud-functions",{"tool":62,"command":63},"bunx","bunx skills add welflau\u002Fai-dev-system --skill cloud-functions",{"tool":65,"command":66},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill cloud-functions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fcloudbase\u002Fskills\u002Fcloudbase\u002Freferences\u002Fcloud-functions\u002FSKILL.md",true,[],[71,103,135,160,186,208],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":82,"publishedAt":44},"01M6HSTDP4M3JFXEBK91VFB4PA","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FSKILL.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,29,102],"web artifacts builder","web","artifacts","artifacts builder","builder","frontend","css","components","react","routing","state management","state","file","Tailwind","use","single-file","simple","ui components","multi","single",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":119,"publishedAt":44},"01M6HSDXH0JSP8R3QTNY9XZ8HN","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FSKILL.md",[110,111,114],{"categoryNo":80,"categoryName":81,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[88,120,121,89,84,90,91,122,123,124,85,125,126,127,97,128,129,130,131,132,133,134],"design","frontend design","react components","create","code","examples","applications","landing","ui design","pages","aesthetics","web ui","with","generic","when",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":44},"01M6HSA77QYVP7A72HREGTDN2C","algorithmic-art","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FSKILL.md",[142],{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},[144,145,146,123,124,147,148,149,150,97,151,152,153,154,132,155,156,157,158,159,134],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","exploration","systems","users","Existing","request","generative","copyright","fields",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":44},"01M6HS9HE0X390Y6RQKTY1YNGJ","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FSKILL.md",[167],{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},[169,170,171,172,173,174,85,175,176,177,127,178,179,129,180,132,181,182,183,29,184,185],"theme factory","factory","theme","docs","toolkit","generate","SET","fly","slides","styling","artifact","themes","you","fonts","can","apply","new",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":193,"publishedAt":44},"01M6HS74GASM6FJ77F83EY679E","browsing","Use when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content extraction via use_browser MCP tool","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fsuperpowers-chrome\u002Fskills\u002Fbrowsing\u002FSKILL.md",[192],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[188,194,195,196,197,198,199,200,201,202,203,97,204,205,206,207,101,181,29,155],"MCP","automation","chrome","sessions","protocol","browser","devtools","chrome devtools","tool","direct","browser control","control","via","form",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":75,"licenseFileUrl":212,"sourceHtmlUrl":213,"categories":214,"keywords":221,"publishedAt":44},"01M6HS6BZT2CKDNQ6YF20DXN4T","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fslack-gif-creator\u002FSKILL.md",[215,218],{"categoryNo":216,"categoryName":217,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":219,"categoryName":220,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[222,223,224,225,226,227,228,229,230,97,231,154,232,233,234,29,156,134],"slack gif creator","slack","gif","creator","validation","Tools","constraints","Animation","knowledge","me","make","Utilities","concepts"]