agentsclimarketplace

Alibaba function serverless operator

Skill Raishin/vanguard-frontier-agentic/skills/alibaba/alibaba-function-serverless-operator

Curated marketplace of AI skills, agents, and rules for cloud, zero-trust, and compliance-aware engineering - works with Claude Code, Codex, Cursor, Copilot, and more.

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-function-serverless-operator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.2 KB, 585 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it: 3 files

4.1 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most containers cloud skills give in 585 tokens

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-07

  • Run containers as a non-root userin 66 of 607, across 46 files
  • Use multi-stage buildsin 53 of 607, across 44 files
  • Use Promise.all for independent operationsin 47 of 607, across 13 files
  • Import directly instead of barrel filesin 46 of 607, across 12 files
  • Use ternary instead of AND for conditionalsin 45 of 607, across 12 files
  • Use Set or Map for O(1) lookupsin 42 of 607, across 10 files
  • Create a .dockerignore filein 41 of 607, across 31 files
  • Read individual rule files for detailsin 39 of 607, across 9 files
  • Copy dependency files before source codein 36 of 607, across 23 files
  • Authenticate server actions like API routesin 35 of 607, across 7 files
  • Use next/dynamic for heavy componentsin 34 of 607, across 9 files
  • Use React.cache for per-request deduplicationin 34 of 607, across 10 files

Said here and by no other author read

  • prefer official documentation and live evidence over memory
  • separate confirmed facts from inference
  • state if a platform capability is unverified
  • challenge workloads placed on wrong platform tiers
  • challenge auto-scaling configurations mismatching traffic patterns
  • keep answers scoped, traceable, and explicit about trade-offs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 327,132. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.