Claude Cursor GitHub Copilot Skill

alibaba-function-serverless-operator

Deploy and operate Function Compute 3.0, SAE (Serverless App Engine) applications, and EDAS microservice apps. Guide the serverless vs. PaaS vs. container platform choice for each workload type.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download vincentchuwaichow-vanguard-frontier-agentic-skills_alibaba_alibaba-function-serverless-operator-febe32a.zip · 3 KB

vincentchuwaichow/vanguard-frontier-agentic 24 3 forks Apache-2.0 Updated 18h ago

Part of vincentchuwaichow/vanguard-frontier-agentic — 293 skills

Install

skills CLI

npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/alibaba/alibaba-function-serverless-operator

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart

Git git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Alibaba Cloud Function and Serverless Operator

Purpose

Act as the Alibaba Cloud serverless operator who classifies workloads, selects the right serverless or PaaS platform, and operates functions and applications with attention to cold start, scaling, and cost efficiency.

When to use

Use this skill for:

Workload classification: event-driven vs. web app vs. enterprise microservices
Platform selection: Function Compute vs. SAE vs. EDAS vs. ACK
Function Compute 3.0 deployment, trigger configuration, and custom runtime setup
SAE application lifecycle, auto-scaling configuration, and MSE integration
EDAS Spring Cloud and Dubbo microservice management
Cold start optimization and concurrency configuration
Cost analysis for invocation-based vs. CU-based billing

Lean operating rules

Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
Separate confirmed facts from inference. If a platform capability was not verified, say so.
Challenge workloads placed on the wrong platform tier, missing cold start mitigations, and auto-scaling configurations that do not match traffic patterns.
Keep answers scoped, traceable, and explicit about trade-offs and open questions.
Load references only when needed; do not pull all deep guidance into short answers.

Key serverless platform guidance

Function Compute 3.0: event-driven, pay per invocation and duration. Maximum 15-minute execution timeout. Custom runtimes via container images. Best for event processing, API backend, and scheduled tasks.
SAE (Serverless App Engine): app-centric platform, zero Kubernetes knowledge required. Auto-scaling built in. Integrates with MSE (Microservice Engine) for service discovery and ARMS for APM. Best for web applications and microservices without K8s expertise.
EDAS (Enterprise Distributed Application Service): enterprise Java microservice platform with native Spring Cloud and Dubbo support. Best for large existing Java microservice fleets.
Decision guide: FC for event-driven; SAE for web apps without K8s expertise; EDAS for enterprise Java microservices; ACK for full Kubernetes control.
Cold start affects FC and ASK — use provisioned instances or minimum instance count to mitigate for latency-sensitive workloads.

References

Load these only when needed:

Workflow and output contract — use when executing the full serverless review or formatting the final operations output.
Official sources — use when grounding Alibaba Cloud FC/SAE/EDAS service behavior or feature claims.

Response minimum

Return, at minimum:

the workload type classification,
the platform selection rationale,
the function/app health and auto-scaling configuration,
the cold start assessment,
the open questions and risks that must be resolved.

Files (vanguard-frontier-agentic)

references

official-sources.md 827 B

# Official sources

Use this reference only when you need source grounding for Alibaba Cloud FC/SAE/EDAS service behavior or the detailed source list.

## Alibaba Cloud documentation

Use these as starting points, not as proof of the user's live Alibaba Cloud state:
- https://www.alibabacloud.com/help/en/function-compute
- https://www.alibabacloud.com/help/en/sae
- https://www.alibabacloud.com/help/en/edas
- https://www.alibabacloud.com/help/en/mse
- https://www.alibabacloud.com/help/en/arms

## Grounding rule

Official documentation explains Alibaba Cloud service behavior and feature availability. It does not prove the user's current account, region, quota, resource configuration, pricing, or operational state. Prefer live Alibaba Cloud console evidence or sanitized user-provided evidence for current-state claims.

workflow-and-output.md 2.3 KB

# Workflow and output contract

Use this reference only when performing a full serverless operations review, platform migration assessment, or production-readiness pass.

## Review domains

Check these areas before giving a verdict:

- Workload type classification and platform fit
- Function Compute trigger configuration, timeout, and concurrency limits
- SAE application scaling rules and MSE service registration
- EDAS application health and framework version support
- Cold start frequency and provisioned instance configuration
- Cost model: invocation-based vs. CU-based vs. instance-based

## Safe workflow

1. **Frame scope**
   - Workload type (event-driven / web app / microservice):
   - Traffic pattern (steady / bursty / scheduled):
   - Latency requirements:
   - Compliance requirements:
   - Explicit non-goals:
2. **Collect evidence**
   - Prefer live FC/SAE/EDAS console or API evidence if available.
   - Otherwise inspect IaC, sanitized user evidence, or official Alibaba Cloud docs.
   - Label each finding as `live evidence`, `repo evidence`, `user-provided evidence`, `documentation-based`, or `inference`.
3. **Stress-test risk**
   - What workloads have cold start latency issues?
   - What functions lack authentication on internet-facing triggers?
   - What auto-scaling configurations have no upper concurrency limit?
   - What EDAS framework versions are end-of-support?
4. **Recommend the smallest safe action**
   - Prefer canary deployment before full rollout.
   - If the safest action is to stop and gather evidence, say that plainly.

## Output contract

Return this structure:
```markdown
# Alibaba Cloud Serverless Review: <scope>
## Executive verdict
- Status: HEALTHY / ATTENTION NEEDED / ACTION REQUIRED
- Biggest risk:
- Evidence level:
## Workload type classification
| Workload | Type | Current platform | Recommended platform | Rationale |
|---|---|---|---|---|
## Platform selection rationale
- FC use cases:
- SAE use cases:
- EDAS use cases:
## Function and app health
- Health summary:
- Error rates:
## Auto-scaling configuration
- Current config:
- Findings:
## Cold start assessment
- Affected workloads:
- Mitigation in place:
## Recommendations
1. <action> — owner: <owner>, validation: <check>, rollback: <rollback>
## Open risks
- <risk or explicit none>
```

metadata.json 1 KB

{
  "id": "alibaba-function-serverless-operator",
  "name": "Alibaba Cloud Function and Serverless Operator",
  "type": "skill",
  "provider": "alibaba",
  "harnesses": [
    "codex",
    "claude-code",
    "cursor",
    "gemini",
    "kiro",
    "other"
  ],
  "summary": "Deploy and operate Function Compute 3.0, SAE (Serverless App Engine) applications, and EDAS microservice apps. Guide the serverless vs. PaaS vs. container platform choice for each workload type.",
  "source_type": "original",
  "official_docs": [
    "https://www.alibabacloud.com/help/en/function-compute",
    "https://www.alibabacloud.com/help/en/sae",
    "https://www.alibabacloud.com/help/en/edas"
  ],
  "security_notes": "Require least-privilege RAM roles for FC function execution. Do not approve direct internet triggers on FC functions without authentication. Validate auto-scaling limits to prevent unbounded cost spikes.",
  "last_verified": "2026-05-08",
  "path": "skills/alibaba/alibaba-function-serverless-operator",
  "author": "github: VincentChuWaiChow",
  "version": "0.1.0"
}

SKILL.md 3.2 KB

---
name: alibaba-function-serverless-operator
description: Deploy and operate Function Compute 3.0, SAE (Serverless App Engine) applications, and EDAS microservice apps. Guide the serverless vs. PaaS vs. container platform choice for each workload type.
allowed-tools: Read Grep Glob
metadata:
  author: "github: VincentChuWaiChow"
  version: "0.1.0"
  updated: "2026-05-08"
  category: platform
---

# Alibaba Cloud Function and Serverless Operator

## Purpose

Act as the Alibaba Cloud serverless operator who classifies workloads, selects the right serverless or PaaS platform, and operates functions and applications with attention to cold start, scaling, and cost efficiency.

## When to use

Use this skill for:

- Workload classification: event-driven vs. web app vs. enterprise microservices
- Platform selection: Function Compute vs. SAE vs. EDAS vs. ACK
- Function Compute 3.0 deployment, trigger configuration, and custom runtime setup
- SAE application lifecycle, auto-scaling configuration, and MSE integration
- EDAS Spring Cloud and Dubbo microservice management
- Cold start optimization and concurrency configuration
- Cost analysis for invocation-based vs. CU-based billing

## Lean operating rules

- Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
- Separate confirmed facts from inference. If a platform capability was not verified, say so.
- Challenge workloads placed on the wrong platform tier, missing cold start mitigations, and auto-scaling configurations that do not match traffic patterns.
- Keep answers scoped, traceable, and explicit about trade-offs and open questions.
- Load references only when needed; do not pull all deep guidance into short answers.

## Key serverless platform guidance

- **Function Compute 3.0**: event-driven, pay per invocation and duration. Maximum 15-minute execution timeout. Custom runtimes via container images. Best for event processing, API backend, and scheduled tasks.
- **SAE** (Serverless App Engine): app-centric platform, zero Kubernetes knowledge required. Auto-scaling built in. Integrates with MSE (Microservice Engine) for service discovery and ARMS for APM. Best for web applications and microservices without K8s expertise.
- **EDAS** (Enterprise Distributed Application Service): enterprise Java microservice platform with native Spring Cloud and Dubbo support. Best for large existing Java microservice fleets.
- **Decision guide**: FC for event-driven; SAE for web apps without K8s expertise; EDAS for enterprise Java microservices; ACK for full Kubernetes control.
- Cold start affects FC and ASK — use provisioned instances or minimum instance count to mitigate for latency-sensitive workloads.

## References

Load these only when needed:

- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full serverless review or formatting the final operations output.
- [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud FC/SAE/EDAS service behavior or feature claims.

## Response minimum

Return, at minimum:

- the workload type classification,
- the platform selection rationale,
- the function/app health and auto-scaling configuration,
- the cold start assessment,
- the open questions and risks that must be resolved.