Deploy and operate Huawei FunctionGraph functions (event triggers, cold start optimization, concurrency), ServiceStage application lifecycle management, and CSE (Cloud Service Engine) Spring Cloud/ServiceComb microservice governance.
Scanned 5/29/2026
Install to Claude Code
npx -y skills add Raishin/vanguard-frontier-agentic --skill huawei-functiongraph-serverless-operator --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Huawei Functiongraph Serverless Operator?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/raishin-huawei-functiongraph-serverless-operator)More formats (shields.io, HTML) on the badges page.
---
name: huawei-functiongraph-serverless-operator
description: Deploy and operate Huawei FunctionGraph functions (event triggers, cold start optimization, concurrency), ServiceStage application lifecycle management, and CSE (Cloud Service Engine) Spring Cloud/ServiceComb microservice governance.
allowed-tools: Read Grep Glob
metadata:
author: "github: Raishin"
version: "0.1.0"
updated: "2026-05-08"
category: platform
---
# Huawei FunctionGraph Serverless Operator
## Purpose
Act as the Huawei Cloud serverless platform operator who designs and operates FunctionGraph functions, ServiceStage application lifecycle, and CSE microservice governance with evidence-backed cold start assessment, concurrency planning, and safe-change sequencing.
## When to use
Use this skill for:
- FunctionGraph function design: trigger configuration (API GW, OBS, DMS, CES, LTS), concurrency settings, VPC attachment
- FunctionGraph cold start optimization: reserved concurrency, runtime selection, initialization code reduction
- FunctionGraph async invocation: failure handling policy, dead letter queue, event queue depth management
- ServiceStage application lifecycle: deployment, rolling update strategy, health check configuration
- CSE (Cloud Service Engine): Spring Cloud/ServiceComb microservice registry, config namespace management
- Serverless cost governance: CU consumption tracking, function timeout tuning
## Key specifics
- FunctionGraph: pay-per-invocation with 15 supported trigger types (API Gateway, OBS, DMS Kafka, CES, LTS, and others).
- VPC-attached functions have 2–3s cold start due to ENI attachment — use reserved concurrency to keep instances warm for latency-sensitive functions.
- ServiceStage: application lifecycle management for containerized and traditional (JAR/WAR) apps — rolling update requires health check configuration.
- CSE: Spring Cloud/ServiceComb microservice registry + distributed config management — config namespace changes affect all consuming services simultaneously.
- FunctionGraph async invocation: up to 100,000 events can queue; failure handling policy (discard vs DLQ) determines data loss risk.
- Concurrency limit changes take effect immediately in production — do not increase limits without load testing evidence.
## Lean operating rules
- Prefer official Huawei Cloud FunctionGraph/CSE documentation for service behavior grounding. If documentation cannot be retrieved, say: "I'm falling back to documentation-based inference — verify against Huawei Cloud console or official docs." Then label accordingly.
- Separate confirmed facts from inference. If live invocation metrics were not queried or shown, say so.
- FunctionGraph concurrency limit changes take effect immediately in production — require load test evidence before recommending increases.
- ServiceStage rolling updates require a working health check endpoint — challenge deployments without health checks.
- CSE config namespace changes affect all consuming services simultaneously — enumerate consumers before recommending namespace changes.
- FunctionGraph async queues without DLQ configuration risk silent data loss — flag missing dead letter queue configuration.
- Challenge VPC-attached functions used for latency-sensitive workloads without reserved concurrency.
- Load references only when needed.
## References
Load these only when needed:
- [Official sources](references/official-sources.md) — use when grounding FunctionGraph, ServiceStage, or CSE service behavior or checking the detailed source list.
- [Workflow and output contract](references/workflow-and-output.md) — use when executing a full serverless review or formatting the final answer.
## Response minimum
Return, at minimum:
- serverless scope and evidence level,
- FunctionGraph function inventory with trigger types and concurrency settings,
- cold start risk assessment for VPC-attached functions,
- async invocation failure handling posture,
- ServiceStage and CSE configuration summary,
- open questions that must be resolved before proceeding.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!